These procedures build and deploy Deployment Profiles that map the resources named in the cmSub_DLQ and cmSub_ProcErrors Connectivity Maps to the externals in an Environment. The cmSub_DLQ map uses a BP to receive messages from the JMS topic EX_DEADLETTER (sometimes called the “dead letter queue”) and write them to a file. The cmSub_ProcErrors map uses a BP to receive messages from the JMS topic EX_PROCESSEDERRORS and write them to a file.
With the Project Explorer tab active, in the project tree, open the eXchange⇒Errors project.
If you have not already done so, start the domain associated with the Environment’s Integration Server.
In the project tree, under eXchange⇒Errors⇒Sub_DLQ, open cmSub_DLQ and make sure that its File eWay is configured appropriately for your operating environment.
Right-click the Sub_DLQ project.
On the context menu, point to New and click Deployment Profile
In the Create Deployment Profile dialog box, name the Deployment Profile to dpErrorsDLQ and point it at the correct Environment.
Make sure that it is referencing cmSub_DLQ (the Connectivity Map for the “dead letter” topic), and then click OK.
See Figure 4–25.
In the Deployment Editor, click Automap to map the two components to their respective external systems, and then click Build.
See Figure 4–26.
After the build step completes successfully (creating the EAR file), click Deploy.
The Sub_DLQ project is built and deployed. At runtime, any undeliverable messages that cannot be processed are copied and written to a file.
In the project tree, under eXchange⇒Errors⇒Sub_ProcErrors, open cmSub_ProcErrors and make sure that its File eWay is configured appropriately for your operating environment.
Right-click the Sub_ProcErrors project.
On the context menu, point to New and click Deployment Profile.
In the Create Deployment Profile dialog box, name the Deployment Profile to dpErrorsProc and point it at the correct Environment.
Make sure that it is referencing cmSub_ProcErrors (the Connectivity Map for the “processed errors” topic), and then click OK.
In the Deployment Editor, click Automap to map the two components to their respective external systems, and then click Build.
After the build step completes successfully (creating the EAR file), click Deploy.
See Figure 4–27.
The Sub_ProcErrors project is built and deployed. At runtime, undeliverable messages written to the processed-errors topic are copied and written to a file.