|
|
A resource adapter is a system library specific to an Enterprise Information System (EIS) and provides connectivity to that EIS. A resource adapter is analogous to a JDBC driver, which provides connectivity to a database management system. The interface between a resource adapter and the EIS is specific to the underlying EIS. These resource adapters are based on JCA 1.5 standards and need to be deployed in the application server. The resource adapter plugs into an application server, such as Oracle WebLogic Server, and provides seamless connectivity between the EIS, application server, and enterprise application.
Oracle WebLogic Integration integrates with resource adapters via the Adapter Framework. The Adapter Framework enables a resource adapter to expose its functionality as a web service, which is expressed in a WSDL. The adapter framework uses the Web Service Invocation Framework (WSIF) standard to convert a web service call from a WLI business process into a JCA interaction for the resource adapter.
To use the resource adapter to connect to the EIS, you need to create the WSDL representing the EIS-specific resource adapter services in the EIS environment. The adapter service WSDL contains JCA-specific extensions to store adapter-related information. You can then create Oracle WebLogic Integration event generators and controls using these adapter services.
This section provides information about:
The following resource adapters are supported in this release:
You need to manually deploy the JCA compliant resource adapters before you can use them for EIS connectivity. Login to Oracle WebLogic Server Administration Console using the http://<host:port>/console URL and deploy the resource adapters, where host is the host name or IP address of the Oracle WebLogic Server administrative server, and port is the server listening port.
To use the Oracle Applications adapter, deploy the following files in the specified order:
To use the Oracle AQ adapter, deploy the following files in the specified order:
| Note: | Because the Oracle AQ adapter and the Oracle Applications adapter require some of the classes that are available in the DBAdapter.rar file, make sure that you deploy these resource adapters in the specified order. |
These adapter resources (the .rar files) are located in the WLI_HOME\lib directory.
For more information about deploying the resource adapters in Oracle WebLogic Server Administration Console, see Deploy resource adapters.
After deploying the resource adapter, to invoke an EIS in managed or non-managed mode, you need to configure the resource adapter. For more information see Managed and Non-managed Connections.
For information about installing, configuring, and deploying the Oracle Application Adapter for SAP R/3, see Oracle Application Adapter for SAP R/3 Installation Guide.
Based on how resource adapters establish a connection to an EIS, resource adapters are said to invoke the EIS in a managed mode or a non-managed mode. The EIS is invoked in the managed mode when you use a data source and Oracle WebLogic Server manages the transaction. The EIS is invoked in the non-managed mode when you do not specify any data source and the resource adapter takes care of the connection management.
For non-managed connections, to invoke an EIS, Oracle WebLogic Integration uses the connection details specified while generating the resource adapter service WSDL in the EIS environment. These connections are not made within the context of a transaction.
If you want a managed connection between Oracle WebLogic Integration and the EIS via the resource adapter, create a data source in Oracle WebLogic Server Administration Console. In addition, after deploying the resource adapters, you need to configure the outbound connection instance properties in the Outbound Configuration page of the resource adapter in the Oracle WebLogic Server Administration Console. The JNDI name of the data source is maintained in the WSDL file of the resource adapter service and is used to obtain the connection details specified in the data source and invoke the EIS. For more information, see Creating a Data Source and Configuring Deployed Resource Adapters.
A data source is a J2EE standard method of configuring connectivity to a database. Each WebLogic data source contains a pool of database connections. Applications look up the data source on the JNDI tree or in the local application context and then use a database connection from the pool of connections. Data sources and their connection pools provide connection management processes that help keep your system running and performing. To invoke an EIS in a managed mode, you need to use a data source.
Configure the data source using information available in configuring JDBC data sources and Create JDBC data sources in the Oracle WebLogic Server Administration Console Help.
After you configure the JDBC data source, you need to configure the deployed resource adapters to use this new data source. For more information see Configuring Deployed Resource Adapters.
To invoke an EIS in a managed, configure a deployed resource adapter by modifying its outbound connection pool properties and associating it with outbound connection instances.
To configure a resource adapter:
The resource adapter is now configured to use this outbound connection instance for invoking the EIS.
The Oracle Applications Adapter provides bi-directional connectivity to the Oracle E-Business Suite. The Oracle Applications adapter service provides the necessary infrastructure to integrate with other applications in a heterogeneous enterprise environment.
Use the JDeveloper application to create Oracle Applications adapter services. You can use these services to send or receive messages from Oracle E-Business Suite.
Oracle JDeveloper provides wizards that assist you in creating inbound and outbound adapter services. The wizard collects the necessary information to generate the WSDL file that defines the service.
You can create both inbound and outbound services. While creating a service, you can select outbound operations on a table like Insert, Update, or Delete to create outbound services. Use the WSDL generated for these outbound operations to create a JCA control and use the control to invoke the services in the EIS. You can select inbound operations like polling for new or changed records in a table to create inbound services. Use the WSDL generated for these inbound operations to create a JCA event generator and use the event generator to receive events from the EIS.
To create an Oracle Applications adapter service:
Based on the operation you select, the generator service is either an inbound service or an outbound service. Use the inbound service to create a JCA control and use the outbound service to create a JCA event generator.
After you configure the Oracle Applications adapter service, the WSDL is generated and placed in the project directory. An XSD file that contains the schema for the database object and the inbound / outbound header fie is also created.
All required WSDLs and schema files are created in a folder with the same name as the service name that you provide during the adapter configuration. Use the generated WSDL to create a JCA event generator or control in Oracle WebLogic Integration.
For more information, see Creating Inbound and Outbound Services in Oracle Enterprise Service Bus Developer's Guide and Oracle Application Server Adapter for Oracle Applications User's Guide.
Oracle Advanced Queuing (Oracle AQ) is a database integrated message queue. The Oracle Advanced Queuing (AQ) adapter handles enqueuing (posting of messages) to a queue and dequeuing (removal of messages) from a queue.
Use the JDeveloper application to create Oracle AQ adapter services. You can use these services to enqueue or dequeue messages in Oracle AQ.
Oracle JDeveloper provides wizards that assist you in creating inbound and outbound adapter services. The wizard collects the necessary information to generate the WSDL file that defines the service.
You can create both inbound and outbound adapter services. While creating a service, select the enqueue operation to create an outbound service. Use the WSDL generated for this outbound service to create a JCA control. While creating a service, select the dequeue operation to create inbound services. Use the WSDL generated for the inbound service to create a JCA event generator.
To create an Oracle AQ adapter service:
For more information about creating the resource adapter service, see Oracle Application Server Adapter for Advanced Queuing.
After you configure the Oracle AQ service, the WSDL is generated and placed in the project directory. An XSD file that contains the payload schema is also created along with the inbound / outbound header WSDLs.
All required WSDLs and schema files are created in a folder with the same name as the service name that you provide during adapter configuration. Use the generated WSDL to create a JCA event generator or control in Oracle WebLogic Integration.
Oracle WebLogic Integration connects to a SAP R/3 system through Oracle Application Adapter for SAP R/3. Oracle Application Adapter for SAP R/3 is an application adapter that provides connectivity and carries out interactions on a SAP R/3 system.
To use the Oracle Application Adapter for SAP R/3 with Oracle WebLogic Integration, you need to:
For information about these tasks, see Oracle Application Adapter for SAP R/3 Installation Guide.
Based on your requirements, you can now configure inbound and outbound processing using Oracle WebLogic Integration. For information about these tasks, see Oracle Application Adapter for SAP R/3 User's Guide.
|