To resolve error 1:
1. Log on to the WAS Administration Console.
2. Expand Applications on the left-hand pane and click
Enterprise Applications.
3. Click WC_xxx, which is the WebSphere Commerce
Server in use.
4. Click Connector Modules > Enablement-JCAJMSConnector.rar >
Resource Adapter > J2C Connection Factories.
5. Ensure there is at least one entry. If not, click New to create
one. If there is an entry, click on the entry and follow step 7.
6. Enter Enablement-JCAJMSConnector.rar for the Name
field.
7. JNDI name should be eis/JCAJMS.
8. Click OK at the bottom of the page.
9. Save the configuration by clicking Save at the top.
10. Repeat steps 4 through 9 for all the other connectors according to the
following table:
| Resource Adapter name
| J2C Connection Factory name
| JNDI name
| | WC_xxx.Adapter for WebSphere MQ
| Enablement-JCAJMSConnector.rar
| eis/JCAJMS
| | WC_xxx.Adapter for WebSphere InterChange
Server
| Enablement-JCACrossWorldsConnector.rar
| eis/CWConnectionFactory
| | WC_xxx.File Adapter
| Enablement-JCAFileConnector.rar
| eis/JCAFile
| | WC_xxx.E-mal Adapter
| Enablement-JCAEMailConnector.rar
| eis/JCAEmail
| | WC_xxx.Sample Adapter
| Enablement-JCASampleConnector.rar
| eis/JCASample
|
11. Restart the WebSphere Commerce Server.
To resolve error 2:
Steps are required to configure WAS and WebSphere MQ to have WebSphere Commerce working with WebSphere MQ. Follow the
instructions outlined in the Addition Software Guide for more
details on required configuration.
For both error 1 and error 2, if these JCA connectors are not needed, (for
example, no e-mail, MQ functionality requirements, and so on), you can
consider disabling the Listener for WebSphere MQ and all the transports.
The Listener for WebSphere MQ is disabled by default. To enable or disable
the Listener for WebSphere MQ:
1. Stop WebSphere Commerce
2. Launch the WebSphere Commerce Configuration Manager
3. Enter your Configuration Manager user ID and password
4. Expand host_name > Commerce > Instance List >
instance > Components > Listener for WebSphere MQ
(TransportAdapter).
Where host_name is the short name of the machine running WebSphere Commerce and instance is the name of the WebSphere Commerce
instance.
5. Select Enable to enable WebSphere MQ, or otherwise clear it.
6. Click Apply.
7. Exit the WebSphere Commerce Configuration Manager.
To disable transports, which in turn use the JCA connectors:
1. Start WebSphere Commerce.
2. Log on to the WebSphere Commerce Administration Console.
3. Under Site profile, expand Configuration >Transport.
4. Select the transports with active statuses and click Change
Status.
5. The transport statuses should have turned to Inactive.
6. Log out from the Administration Console.
|
| Segment
| Product
| Component
| Platform
| Version
| Edition
|
| Commerce
| WebSphere Commerce Enterprise
| Migration
| AIX, i5/OS, Linux, Solaris, Windows
| 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
| Enterprise
|
| Commerce
| WebSphere Commerce Business Edition
| Migration
| AIX, i5/OS, Linux, Solaris, Windows
| 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 5.6.1.4
| Business Edition
|
| Commerce
| WebSphere Commerce - Express
| Migration
| i5/OS, Linux, Windows
| 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 5.6.1.4, 6.0, 6.0.0.1, 6.0.0.2,
6.0.0.3, 6.0.0.4
| Express
|
| Commerce
| WebSphere Commerce Developer Enterprise
| Migration
| Windows
| 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
| Enterprise
|
|
Current web document: http://www.ibm.com/support/docview.wss?uid=swg21237546
|