The enterprise service discovery wizard and the assembly editor that simplify the development of applications through generating artifacts, also create references to the generated artifacts. When you refactor the artifacts, either through the refactoring user interface or manually moving, renaming and deleting objects yourself, these references sometimes will require revisions, which are listed in this section.
Correction: The necessary updates will be performed by the refactoring operation and the results can be viewed in the refactoring wizard's Details view on the Preview page.
Correction: The necessary updates will be performed by the refactoring operation and the results can be viewed in the refactoring wizard's Details view on the Preview page. Undeploy the current instance of the resource adapter and redeploy.
Correction: The necessary updates will be performed by the refactoring operation and the results can be viewed in the refactoring wizard's Details view on the Preview page.
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithExport/NewExportLocation/ExportName_RECEIVE_D" type="javax.jms.Queue" usage="send" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithExport/NewExportLocation/ExportName_SEND_D" type="javax.jms.Queue" usage="receive" />
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithExport/NewExportName_RECEIVE_D" type="javax.jms.Queue" usage="send" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithExport/NewExportName_SEND_D" type="javax.jms.Queue" usage="receive" />
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="NewModuleWithExport/ExportName_RECEIVE_D" type="javax.jms.Queue" usage="send" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="NewModuleWithExport/ExportName_SEND_D" type="javax.jms.Queue" usage="receive" />
Description: You have an import with a JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that export has to have the same interface as import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import is moved to another folder within the module, the destinations' JNDI lookup name value that might be referenced by the JMS export becomes invalid.
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithImport/NewImportLocation/ImportName_SEND_D" type="javax.jms.Queue" usage="receive" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithImport/NewImportLocation/ImportName_RECEIVE_D" type="javax.jms.Queue" usage="send" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
Description: You have an import with a JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that the export has to have the same interface as the import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import name is changed, the destinations' JNDI lookup name value that might be referenced by the JMS export becomes invalid.
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithImport/NewImportName_SEND_D" type="javax.jms.Queue" usage="receive" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="ModuleWithImport/NewImportName_RECEIVE_D" type="javax.jms.Queue" usage="send" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
Description: You have an import with a JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that export has to have the same interface as import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import's module name is changed, the destinations' JNDI lookup name value that might be referenced by the JMS export becomes invalid.
<destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="NewModuleWithImport/ImportName_SEND_D" type="javax.jms.Queue" usage="receive" /> <destination implType="com.ibm.ws.sib.api.jms.impl.JmsQueueImpl" target="NewModuleWithImport/ImportName_RECEIVE_D" type="javax.jms.Queue" usage="send" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
Correction: The necessary updates will be performed by the refactoring operation and the results can be viewed in the refactoring wizard's Details view on the Preview page.
<send target="ModuleWithExport/NewExportLocation/ExportName_MQ_RECEIVE_D" type="javax.jms.Queue" /> <receive target="ModuleWithExport/NewExportLocation/ExportName_MQ_SEND_D" type="javax.jms.Queue" />
<send target="ModuleWithExport/NewExportName_MQ_RECEIVE_D" type="javax.jms.Queue" /> <receive target="ModuleWithExport/NewExportName_MQ_SEND_D" type="javax.jms.Queue" />
<send target="NewModuleWithExport/ExportName_MQ_RECEIVE_D" type="javax.jms.Queue" /> <receive target="NewModuleWithExport/ExportName_MQ_SEND_D" type="javax.jms.Queue" />
Description: You have an import with an MQ JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that the export has to have the same interface as import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import is moved to another folder within the module, the destinations' JNDI lookup name value that might be referenced by the MQ JMS export becomes invalid.
<receive target="ModuleWithImport/NewImportLocation/ImportName_MQ_SEND_D" type="javax.jms.Queue" /> <send target="ModuleWithImport/NewImportLocation/ImportName_MQ_RECEIVE_D" type="javax.jms.Queue" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
Description: You have an import with a MQ JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that the export has to have the same interface as the import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import name is changed, the destinations' JNDI lookup name value that might be referenced by the MQ JMS export becomes invalid.
<receive target="ModuleWithImport/NewImportName_MQ_SEND_D" type="javax.jms.Queue" /> <send target="ModuleWithImport/NewImportName_MQ_RECEIVE_D" type="javax.jms.Queue" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
Description: You have an import with an MQ JMS binding and you deployed it to the server. You want to have an export that will communicate with the import. Note that the export has to have the same interface as import. You update the export's destination JNDI names with the JNDI names that the import is using. You retrieve the destination JNDI names from the import's Summary page of the properties view. Then you deploy the export and it will communicate with the import.
Problem: When the import's module name is changed, the destinations' JNDI lookup name value that might be referenced by the MQ JMS export becomes invalid.
<receive target="NewModuleWithImport/NewImportName_MQ_SEND_D" type="javax.jms.Queue" /> <send target="NewModuleWithImport/NewImportName_MQ_RECEIVE_D" type="javax.jms.Queue" />Then you redeploy. If you did not deploy originally, then the correction is simple. You refactor the import and the export is updated. Now you are ready to deploy and test.
In the case of a Java™ Message Service (JMS) binding where you created an import by dragging and dropping an export, there is a matching export for that import. Re-create the import and export pair if one of them is deleted.
A shortcut often used to create an import with a JMS binding is to drag an export with a JMS binding from one module into the module where you want to create the import. However, if you refactor the interface of the original export, it will not modify the interface of the import accordingly. This section describes the manual steps you would need to perform to correct the interface of the import.
Moving an export with a JMS binding to another module to create an import (drag and drop scenario)