Create G-Billing Code for New Customer
Create a New G-Billing Code for a Customer who is being onboarded onto SCBN.
If the customer is an existing one, then this step would not be needed.
Create Business Alias in BPN for the Customer
Again, creation of Business Alias would be needed if the Customer is a new one that is being onboarded.
If the customer is a existing one, then we would not need the new Busines Alias to be created.
Create Communication Protocol relationship for Customer to receive and send EDI documents to SCBN
The New Protocol Relationship needs to be created under Relationships under the Customer Profile in Inflight to have the Customer Send and Receive Documents to and from SCBN.
Login to IBM Cloud
Search APP CONNECT from the Catalog and create a service
Search APP CONNECT from the Catalog and create a service with the desired plan.
Launch App Connect
Open the created cloud Foundry Service and click on Launch APP CONNECT
Create new Flows for an API and Create Model.
On the Dashboard, click New > Flows for an API. Enter a name that identifies the purpose of your API. In the Model name field, you need to enter a name for your model that reflects the type of object that your API will work with. Click Create model.
Develop a Flow and Start API.
Complete the Opereations and Properties Tab. Click on Implement Flow with Request and Response Node. Add Applications as needed. Complete the Parameters for each of these and click Done.
From the options menu (â‹®), click Start API.
Test the flow for your API
Click the Manage tab and then scroll down to the Sharing Outside of Cloud Foundry organization.
Click Create API key.
Click the API Portal Link link.
To invoke your API in the API portal, click Try it.
The URL created here from Sharing Outside CLoud Foundry Organization would become the exposed URL to which the data gets posted from SCBN.
Create HTTP Protocol Relationship in SCBN to have the document posted to APP CONNECT
In this HTTP relationship, the destination URL would be the URL generated in Step 9. Apart from destination URL, the header parameters (x-ibm-client-id and content type) needs to be passed for authentication
Creating Routing Rules in SCBN
The routing rules in the Business Alias needs to be created to receive the documents from the customer, translate them into Json format using the translation map and then post the documents out to APP CONNECT using the HTTP relationship created in Step 10.
Acknowledgement and Further Processing
API Flow in APP CONNECT can be configured to send acknowledgement to SCBN on receipt of documents.
APP CONNECT flow would receive the document and would do further processing as configured. The further processing might involve posting of document to another application as well.