Sending objects to Server

Purpose of sending objects to Server

Send to Server and Send to Server complete

Before sending an object to Server

Sending an object to Server

Results of the operation

Purpose

To execute an object, you must transfer it from Composer to at least one run-time environment. This operation is referred to as Send to Server.

The run-time environment corresponds to the Axway Server. To set up the run-time environment, you must define the Axway Server in the Topography layer and then send the Axway Server configuration to Server. When you send an Axway Serverto Server, Composer also sends all the objects used by that Server.

You can then send the following objects to Server on a given Axway Server:

• TopographyDiagram: sends to Server all Axway Servers on the Diagram
• Channel: sends all objects used by the Channel
• Integration-Services-Diagram: sends to Server all objects included in the Diagram
• Axway product-specific objects: refer to the product-specific documentation for details

In addition, you can send a ServerList to Server. Via a single operation, Composer sends to Server the configuration of all Servers included in the List.

Send to Server complete

Two Send to Server actions are available:

• Send to Server: only sends objects that are not already on a Server
• Send to Server complete: sends the object and all child objects to Server, even if the child objects are already on a Server in association with a different parent object. Use this command if you need to initialize your run-time environment and make sure that all the required objects are sent to Server on the Axway Server.

Before sending an object to Server

You can send to Server objects with the following life cycle statuses:

• Checked
• ReadyToSend
• Archived

Before you send an object to Server, complete the following steps:

1. Complete the definition of the object.
2. Check the object definition. Composer sets the object status to Checked and displays next to the object and all objects that it uses.
3. Optionally, set the object status to ReadyToSend. Select Other Actions / Ready to send from the File menu or from the contextual menu for this object. For details, see Making objects ready to send to Server.

Sending objects to Server

Depending on the Axway Server, you can select to send an object to a single Serveror to multiple Servers.

The way you send objects to Server depends on whether the object is linked to a given Axway Server or not. For example, if an Application is based on anAxway Server and uses its CommAdapter, then when you send this Application to Server, Composer sends the Application to the appropriate Axway Server.

On the other hand, if the object you select to send to Server has no link with a specific Axway Server, you must select the Server, as described next.

Sending objects that are not linked to a given Axway Server

1. Select the object from the left pane and then select Other Actions / Send to Server from the File menu. Alternatively, right-click the object and select Other Actions / Send to Server from the contextualmenu.
   The Select Axway Server(s) dialog box opens.
2. The dialog boxdisplays the list of authorized Servers. Select the Server(s) where you want to execute the object.

3. Click OK to send the object to the selected Server(s).

Results of the Send to Server operation

When you send an object to Server, the results of the operation are as follows.

1. The software creates a broadcast that sends the object and all the objects it uses to the selected Server(s). Until the broadcast operation is complete, the status of all objects involved in the broadcast is set to Broadcast in Progress.
2. When the broadcast is completed, the software resets the object status to indicate the result of the operation. If the send to Server operation:

• Is successful on all Servers, Composer sets the object status to Committed, or to ToBeCommitted in the case of Transfer CFT,and displays next to objects that are on a Server.
• Fails on all Servers, the status of all objects is reset to Checked.
• Is successful on one Server, but not on all Servers, the status of the broadcast transaction is set to Wait for User Action. The status of all objects involved in the broadcast remains Broadcast in Progress. You must then cancel, restart or force the broadcast on the Server in error. For details, see Using the Broadcast Browser

3. The results of the operation are displayed on the History tab of the Broadcast Browser. This tab provides access to a log file.

Send to Server on two Axway Servers

If a Channel connects two Applications that are based on underlying Servers, the Applications are linked to the Servers by a dotted line.

When you send the Channel to Server, Composer:

• Identifies the two Servers linked to the Applications
• Sends the Channel and associated objects to Server on both identified Servers

If the Send to Server operation:

• Is successful on both Servers, the object status passes to Committed or ToBeCommitted.
• Fails on both Servers, the object status returns to Checked.
• Is successful on one Server but not the other, the object status passes to Broadcast in Progress and the broadcast status is set to Wait for User Action. Use the Broadcast Browser to restart, cancel or force the broadcast operation on the Server in error.