Implementation > Message recycling services > Configuration tasks > Creating an Application object to represent Messaging

Creating an Application object to represent Messaging

About the Messaging Application object

Prerequisites

Procedure

About the Messaging Application object

An Application object specifies the machine, protocols and access mechanisms that enable an Integrator to communicate with a Messaging Server.

Prerequisites

Before you create the Application object, you must create:

A CommNetwork object that defines the network protocol you use to communicate between Integrator and Messaging.
View dedicated topic
A Host object that defines characteristics of the machine where the Messaging Server instance runs.
View dedicated topic
Optionally, a HostGroup object that defines characteristics of the machine where the Messaging application is situated.
View dedicated topic

Procedure

In the Composer Integration Services workbench Transport tab, double-click a HostGroup to display a list of Hosts.
Right-click the Host where you want to define the Application. From the context menu, select Application.
Composer opens the Application properties window.
In the General tab, enter a name for the Application object.
In the Communication tab:
- In the left pane, add the CommNetwork that you created previously.
- Right-click the CommNetwork node and from the context menu, select Add a CommAdapter.
- Composer adds a CommAdapter node as a child node of the CommNetwork node in the left pane, and opens the CommAdapter properties window in the right pane.
- Composer adds a Configuration sub-tab for configuring the JMS CommAdapter.
- In the CommAdapter type field select JMS.
Complete the Configuration sub-tab.

View fields

Field	Description
Context factory name	Enter com.axway.xms.jms.XmsInitialContextFactory This is the value of the java.naming.factory.initial JNDI property which is used to access to the Axway Messaging server. This value varies depending on the JMS provider.
Provider URL	This is the host machine and port you use to access to the Axway Messaging server. This port information was specified when you installed the Axway Messaging server.
Connection factory name	Enter factory/QueueConnectionFactory. This is the factory name of Axway Messaging used to create connections. This value varies depending on the JMS provider.

Field

Description

Context factory name

Enter com.axway.xms.jms.XmsInitialContextFactory This is the value of the java.naming.factory.initial JNDI property which is used to access to the Axway Messaging server.

This value varies depending on the JMS provider.

Provider URL

This is the host machine and port you use to access to the Axway Messaging server. This port information was specified when you installed the Axway Messaging server.

Connection factory name

Enter factory/QueueConnectionFactory. This is the factory name of Axway Messaging used to create connections.

This value varies depending on the JMS provider.

Right-click the CommAdapter node in the left pane, and from the context menu, select Add a CommPoint.
Composer adds a CommPoint node as a child node of the CommAdapter node in the left pane, and opens the CommPoint properties window in the right pane.
Configure this CommPoint to represent the SWIFTNet Portal input queue: For the Destination value enter: queue/SWIFT_IN
Add a second CommPoint to represent the SWIFTNet Portal output queue: For the Destination value, enter: queue/SWIFT_OUT