Deploying module at node level with JNDI activation specification

The adapter is deployed at the node level, and the application provides a JNDI reference to the activation specification. You must create the activation specification with the same JNDI name at the cluster scope from the Process Administrative Console. The adapter can be shared across multiple applications

1. In the Service Configuration Properties window, from the Deploy connector project property list, select On server for use by multiple applications.
2. From the Connection properties list, select Use JNDI lookup name configured on server.
3. In the JNDI lookup name property field, specify the JNDI name. Use this same JNDI name when you create the activation specification from the Admin Console.
4. Create the module as described in the Business process management samples for WebSphere Adapters.
5. In the Dependencies option for the module, ensure that the Deploy with module option is not selected for the adapter.
6. If the server is not running, right-click your server in the Servers view and select Start.
7. When the server status changes to Started, right-click the server and select Administration > Run administrative console. Log on to the administrative console.
8. To install the adapter at the node level, click Resources > Resource Adapters > Resource adapters. In the clustered environment, you must install the adapter in each node separately.
9. In the Resource adapters page, click Install RAR.
10. In the Install RAR file page, click Browse and navigate to the RAR file for your adapter. Deploy the RAR on each node.

    The RAR files are typically installed in the following path: IID_installation_directory/ResourceAdapters/adapter_name/adapter.rar

11. For deployment at node level, do not select any Scope because the scope is always Node. Click Next.
12. Optional: In the Resource adapters page, change the name of the adapter and add a description. Click OK.
13. Click Save in the Messages box at the top of the page.
14. To install the RAR at the cluster level, click Resources > Resource Adapters > Resource adapters
15. In the Resource adapters page, set the Scope to Cluster, and then click New.
16. Select the RAR deployed at the node level, and then check if the adapter RAR is now deployed at the cluster level. Deploy the application after the adapter is deployed at the node level on the individual nodes, and then at the cluster level.
17. From the Deployment Manager Admin Console, click Install applications to deploy the application.
18. In the Admin Console, click Resources > Resource Adapters > IBM WebSphere Adapter for SAP Software > J2C activation specifications > New to create the activation specification from the adapter deployed at the cluster level.
19. When installing the adapter, in the Name field, you must enter the same name as defined in the RAR.
20. In the JNDI name field, you must enter the same name as given during the module creation.
21. Click Resources > Resource Adapters > IBM WebSphere Adapter for SAP Software > J2C activation specifications to check if the JNDI reference on the adapter is same as the one specified for the module.
22. Click Resources > Resource Adapters > IBM WebSphere Adapter for SAP Software > J2C activation specifications > Custom properties to set values for the activation specification in the Admin Console.
23. From the Deployment Manager Admin console, click Install applications to deploy the application after you deploy the RAR and create the activation specification.
24. On the Step 2: Map modules to servers page, select the module and click Next. The adapter is not part of the deployed application.