Troubleshooting
Problem
Collecting data for problems with the WebSphere Adapter for JDBC. Gathering this MustGather information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
Resolving The Problem
MustGather technotes provide a detailed description of the documentation required by the IBM Support team to diagnose your problem.
Select the runtime where your problem occurs:
WebSphere Application Server
WebSphere Enterprise Service Bus
WebSphere Process Server
IBM Business Process Manager
| WebSphere Application Server |
Gather the following documentation for the WebSphere Adapter for JDBC running with Rational Application Developer and WebSphere Application Server runtime:
Troubleshooting Development/Discovery time issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues during discovery process using Rational Application Developer:
Adapter version being used during discovery:
1. Launch the J2C Bean wizard: Go to the Enterprise Explorer of Rational Application Developer for WebSphere Software and click File > New > Other > J2C > J2C Bean.
2. Click Next.
3. In the Resource Adapter Selection window, expand the JDBC folder to find the select IBM WebSphere Adapter for JDBC Software (IBM : version), where version is the version of the adapter being used.
Project Interchange:
Steps to export the Project Interchange:
1. In the Project Explorer, right-click the project that you want to export, and select Export > Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Meta-data discovery logs:
Steps to enable and collect the Meta-data discovery logs:
1. In the J2C Bean Wizard :
-Set the Logging Level property to 'SEVERE' (which is the default value as well)
-Set the Log file output location to Output location where the JDBCMetadataDiscovery log
is created. Default value is the .metadata directory of the workspace,Specify a different
output location
2. Recreate the issue.
3. Compress and provide the contents of the ,metadata directory
Troubleshooting Runtime Issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues at runtime using WebSphere Application Server runtime:
Adapter version at runtime:
The adapter version can be found in ra.xml file :
If adapter is deployed with embedded mode: <WAS root dir>\profiles\<profile>\installedApps\<CellName>\<AdapterApp>.ear\<AdapterRAR>\META-INF\ra.xml
If adapter is deployed with standalone mode: <WAS root dir>\profiles\<profile>\installedConnectors\<AdapterRAR>\META-INF\ra.xml
Project Interchange:
Steps to export the Project Interchange:
1. In the Project Explorer, right-click the project that you want to export, and select Export > Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Logs/Traces:
SystemOut and trace logs:
Following are the steps to enable and collect SystemOut.log and trace.logs at runtime:
1. In the navigation pane of the Administrative console, click Servers > WebSphere application servers.
2. Click the name of the server that you want to work with.
3. Under Troubleshooting, click Logging and tracing.
4. Click Change Log Detail Levels.
5. Specify when you want the change to take effect:
- For a static change to the configuration, click the Configuration tab.
- For a dynamic change to the configuration, click the Runtime tab.
6. Set the logging level : that is com.ibm.j2ca.*='all' to capture the detailed level logs/traces.
7. Recreate the issue.
8. Collect the SystemOut.log, System.Err, and the trace.log files located for example in the <install_root>/profiles/profile_name/logs/server_name folder.
First-failure data capture (FFDC)logs:
FFDC feature runs in the background and collects events and errors that occur at runtime.
Following are the steps to collect FFDC logs at runtime:
1. Navigate to FFDC directory where all the FFDC logs are captured. For example:<WAS root dir>\profiles\<profile>\logs\ffdc
2. Compress and provide the contents of ffdc directory.
Other Details:
- Database used, including version
- JDBC driver used and version
- Data base definition
- Operating system with version on which JDBC adapter is running
- Operating system with version on which database is running
- Is JDBC adapter and database running on the same machine?
- Environment on which issue is seen (Production or Development/Test)
| WebSphere Enterprise Service Bus |
Please gather the following documentation for the WebSphere Adapter for JDBC running with WebSphere Integration Developer and WebSphere Enterprise Service Bus runtime:
Troubleshooting Development/Discovery time issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues during discovery process using WebSphere Integration Developer:
Adapter version being used during discovery:
1. Launch the External Service wizard: In the WebSphere Integration Developer, click File > New > External Service
2. Click Next.
3. In the Resource Adapter Selection window, find the IBM WebSphere Adapter for JDBC Software (IBM : version), where version is the version of the adapter being used.
Project Interchange:
Steps to export the Project Interchange:
1. In the WebSphere Integration Developer, Select File -Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Meta-data discovery logs:
Steps to enable and collect the Meta-data discovery logs:
1. Launch the External Service Wizard .
2. In the Discovery Configuration window, Select the 'Change logging properties for the wizard'
-Set the Logging Level property to 'SEVERE' (which is the default value as well)
-Set the Log file output location to Output location where the JDBCMetadataDiscovery log
is created. Default value is the .metadata directory of the workspace, specify a different
output location
3. Recreate the issue.
4. Compress and provide the contents of the ,metadata directory.
Troubleshooting Runtime Issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues at runtime using WebSphere Enterprise Service Bus runtime:
Adapter version at runtime:
The adapter version can be found in ra.xml file :
- If WebSphere Enterprise Service Bus is bundled with WebSphere Integration Developer: < WebSphere Integration Developer root dir>\pf\wps\installedApps\widCell\<AdapterApp>.ear\<AdapterApp>\<AdapterRAR>\META-INF\ra.xml
- If WebSphere Enterprise Service Bus is not bundled with WebSphere Integration Developer: <WebSphere Enterprise Service Bus root dir>\profiles\<profile>\installedApps\<CellName>\<AdapterApp>.ear\<AdapterRAR>\META-INF\ra.xm
Project Interchange:
Steps to export the Project Interchange:
1. In the WebSphere Integration Developer, Select File-Export
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Logs/Traces:
SystemOut and trace logs:
Following are the steps to enable and collect SystemOut.log and trace.logs at runtime:
1. In the navigation pane of the Administrative console, click Servers > WebSphere application servers.
2. Click the name of the server that you want to work with.
3. Under Troubleshooting, click Logging and tracing.
4. Click Change Log Detail Levels.
5. Specify when you want the change to take effect:
- For a static change to the configuration, click the Configuration tab.
- For a dynamic change to the configuration, click the Runtime tab.
6. Set the logging level : that is com.ibm.j2ca.*='all' to capture the detailed level logs/traces.
7. Recreate the issue.
8. Collect the SystemOut.log, System.Err, and the trace.log files located for example in the <install_root>/profiles/profile_name/logs/server_name folder.
First-failure data capture (FFDC)logs:
FFDC feature runs in the background and collects events and errors that occur at runtime.
Following are the steps to collect FFDC logs at runtime:
1. Navigate to FFDC directory where all the ffdc logs are captured. For example:<install root >\profiles\<profile>\logs\ffdc
2. Compress and provide the contents of ffdc directory.
Other Details:
- Database used, including version
- JDBC driver used and version
- Data base definition
- Operating system with version on which JDBC adapter is running
- Operating system with version on which database is running
- Is JDBC adapter and database running on the same machine?
- Environment on which issue is seen (Production or Development/Test)
| WebSphere Process Server |
Troubleshooting Development/Discovery time issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues during discovery process using WebSphere Integration Developer:
Adapter version being used during discovery:
1. Launch the External Service wizard: In the WebSphere Integration Developer, click File > New > External Service
2. Click Next.
3. In the Resource Adapter Selection window, find the IBM WebSphere Adapter for JDBC Software (IBM : version), where version is the version of the adapter being used.
Project Interchange:
Steps to export the Project Interchange:
1. In the WebSphere Integration Developer, Select File -Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Meta-data discovery logs:
Steps to enable and collect the Meta-data discovery logs:
1. Launch the External Service Wizard.
2. In the Discovery Configuration window, Select the 'Change logging properties for the wizard'
-Set the Logging Level property to 'SEVERE' (which is the default value as well)
-Set the Log file output location to Output location where the JDBCMetadataDiscovery log
is created. Default value is the .metadata directory of the workspace, Specify a different
output location
3. Recreate the issue.
4. Compress and provide the contents of the ,metadata directory.
Troubleshooting Runtime Issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues at runtime using WebSphere Process Server runtime:
Adapter version at runtime:
The adapter version can be found in ra.xml file:
- If WebSphere Process Server is bundled with WebSphere Integration Developer: < WebSphere Integration Developer root dir>\pf\wps\installedApps\widCell\<AdapterApp>.ear\<AdapterApp>\<AdapterRAR>\META-INF\ra.xml
- If WebSphere Process Server is not bundled with WebSphere Integration Developer: <WebSphere Process Server root dir>\profiles\<profile>\installedApps\<CellName>\<AdapterApp>.ear\<AdapterRAR>\META-INF\ra.xm
Project Interchange:
Steps to export the Project Interchange:
1. In the WebSphere Integration Developer , Select File-Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Logs/Traces:
SystemOut and trace logs:
Following are the steps to enable and collect SystemOut.log and trace.logs at runtime:
1. In the navigation pane of the Administrative console, click Servers > WebSphere Application Servers.
2. Click the name of the server that you want to work with.
3. Under Troubleshooting, click Logging and tracing.
4. Click Change Log Detail Levels.
5. Specify when you want the change to take effect:
- For a static change to the configuration, click the Configuration tab.
- For a dynamic change to the configuration, click the Runtime tab.
6. Set the logging level : that is com.ibm.j2ca.*='all' to capture the detailed level logs/traces
7. Recreate the issue.
8. Collect the SystemOut.log,System.Err,and the trace.log files located for example in the <install_root>/profiles/profile_name/logs/server_name folder.
First-failure data capture (FFDC) logs:
FFDC feature runs in the background and collects events and errors that occur at runtime.
Following are the steps to collect FFDC logs at runtime:
1. Navigate to ffdc directory where all the ffdc logs are captured. For example:<install root >\profiles\<profile>\logs\ffdc
2. Compress and provide the contents of ffdc directory.
Other Details:
- Database used, including version
- JDBC driver used and version
- Data base definition
- Operating system with version on which JDBC adapter is running
- Operating system with version on which database is running
- Is JDBC adapter and database running on the same machine?
- Environment on which issue is seen (Production or Development/Test)
| IBM Business Process Manager |
Troubleshooting Development/Discovery time issues:
Following is the information that needs to be gathered for troubleshooting data for WebSphere Adapter for JDBC issues during discovery process using IBM Integration Designer:
Adapter version being used during discovery:
1. Launch the External Service wizard: In IBM Integration Designer, click File > New > External Service
2. Click Next.
3. In the New External Service window, find the IBM WebSphere Adapter for JDBC Software (IBM : version), where version is the version of the adapter being used.
Project Interchange:
Steps to export the Project Interchange:
1. In the IBM Integration Designer, Select File -Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Meta-data discovery logs:
Steps to enable and collect the Meta-data discovery logs:
1. Launch the External Service Wizard.
2. In the Discovery Configuration window, Select the 'Change logging properties for the wizard'
-Set the Logging Level property to 'SEVERE' (which is the default value as well)
-Set the Log file output location to Output location where the JDBCMetadataDiscovery log
is created. Default value is the .metadata directory of the workspace, specify a different
output location
3. Recreate the issue.
4. Compress and provide the contents of the metadata directory.
Troubleshooting Runtime Issues:
Following is the information that needs to be gathered for troubleshooting data WebSphere Adapter for JDBC issues at runtime using IBM Business Process Manager runtime:
Adapter version at runtime:
The adapter version can be found in ra.xml file:
<IBM Business Process Manager root dir>\profiles\<profile>\installedApps\<CellName>\<AdapterApp>.ear\<AdapterRAR>\META-INF\ra.xm
Project Interchange:
Steps to export the Project Interchange:
1. In the IBM Integration Designer, Select File-Export.
2. Click Other > Project Interchange, and then click Next.
3. Select the projects that you want to export:
- Click Select All to select all projects in the window.
- Click Select Referenced to automatically select projects that are referenced by any of the currently selected projects.
4. In the To zip file field, enter the full path, including the ZIP file name, where you want to export the selected projects.
5. If you want to include derived files generated in the project, select the Include derived files check box.
6. Click Finish.
Logs/Traces:
SystemOut and trace logs:
Following are the steps to enable and collect SystemOut.log and trace.logs at runtime:
1. In the navigation pane of the Administrative console, click Servers > WebSphere Application Servers.
2. Click the name of the server that you want to work with.
3. Under Troubleshooting, click Logging and tracing.
4. Click Change Log Detail Levels.
5. Specify when you want the change to take effect:
- For a static change to the configuration, click the Configuration tab.
- For a dynamic change to the configuration, click the Runtime tab.
6. Set the logging level : that is com.ibm.j2ca.*='all' to capture the detailed level logs/traces
7. Recreate the issue.
8. Collect the SystemOut.log, System.Err, and the trace.log files located for example in the <install_root>/profiles/profile_name/logs/server_name folder.
First-failure data capture (FFDC) logs:
FFDC feature runs in the background and collects events and errors that occur at runtime.
Following are the steps to collect FFDC logs at runtime:
1. Navigate to ffdc directory where all the ffdc logs are captured. For example:<install root >\profiles\<profile>\logs\ffdc
2. Compress and provide the contents of ffdc directory.
Other Details:
- Database used, including version
- JDBC driver used and version
- Data base definition
- Operating system with version on which JDBC adapter is running
- Operating system with version on which database is running
- Is JDBC adapter and database running on the same machine?
- Environment on which issue is seen (Production or Development/Test)
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21439536