This guide walks you through connecting your Oracle E-Business Suite (EBS) account through Makini Link.Filling in the form takes about 10 minutes. Before that, your EBS administrator has a one-time setup to do on the EBS side, which is the bigger job. You'll need your EBS address, an EBS user for Makini, and a few details about that user's responsibility and operating unit.
EBS has no ready-made API to connect to. Makini talks to EBS through Oracle's Integrated SOA Gateway (ISG), and in EBS nothing is available over ISG until an administrator deploys it. That's why Step 1 exists.You'll need your EBS administrator. Step 1 is done by whoever manages your EBS applications tier, usually an EBS DBA. If that isn't you, send them this guide.Use a user made just for this connection. Everything Makini does in EBS happens as this user, under the responsibility you enter in Step 3. A personal login mixes your own activity with the connection's, and the connection stops working when that person leaves.Most EBS systems sit on your own network. If yours can't be reached from the internet, you'll turn on Connect to on-prem system via VPN/Firewall on the same form in Step 3. Have your network details ready, or your network team nearby.
Integrated SOA Gateway must be enabled on your EBS instance. This is a one-time Oracle setup. If it isn't enabled yet, plan for it: enabling it restarts the EBS applications tier.
2.
Deploy Makini's service definition. Ask us for the Makini ISG service descriptor file. Your administrator deploys it with Oracle's standard ISG deployment tool. It deploys interfaces Oracle already ships with EBS. It creates no database objects and adds no custom code.
The file has a read section and a separate, optional write section. Your administrator can deploy the read section on its own if that's all you need.
By default the file grants the services to everyone. If that's wider than your policy allows, your administrator can grant them to the responsibility your Makini user holds instead.
3.
Check that it worked. Oracle's deployment tool reports success even when a service wasn't actually created, so the log isn't proof. Your administrator should open each service's description in a browser, for example http://ebs.example.com:8000/webservices/rest/ego_item_sync_v?WADL. A page that loads means it's deployed. An error mentioning ISG_INVALID_ALIAS means it isn't, whatever the log said.
If your administrator had to use different service names (aliases) than the ones in the file, ask them what prefix they added. You'll need it in Step 3.
Ask your EBS administrator to create an EBS user for Makini and give it a responsibility with access to the data you want to bring across. Then collect:
The responsibility key of that responsibility
The application short name that responsibility belongs to
The numeric operating unit ID (ORG_ID) you want to connect. It's a number, not the operating unit's name.
EBS URL: the address of your EBS applications tier, without any path, for example http://ebs.example.com:8000. The full service address ending in /webservices/rest works too.
Username: the EBS user from Step 2
Password: that user's password
Responsibility Key: the responsibility key from Step 2. The form comes with an example value filled in, so replace it with yours.
Responsibility Application: the application short name for that responsibility. Replace the example value with yours.
Operating Unit (ORG_ID): the numeric operating unit ID, for example 204. Digits only.
2.
Under Advanced settings, ISG Service Alias Prefix is optional. Leave it empty unless your administrator deployed the services with a prefix in Step 1. If they did, enter that prefix.
3.
If your EBS system isn't reachable from the internet, turn on Connect to on-prem system via VPN/Firewall and fill in your network details.
