This chapter describes development environment setup topics that are relevant to Service Bus, such as using the default Derby database and disabling the default JMS reporting provider.
This chapter includes the following topics:
In order to deploy services from JDeveloper, your JDeveloper environment needs to be connected to an Oracle WebLogic Server. To do this, you create an application server connection. You can also create connections to the Oracle Metadata Services (MDS) repository to share artifacts with SOA Suite applications.
When developing in JDeveloper, you must create a connection to the application server to which Service Bus applications will be deployed. Once you create this connection, you can deploy your applications to the server and you can access other applications and artifacts already deployed to that server.
For instructions, see "How to Create a Connection to the Target Application Server" in Developing Applications with Oracle JDeveloper.
To deploy a Service Bus application that shares data with other composites, use the Create SOA-MDS Connection wizard to create a connection to a database-based Oracle MDS Repository server.
To create a SOA-MDS connection:
The New Gallery wizard appears.
The Create SOA-MDS Connection dialog appears.
Click Help on the dialog to get information about each field and the values you need to enter.
You can now browse the connection in the Resources window and view shared artifacts under the /apps node.
The default MDS Repository connection uses a default repository located in
/soamds in the JDeveloper system or application data folders. You can change the location of the repository if needed.
To change the MDS Repository location:
The Edit SOA-MDS Connection dialog appears.
Figure 4-1 Edit SOA-MDS Connection Dialog
You can select any directory, but it must have a folder named apps directly beneath it.
The Oracle JCA adapters are deployed as JCA resource adapters in a WebLogic Server container. Adapters are packaged as Resource Adapter Archive (RAR) files using a JAR format. When adapters are deployed, the RAR files are used and the adapters are registered as connectors with the WebLogic Server or middle-tier platform. The RAR file contains the following:
ra.xml file, which is the deployment descriptor XML file containing deployment-specific information about the resource adapter
Declarative information about the contract between Oracle WebLogic Server and the resource adapter
Adapters also package the
weblogic-ra.xml template file, which defines the endpoints for connection factories. For information about creating connection factories and connection pools, see "Adapter Framework" in Understanding Technology Adapters.
By default, the Service Bus JMS reporting provider is deployed in an Service Bus domain. The reporting provider uses a database to persist reporting data. If you do not want to use the JMS reporting provider in your development domain, you can disable or untarget it during the domain creation process.
For more information, see "How to Untarget a JMS Reporting Provider" in Administering Oracle Service Bus. Disabling the reporting provider prevents benign JMS reporting provider errors at server startup.