Resource adapter deployment

When you click finish in J2C Java bean creation wizard and deployment wizard, unless you specified the Deploy RAR to ear option explicitly, our tools will try to deploy the resource adapter to the server.

If the project has a target server, the resource adapter is deployed to the this server. If the project has no target server, but is associated with an EAR, the application selects the first server that is compatible with that EAR to deploy the RAR. If no EAR is associated with the project, but a server instance is present, that server instance is picked up. If no server instance is created, the application attaches a listener that listens for new server creation, and when the server is created, the RAR will be deployed to this server.

Note: For the RAR deployment step server doesn’t need to be start. In case server is not started, we just postpone (by attaching the publish listener) the deployment step until the time when server is started/republished.

JNDI browse functionality: In this scenario, you can browse to see what J2C Connection factories associated with specific RAR file are defined on the server. After you click Browse, you select the server instance on which the connection factories will be looked up. Once the server is selected, the tool will look up all the connection factories available on the server for the given resource adapter. All the non-default connection properties will be displayed.
Note: If WebSphere 6.0 or WebSphere 6.1 servers is selected, the server will be started before the information about the connection factories is retrieved.
JNDI create functionality: In this scenario, you can create a new connection factory Click New. Select the server on which the connection factory is to be created. On the next page the user specifies the connection properties for the given connection factory. This page is essentially the same as the connection page in the J2C Java bean creation wizard (for the non-managed part)
Note: If WebSphere 6.0 OR WebSphere 6.1 servers are selected, they do not have to be started. In case the server is not started, the connection factory creation step will be postponed until the server is republished.
Multiple resource adapters: Multiple resource adapter definitions are supported in the following situations:
- When a J2C Java bean has been generated for a managed-only scenario, and you try to invoke the Deployment wizard or Add method wizard.
- The JNDI name specified is not present on the running server instance, or the corresponding servers are not running.
- There are multiple resource adapters defined on the class path of the project where J2C Java bean was generated.
IF all these conditions are true, you nust select the resource adapter that was used to generate the J2C Java bean, before the Deployment wizard or Add method functionality can be invoked