Enabling a JMS router for an existing component
You can enable a JMS router for an existing HCL Commerce component.
Note: To enable this router by using
the following steps, you modify base packages, such as a JAR file,
for your HCL Commerce instance. Whenever maintenance is applied
to your HCL Commerce instance, such as fix packs or APARs, you
might need to reapply your changes to the base assets to maintain
the enablement of your router.
Procedure
- Import the existing EJB component into your workspace by
importing the following files into HCL Commerce Developer:
- component_name-Server.jar
- component_nameServicesHTTPInterface.war
- If you want to test the changes by using the HCL Commerce test server, import the component_name-Server.jar file corresponding to the database type used by HCL Commerce Developer.
- Otherwise, import the component_name-Server.jar file corresponding to the database type used by your production environment.
- Add the component_name-Server.jar file
as a module to the HCL Commerce EAR.Note: Perform this step even though the binary exists. This step replaces the existing binary with your own.
- Generate the HTTP/JMS
router modules for the component_name-Server.jar project,
where:
- Create the JMS queues and activation specs.Create the following items:
- The inbound JMS queue and its QCF (queue connection factory).
- The outbound QCF.
- The activation spec.
- Deploy your changes by Deploying the component facade. Ensure that you change the data source JNDI name of the component_name-Server.jar file when the changes are deployed to the runtime environment.