This subsection describes the notes on the resource adapters.
- Functionality that is unavailable based on the deploy method
- When you include and use the resource adapter in the J2EE application, the following functionality is not enabled even if the resources included in the J2EE application are updated:
- Detecting the J2EE application updates
- Reloading the J2EE applications
- For details, see 13.8.13 Notes and restrictions related to reloading.
- Notes on the display names of the resource adapters
- The EJBs and WARs in the J2EE application can concurrently use the resource adapters that are deployed as J2EE resource adapters and the resource adapters that are included in the J2EE application. However, two or more resource adapters with the same display name cannot be used on one J2EE server. If you try to use resource adapters with the same display name on one J2EE server, an error message is displayed and the resource adapter fails to start. The examples of procedures when the resource adapter fails to start are as follows:
- Example 1.
- A resource adapter with the display name 'Rar1' is deployed on the J2EE server.
- A J2EE application containing a resource adapter with the display name 'Rar1' is imported.
- Example 2.
- A resource adapter with the display name 'Rar2' is deployed on the J2EE server.
- A resource adapter with the display name 'Rar2' is added to the imported J2EE application.
- Example 3.
- A J2EE application containing a resource adapter with the display name 'Rar3' is imported.
- A resource adapter with the display name 'Rar3' is deployed on the J2EE server.
- Notes on the optional names for resource adapters
- If multiple resource adapters are deployed with the same optional name, an error message is displayed and the resource adapter fails to start.
- Notes on the start processing of the resource adapters
- If the start processing of a resource adapter fails while a J2EE server is being started, the resource adapter status changes from Start to Stop. In this case, the resource adapter does not start even when you start the J2EE server the next time. The application that is using the applicable resource adapter also fails to start.
- In such cases, see the error information, eliminate the cause of the error, and then take the following action:
- If the transaction support level of the resource adapter is LocalTransaction or NoTransaction
- Start the resource adapter that changed to Stop status.
- Start the application that is using the resource adapter.
- If the transaction support level of the resource adapter is XATransaction
- Start the resource adapter that changed to Stop status.
- Restart the J2EE server to recover the unconcluded transactions.
- Start the application that is using the resource adapter.
- Other notes
- The functionality for referencing the URL connection Resource Factory is not supported.