4 Setting up the Development Environment for JDeveloper

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:

• Creating Server Connections in JDeveloper

• Creating Connection Factories for Oracle JCA Adapters

• Disabling the JMS Reporting Provider

4.1 Creating Server Connections in JDeveloper

To deploy services from JDeveloper, the JDeveloper environment must be connected to an Oracle WebLogic Server. To do this task, 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.

• How to Create an Application Server Connection

• How to Create a SOA-MDS Connection

• How to Change the MDS Repository Location

4.1.1 How to Create an Application Server Connection

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.

4.1.2 How to Create a SOA-MDS Connection

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:

1. From the File main menu, point to new New and select From Gallery.

   The New Gallery wizard appears.

2. In the General category, select Connections.
3. Select SOA-MDS Connection, and click OK.

   The Create SOA-MDS Connection dialog appears.

4. In the connection fields, provide values appropriate to your environment.

   Click Help on the dialog to get information about each field and the values you need to enter.

5. Click OK.

   You can now browse the connection in the Resources window and view shared artifacts under the /apps node.

4.1.3 How to Change the MDS Repository Location

The default MDS Repository connection uses a default repository located in $JDEV_USER_DIR/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:

1. If the Resources window is not visible in JDeveloper, click the Window menu and select Resources.
2. In the Resources window, expand SOA-MDS, right-click the repository name (the default name is SOA_DesignTimeRepository), and click Properties.

   The Edit SOA-MDS Connection dialog appears.

   Figure 4-1 Edit SOA-MDS Connection Dialog

   
   Description of "Figure 4-1 Edit SOA-MDS Connection Dialog"
3. In the MDS Root Folder field, select the new root directory for the repository.

   Note:

   You can select any directory, but it must have a folder named apps directly beneath it.

4. Click Test Connection to verify the directory.
5. Upon successful completion of the test, click OK.

4.2 Creating Connection Factories for Oracle JCA Adapters

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:

• The 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.

4.3 Disabling the JMS Reporting Provider

By default, the Service Bus JMS reporting provider is deployed in a 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 Untargeting a JMS Reporting Provider in Administering Oracle Service Bus. Disabling the reporting provider prevents benign JMS reporting provider errors at server startup.