Using Integrated SOA Gateway in Oracle EBS (Websevice)

http://blog.csdn.net/pan_tian/article/details/10159935

How does Oracle EBS integrate with third-party systems? For example, if the X system knows the material code, needs to read the material information from the EBS system, or if the X system wants to synchronize its personnel information to EBS, you may need to use the Oracle EBS Integrated SOA Gateway for this kind of integration problem.

Integrated SOA Gateway is a responsibility in EBS, and when assigned to a user, you can see that when you enter a responsibility (such as), you see that all Oracle EBS can (just, really let go of the actions that need to be released and deployed) to develop interfaces externally.

(Of course, if the system comes with an interface that doesn't meet your integration needs, then you need to customize the interface.)

First share some of the collected documents, the subsequent need to be able to read more detailed:

Oracle®integration Repository User ' s Guide

Oracle e-business Suite Integrated SOA Gateway User ' s Guide
Oracle e-business Suite Integrated SOA Gateway Implementation Guide R12.1
Oracle e-business Suite Integrated SOA Gateway Developer ' s Guide

Minute Guide to Oracle integration Repository

Enable Oracle e-business Suite Integrated SOA Gateway
Oracle Integration Repository

Oracle application Server adapters for Files, FTP, Databases, and Enterprise Messaging User's Guide
Securing E-business Suite Web Services with Integrated SOA Gateway

Using SOA Gateway in EBS 12

Enable Oracle e-business Suite Integrated SOA Gateway

To use the integrated SOA Gateway, first make some patches, see note 556540.1 or another article of mine.

Ordinary users can only view the EBS interface information, but not the interface, and deployment, only the sysadmin account has this permission. (Note: By default, the vast majority of interfaces are not published and deployed and can only be called by a third-party system after the sysadmin release is required.) ）

If you do not want to use the sysadmin account to manage the interface, then assign three roles to the target user to do the same thing as the sysadmin, these three roles are:

* Irep Administrator (Chinese:Irep Administrator)
* System Integration Developer (Chinese: Systems integration Developer)
* System Integration Analyst (Chinese: Expert in systems integration analysis)

Each role has different permissions to the interface library, such as

The sysadmin defaults to the above three roles, so no special settings are required. Other users need to set up, how to assign a role to the user can see note:861982.1

Interfaces

The following example shows how to release an interface, allowing an external program to invoke a procedure, as an instance of the system provided by default.

Log in as a sysadmin account, and then path: Integrated SOA Gateway > Supply Chain Management > Inventory > Inventory Organization Setup, you can see two interfaces, one of which is called Locator maintenance API, this interface allows users to create, modify, delete locator.

(If the interface's internal name is user_xxx_xxx, such as user_pkg_lot,user_pkg_serial, it means that the interface is a user-defined interface that needs to implement its own background business processing logic)

Click inside to see the details of the interface. You can see that this interface is a PL/SQL interface, and the corresponding package in the background is called Inv_loc_wms_pub, which contains four methods for locator processing. If you are interested, you can open inv_loc_wms_pub this package, you can see the specific implementation logic.

Each method can be point in, is the interface method description and interface parameters.

Generate WSDL

Here, the PL/SQL package needs to be published in WebService mode, and this interface needs to be generated as WSDL. (see this article for your own customized PL/SQL registration to the integrated SOA Gateway)

The Wsdl:web Service Definition language (WEB service define Language), which defines the service interface. In fact, it can describe two different aspects of a service: the signature of the service (name and parameters), and the binding and deployment details (protocol and location) of the service.

Once the WSDL is generated, the Web Service status becomes ' Generated '. And you can view the WSDL

' View WSDL ' to see the WSDL information

Deploy Webservice

After the WSDL is generated, the external system cannot invoke it, and you need to deploy the generated WSDL to the application server, which also installs some necessary webservice files to the application server. Here's a check for the WebService security type: Username token, SAML token.

For these two types of security, you can read the securing e-business Suite Web Services with Integrated SOA Gateway in detail for a detailed explanation.

Create Grant

When the deployment is complete, the WebService state becomes deployed. There is one more step after this-authorization, whether you want all users to have access to the interface, or just a specific user.

Test Web Service

The address of the WSDL is HTTP://[HOST]:[PORT]/WEBSERVICES/SOAPROVIDER/PLSQL/INV_LOC_WMS_PUB/?WSDL

Then the address of the Oracle Self-Test Web service is the address of the top WSDL, but remove the '? WSDL' (main do not remove the slash/, otherwise it will be reported no WebService Provider is registered at the This URL)

http://[host]:[port]/webservices/soaprovider/plsql/inv_loc_wms_pub/

After invoke, the information on the HTML form is composed of a SOAP message, which is sent to the application server, and the server returns the returned information to the client in the form of a SOAP message.

Below is a sample SOAP request message:

2. <soap:envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http// Docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd ">
4. <soap:header xmlns:ns1="Http://xmlns.oracle.com/apps/cux/soaprovider/plsql/cux_0_ws_server_ prg/">
6. <ns1:soaheader>
8. <ns1:responsibility>inventory</ns1:responsibility>
10. <ns1:respapplication>cux</ns1:respapplication>
12. <ns1:securitygroup>standard</ns1:securitygroup>
14. <ns1:nlslanguage>simplified Chinese</ns1:nlslanguage>
16. <ns1:org_id>0</ns1:org_id>
18. </ns1:soaheader>
20.         <wsse:Security  xmlns:wsse= "http://docs.oasis-open.org/wss/2004/01 /oasis-200401-wss-wssecurity-secext-1.0.xsd " xmlns= "Http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"   xmlns:env= "http://schemas.xmlsoap.org/soap/envelope/"  soap:mustunderstand= "1" >   
22. <wsse:usernametoken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/ Oasis-200401-wss-wssecurity-secext-1.0.xsd " xmlns=" http://docs.oasis-open.org/wss/2004/01/ Oasis-200401-wss-wssecurity-secext-1.0.xsd ">
24. <wsse:username>esb_test</wsse:username>
26. <wsse:password type="http://docs.oasis-open.org/wss/2004/01/  Oasis-200401-wss-username-token-profile-1.0#passwordtext ">1234567890</wsse:Password>
28. </wsse:usernametoken>
30. </wsse:security>
32. </soap:header>
34. <soap:body xmlns:ns2="HTTP://XMLNS.ORACLE.COM/APPS/CUX/SOAPROVIDER/PLSQL/CUX_0_WS_SERVER_PRG /invokews/">
36. <ns2:inputparameters>
38. <ns2:p_iface_code>xxx</ns2:p_iface_code>
40. <ns2:p_batch_number>1234567654323</ns2:p_batch_number>
42. <ns2:p_request_data>32424</ns2:p_request_data>
44. </ns2:inputparameters>
46. </soap:body>
48. </soap:envelope>

(The RESPONSIBILITY,RESPAPPLICATION,SECURITYGROUP,NLSLANGUAGE,ORG_ID node in the request header is the SOAP header information required by the Oracle EBS system for account validation)

Examples of SOAP response messages:

2. <env:envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
4. <env:header/>
6. <env:body>
8. <outputparameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns= "http:/ /xmlns.oracle.com/apps/cux/soaprovider/plsql/cux_0_ws_server_prg/invokews/">
10. <x_return_code xmlns="HTTP://XMLNS.ORACLE.COM/APPS/CUX/SOAPROVIDER/PLSQL/CUX_0_WS_SERVER_PRG /invokefmsws/">error001</x_return_code>
12. <x_return_mesg xmlns="Http://xmlns.oracle.com/apps/cux/soaprovider/plsql/cux_0_ws_server_ prg/invokefmsws/"> Input Request message format is incorrect </x_return_mesg>
14. <x_response_data xsi:nil="true" xmlns="http://xmlns.oracle.com/apps/cux/soaprovider/ plsql/cux_0_ws_server_prg/invokews/"/>
16. </outputparameters>
18. </env:body>
20. </env:envelope>

In addition to this standard test method, you can also use professional tools such as SOAPUI to test WebService, see this article.

SOA Monitor

You can monitor the performance of the webservice that the client calls EBS in the SOA monitor.

Path: Integrated SOA gateway–> SOA Monitor

If the call fails, you can look at the details or the log for specific content.

------

How to assign user management responsibilities to a subscriber

Reference note:734280.1 UMX Error: ' There is no functions available for this responsibility ' and/or ' there is no valid Navigatio NS for this responsibility ' when accessing ' User Management ' responsibility.

To implement the solution, please execute the following steps:
1. Log into the applications as SYSADMIN User.
2. Choose User Management responsibility.
3. Navigate to Users Web page.
4. Search and find the user want to inherit the Security Administrator and Customer Administrator Roles.
5. Click on Update Icon.
6. Click on Assign Roles button.
7. Find and choose ' Security Administrator ' Role.
8. Apply.
9. Repeat the Steps (6-8) for ' Customer Administrator ' Role.
Ten. Log as the user who was assigned user Management Responsibility and facing the issue.
Retest the issue.
Migrate the solution as appropriate to other environments.