Using the Send Master Utility

This chapter discusses the Send Master utility and describes how to:

• Start Send Master.

• Navigate in Send Master.

• Set display preferences.

• Set HTTP proxy and keystore options.

• Create Send Master projects.

• Enter header information in Send Master projects.

• Add input files to projects.

• Use input file projects.

• Use Integration Broker projects.

• Use EIP Test (Batch EIP) projects.

• Use MQSeries projects.

• Work with groups of projects.

• Ping remote nodes.

• View processing performance statistics.

• Export request messages for viewing.

• Allocate additional memory to accommodate posting large files.

Understanding Send Master

The Send Master utility enables you to test PeopleSoft Integration Broker messaging interactions with PeopleSoft and third-party web servers, application servers, and integration gateways. It can test listening connector functionality, target connector functionality, connector introspection and transactions.

Send Master enables you to post any data format, including the PeopleSoft Multipurpose Internet Mail Extensions (MIME) message format, to web and application servers over HTTP and HTTPS. You can also use Send Master to simultaneously test groups of different types of messages, as well as stress test your system.

Send Master also enables you to perform Get functions and to ping application messaging gateways and third-party servers.

Send Master is installed with the PeopleSoft Pure Internet Architecture on Windows and UNIX systems and is delivered as part of the Integration Broker Connector SDK. Send Master is also delivered as a Windows stand-alone batch file. The stand alone version enables you to use the utility without having to install an integration gateway.

Starting Send Master

You can start Send Master from the Integration Broker SDK or as a stand-alone version.

Starting Send Master from the Integration Broker SDK

The location of Send Master in the Integration Broker SDK is <PS_HOME>\webserv\<DOMAIN>.

The name of the Send Master startup script on Windows is StartSendMaster.bat; the name of the script on UNIX is StartSendMaster.sh.

Starting the Stand-Alone Version of Send Master

The standalone version of Send Master is located in the <PS_HOME>\Sendmaster folder, and is named StartSendMaster.bat. If you attempt to launch the batch file and Send Master does not open, you most likely need to set PS_HOME in the environment variables on your machine.

To set PS_HOME in the environment variables:

1. Close any DOS windows that might be open.

2. Right-click My Computer and click Properties.

   The System Properties dialog appears.

3. Click the Advanced tab.

4. In the Environment Variables section, click Environment Variables.

5. In the User variables for <user name> section, click New.

   A New User Variable dialog box appears.

6. In the Variable Name field enter PS_HOME.

7. In the Variable Value field, enter the path to your <PS_HOME> directory (for example, c:\PT846).

8. Click OK.

   The PS_HOME variable name and value appears in the User variables for <user name> section.

9. Click OK again and navigate to the standalone version of Send Master and double-click the StartSendMaster.bat file.

Navigating in Send Master

Send Master features drop-down menus that you use to create, save and delete projects, and to change your user and display preferences. It also features Project and Batch Processing work spaces where you specify project parameters, view output, and so on.

You can navigate in Send Master using:

• Send Master menus.

• The Project work space.

• The Send Master Batch work space.

Using Send Master Menus

Send Master features two menus. This table describes the menus:

Using the Project Work Space

When you open Send Master, the system displays the Project work space. You use the Project work space to define, modify, and test a Send Master project.

The Send Master Project work space features the Project Definitions section, the Input Information section, and the Output Information section. No fields or buttons are enabled until you define or select a project.

Project Definition Section

Use the Project Definition section to add and define a new Send Master project. The information that you specify in this section includes the web server URL used in conjunction with Post and Get methods to work with messages.

Input Information Section

Depending on the type of task that you are performing with Send Master, the Input Information section enables you to create and format MIME messages, as well as specify input files, destination nodes. and more

You need to know the message format that the connectors, application servers, and so forth are expecting, and then incorporate the appropriate tags and components into the message body. For example, to communicate with PeopleSoft systems, you must specify the message name and requesting node.

This section features a toolbar with the following buttons:

Output Information Section

The Output Information section displays information that the system returns when you perform a GET or POST on a web server.

When you work with MIME messages, you can use the provided View drop-down list and choose whether to view the entire raw message response, message metadata, or individual sections of the response.

When you work with message types other than MIME, you can view the raw message response only.

This section features a toolbar with the following buttons:

Using the Send Master Batch Work Space

The Send Master Batch work space enables you to test groups of projects, as well as stress test a project or group of projects. You can access the Batch Processing work space by starting Send Master and selecting File, Batch Processing.

The Batch Processing work space features these sections:

• Group Definition

• Group Projects

• Completed Projects Output

• Output Information

Group Definitions Section

You use the Group Definitions section to create, select, or delete a group of projects. You can also use this section to specify whether to run the projects in the group all at once, in sequence, or at intervals that you specify.

This section features these two buttons:

Group Projects Section

You use the Group Projects section to add, remove, and arrange projects in a group. For each project that you add to a group, you can select the method to invoke, such as GET or POST. You can also specify the number of times to run each project, and specify whether to run project instances all at once, in sequence, or at defined intervals.

This section features a toolbar with the following buttons:

Completed Projects Output Section

The Completed Projects Output section provides processing information about each project in a group, including the number of project instances processed, total time to process all project instances, the average amount of time to process a project instance, and more.

This section features a toolbar with the following buttons:

Output Information Section

The Output Information section displays information that the system returns when you perform a Get or Post on a web server.

When you work with MIME messages, you can use the View drop-down list to view the entire raw message response, message metadata, or individual sections of the response.

When you are working with message types other than MIME, you can view the raw message response only.

This section features a toolbar with the following buttons:

Setting Display Preferences

You can set these display preferences for Send Master:

• Display font, size, and color.

• Background color.

• Word-wrapping options.

To set display preferences, use the Display tab of the Preferences dialog box. To access this box, select File, Preference and click the Display tab.

Setting the Display Font, Size and Color

To set the display font, size and color:

1. Access the Preferences dialog box and click the Display tab.

2. Set the display font, size and color.

   • To set the display font, in the Fonts section, from the Font drop-down list, select a font style.

   • To set the font size, in the field next to the font style, enter a font size.

   • To set the text color, in the Text Color field, click the color block.

     The Choose the Text Color box appears, from which you can select a color for the font.

3. Click OK to save the changes.

Setting the Background Color

This section describes how to set the background color of Send Master work spaces and sections.

To set the background color:

1. Access the Preferences dialog box and click the Display tab.

2. In the Font section, in the Background Color field, click the color block.

   The Choose the Text Background Color box appears, from which you can select a background color and click OK.

3. Click OK to save the changes.

Setting Word-Wrapping Options

You can enable or disable word wrapping in Send Master input and output sections.

To set word-wrapping options:

1. Access the Preferences dialog box and click the Display tab.

2. In the Word Wrap section, enable or disable word wrapping.

   • To enable word wrapping in input windows, select Input Text Windows.

   • To enable word wrapping in output windows, select the Output Text Windows.

3. Click OK to save the changes.

Setting HTTP Proxy and Keystore Options

You can set up HTTP proxy and keystore options for use with Send Master. You set these options on the HTTP tab of the Preferences dialog box. To access the dialog box, select File, Preferences .

Specifying HTTP Proxy Settings

To specify HTTP proxy settings for Send Master:

1. Access the Preferences dialog box and click the HTTP tab.

2. In the Proxy section of the dialog box, specify the following information:

   1. In the Host field enter the name of the proxy host.

   2. In the Port field, enter the appropriate port number.

3. Click the OK button.

Specifying Keystore Settings

To specify keystore settings for Send Master:

1. Access the Preferences dialog box and click the HTTP tab.

2. In the Keystore section of the dialog box, specify the following information:

   1. In the Certificate Alias field, enter the certificate alias.

   2. In the Certificate Password field, enter the encrypted certificate password.

   3. In the Keystore File field, click the folder icon to specify a keystore file.

   4. In the Keystore Password field, enter the encrypted password for the keystore.

3. Click the OK button.

Setting Batch Processing Options

You use the Batch Processing tab to set output directory options related to the projects with which you work in the Batch work space.

Directory	Specify the output directory for Batch project results.
Create if not found	Select this check box to create the directory specified in the Directory field if it does not exist.
Overwrite files	Select this check box to overwrite files of the same name in the output directory.
Delete directory before each run	Select this check box to delete the contents of the directory before you run each batch project.
Delete directory on exit	Select this check box to delete the contents of the directory each time that you exit the Batch work space.

Creating Send Master Projects

To test message and connector processing using Send Master, you use Send Master projects. A Send Master project is a collection of message components, values and parameters that defines what you want to test and how you want to test it.

Understanding Send Master Project Types

This table describes Send Master project types.

The following table describes the type of project to use based on the type of communication that you want to test.

Creating Send Master Projects

To create a Send Master project:

1. Launch Send Master.

2. Select File, New Project.

3. In the Project Name field, enter a name for the project.

4. From the Project Type drop-down list, select one of the following options:

   • Input File

   • 8.4 Integration Broker (MIME)

   • 8.4 Integration Broker (XML)

   • 8.4 EIP Testing (Batch EIP)

   • 8.4 MQSeries

5. Click the OK button.

   The system populates the Input Information section with various tabs, based on the project type that you selected.

6. In the Server URL field, enter the server URL of the server with which to communicate.

   Note. This field is not used for MQSeries projects.

7. In the Time Out field, enter a timeout value.

   The timeout value determines the amount of time Send Master attempts to process a message. If the request does not complete in the time specified, processing stops. Usual timeout is about 60 seconds. The default is 0 (zero), meaning there is no timeout.

8. In the Headers box, enter pertinent HTTP header information for the message.

9. Select File, Save Project.

   Note. This field is not used for MQSeries projects.

The project name appears in the Project field and the type of the project appears in parentheses next to the project name. The content of the work space varies, based on the project type selected.

See Also

Understanding Send Master Project Types

Using Input File Projects

Using Integration Broker Projects

Using EIP Testing Projects

Using MQSeries Projects

Entering Header Information in Send Master Projects

Send Master enables you to specify HTTP, IBInfo, and connector headers. These headers are used in association with the following project types:

• Input File

• Integration Broker (MIME)

• Integration Broker (XML

• MQSeries

Use the information in the following table as a guide for entering header information in Send Master.

Adding Input Files to Projects

The information in this section applies to all project types except for the EIP Testing project type.

When working with EIP Testing projects, you specify file input and file output directories.

See Specifying File Input and File Output Directories.

To add an input file to a project:

1. In the Input Information section, click the Input File tab (if necessary).

2. (Optional.) Select Base64 encode/compress to enable base64 encoding and compression.

   This option is not available when working with MQSeries projects.

3. (Optional.) Select Non Repudiation to enable nonrepudiation.

   This option is not available when working with MQSeries projects.

4. In the text box, compose the content of the message in the area provided, or import a file.

   To import a file, click the Open File button and select a file. The name of the imported file appears under the Input Information section.

5. Modify the message if necessary.

6. Click the Save button on the toolbar within the Input Information section.

7. Select File, Save Project.

After you create an input file, you can modify and format message content. Use the following tips when you work with input files. Note that all buttons referenced appear on the toolbar located within the Input Information section.

• Use the Refresh button to revert to the last saved version of the input file.

• If the message content is XML, use the Format button to indent lines of code.

• Use the Delete button to delete the contents of the section.

Using Input File Projects

This section describes using Input File projects and describes how to:

• Create Input File project types.

• Create and add input files to input file projects.

• Post the input file projects to a web server.

See Also

Understanding Send Master Project Types

Creating Input File Project Types

The first step to using an input file project is creating the Input File project type. Information about how to complete this task is provided earlier in this chapter.

See Creating Send Master Projects.

Creating and Adding Input Files to Input File Projects

Information about creating and adding an input file to a project is provided earlier in this chapter.

See Adding Input Files to Projects.

Posting Input File Projects to Web Servers

After you create the Input File project type, add the input file to the project, and then click the Post button to post the file to the server.

Any server response to the message that you post appears in the Output Information section.

Using Integration Broker Projects

This section provides an overview of Integration Broker project types, and describes how to:

• Create Integration Broker project types (MIME and XML).

• Add header information to the project.

• Add an input file to the project.

• Specify connector information for the project.

• Post the project data to a web server.

Understanding Integration Broker Project Types

You can create two types of Integration Broker projects—an Integration Broker MIME project or an Integration Broker XML project.

When you create Integration Broker MIME projects, you use the Input Information section of the work space to supply Send Master with information to build the IBInfo section of the message. In addition, you also use the section to specify connector information, add cookie information, specify destination nodes, and so on. PeopleSoft Integration Broker uses the information to build the MIME structure in messages that are required to communicate with the PeopleSoft listening connector

For Integration Broker XML projects, Integration Broker uses the information to build the IBRequest.

See Also

Understanding Send Master Project Types

Understanding Input Information for Integration Broker Projects

This section discusses the options you can define when working with Integration Broker MIME and Integration Broker XML project types.

Header Information Tab

Use the Header Information tab to create message headers. This table describes the controls on the tab:

Headers Cont. Tab

You can work with the following controls on this tab.

Note. This tab appears only when you are working with Integration Broker MIME projects.

Input File Tab

Use this tab to add input files. You can also use this tab to apply nonrepudiation, and base64 encoding and compression. This section describes the controls featured on this tab. Controls that appear on this tab that are not described in this section are documented earlier in this chapter.

See Navigating in Send Master.

This table describes the controls on the Input File tab:

Connector Tab

This tab appears only when you are working with the Integration Broker MIME project type.

The Connector tab enables you to perform connector introspection on the integration gateway so you can select from all target connectors loaded on the integration gateway. No fields or controls are active on this tab until you enter connector data and select a target connector with which to work

After you select a target connector, you can select specific target connector properties to use and define those property values. In addition, you can specify and define headers and fields that a selected connector needs to be able to pass information and process message requests.

Note. Header properties with which you work on this tab correspond to properties with the property IDHeaders in PeopleSoft Pure Internet Architecture. Field properties with which you work on this tab correspond to any property ID other than Header in PeopleSoft Pure Internet Architecture.

This table describes the controls on the Connector tab:

Creating Integration Broker Project Types

The first step to using an Integration Broker project is creating the Integration Broker project type. Information about how to complete this task is provided earlier in this chapter.

See Creating Send Master Projects.

Adding PeopleSoft Header Information to Integration Broker Projects

To add PeopleSoft header information to the project:

1. In the Input Information section, select the Header Information tab, if it is not already selected:

2. Complete the following required fields:

   • Requesting Node

   • Message Name

   • Message Type

3. Enter values in any of the remaining optional fields as appropriate for your project.

4. (Optional.) Click the Headers Cont. tab to add cookie information or to gather messaging statistics.

See Also

Entering Header Information in Send Master Projects

Adding Input Files to Integration Broker Projects

Information about creating and adding an input file to a project is provided earlier in this chapter.

See Adding Input Files to Projects.

Specifying Connector Information for Integration Broker Projects

This section discusses how to specify connector information for Integration Broker MIME projects.

To specify connector information for a project, use the Connector tab in the Input Information section of the Project work space. No fields or controls are active on the tab until you introspect target connector data and select a target connector with which to work.

As noted earlier in this section, header properties with which you work on the Connector tab correspond to properties with the property IDHeaders in the PeopleSoft Pure Internet Architecture. Field properties with which you work on this tab correspond to any property ID other than Header in the PeopleSoft Pure Internet Architecture.

Selecting Target Connectors

To select a target connector:

1. From an open Integration Broker MIME project, in the Input Information section, click the Connector tab.

2. Click the Load Introspection Data button.

3. From the Connector drop-down list, select a connector.

4. (Optional.) In the Remote URL field, enter a URL to redirect the message to a different URL than that specified in the Server URL field in the Project Definitions section.

Adding Connector Header Properties

To add connector headers properties:

1. Click the Headers subtab under the Remote URL field.

2. To add all required header properties for the selected connector, click the Add All Required Headers and Their Default Values button.

   All required header properties and their default values, if they exist, appear in the Headers box.

3. To add more header properties:

   1. In the Connector Header section, from the Header drop-down list, select a header property and click the Add Selected Header and Default Value button.

      When you select a header property from the list, its default value, if any, appears in the Value field. Click the Value drop-down list to view all possible values for the property.

   2. Click the Add Selected Header and Default Value button to add the property.

      The header property and its default value, if any, appear in the Headers box.

4. To change the value of a header property:

   1. In the Headers box, select the header property whose value you want to change.

   2. In the Value field, enter the new value to assign.

      Use the Value drop-down list in the Connector Headers section to view possible values and verify the format to enter.

   3. Click the Update Selected Value in List button to apply the new value.

5. To delete a header property, in the Headers box, select the property to delete and click the Delete button.

6. Save the project.

Adding Connector Field Properties

To add connector field properties:

1. Click the Fields subtab under the Remote URL field.

2. To add all required field properties for the connector, click the Add All Required Fields and Their Default Values button.

   All required field properties and their default values, if they exist, appear in the Fields box.

3. To add more field properties:

   1. In the Connector Fields section, from the Field drop-down list, select a field property, and click the Add Selected Fields and Default Value button.

      When you select a property from the drop-down list, its default value, if any, appears in the Value field. Click the Value drop-down list to view all possible values for the property.

   2. Click the Add Selected Field and Default Value button to add the property.

      The field property and its default value, if one exists, appears in the Fields box.

4. To change the value of a field property:

   1. In the Fields box, select the field property whose value you want to change.

   2. In the Value field, enter the new value.

      Use the Value drop-down list in the Connector Fields section to view possible values and verify the format to enter.

   3. Click the Update Selected Value in List button to apply the new value.

5. To delete a field property, in the Fields box, select the property to delete and click the Delete button.

6. Save the project.

Posting Integration Broker Projects

To post Integration Broker MIME or Integration Broker XML projects to web servers, click the Post button.

Viewing Output from Integration Broker Projects

When you POST a message using the Integration Broker project type, the system generates a MIME response message. If you POST data to a PeopleSoft listening connector, the MIME response message appears in the Output Information section of the Project work space.

Using EIP Testing Projects

This section describes how to:

• Create EIP Testing projects.

• Specify file input and output directories.

• Override requesting and destination nodes.

• Start batch processing.

• Use the Batch Project Executor Command Line Tool

Creating EIP Testing Project Types

The first step to using an EIP Testing project is creating the EIP Testing (Batch EIP) project type. To create a project, select File, New Project. Information about creating projects is provided earlier in this chapter.

See Creating Send Master Projects.

Specifying File Input and File Output Directories

To add input files to this project type, you specify the directory location where the files reside.

To specify input files for EIP Testing projects:

1. In the Input Information section, in the Input Directory field, select the location of the input files.

2. In the Output Directory field, select the location where the output files should be written.

3. (Optional.) Select Create If Not Found to create the input and output directories, if they do not exist.

4. (Optional.) Select Overwrite File to direct Send Master to overwrite any output files that exist with the same names.

5. Select File, Save Project.

Overriding Requesting and Destination Nodes

Send Master reads the request and destination node information from the input files. However, you can override the node information:

To override the requesting and destination node information specified in the input files:

1. Open an EIP Testing project.

2. In the Input Information section, in the Optional Overrides section, enter a new requesting node name in the Requesting Node field.

3. To override the destination node , in the Optional Overrides section, enter a new destination node name in the Destination Node field.

4. Select File, Save Project.

Posting EIP Testing Projects

To post the files in an EIP Testing project, open the project and click the Post button.

Viewing Output from EIP Testing Projects

To view the output from EIP Testing projects, navigate to the output directory that you specified on the Headers tab in the Input Information section. You can also view output in Send Master in the Output Information section of the Project work space.

Using the Batch Project Executor

The Batch Project Executor enables you to use the functionality of the EIP Testing project type from a command line tool. This section discusses the Batch Project Executor tool, including its:

• Usage

• Syntax

• Parameters

Usage

The standard usage of the Batch Project Executor command line tool is:

BatchProjectExecutor [-options]

Syntax

The syntax for executing a batch project is:

BatchProjectExecutor -in "C:\temp\input" <keyword>-out</keyword>
"C:\temp\output" <keyword>-url</keyword> "http://localhost/PSIGW
/PeopleSoftListeningConnector" <keyword>-result</keyword> "C:\temp
\output\result.txt"

Parameters

The following table describes the parameters you can pass to the Batch Project Executor.

Sample Output

The following example shows successful output:

<?xml version="1.0"?>
<success>
    <request elapse="1.953 (s)" end="02:33:55.177" filename=
       "20030519T130405.request" id="1" start="02:33:53.224" 
       success="true"/><request elapse="0.201 (s)" end="02:33:55.408" 
       filename="20030519T150417.request" id="2" start="02:33:55.207" 
       success="true"/>
    <request elapse="0.220 (s)" end="02:33:55.638" filename="20030520T150406.
       request" id="3" start="02:33:55.418" success="true"/>
    <request elapse="0.190 (s)" end="02:33:55.828" filename=
       "20030519T150406.request" id="4" start="02:33:55.638" success="false">
       <![CDATA[Error communicating with server: Connection refused: connect]]>
    </request>
</success>

The following example shows a failure:

<?xml version="1.0"?>
<failure>
    <![CDATA[Error while initializing: Invalid output directory: 
    C:\temp\output]]>

Using MQSeries Projects

This section discusses how to:

• Create MQSeries projects.

• Add header information to MQSeries projects.

• Add input files MQSeries projects.

• Post MQSeries projects to queues.

Understanding MQSeries Projects

You can use Send Master to create MQSeries project types and test posting synchronous and asynchronous messages to MQSeries queues.

Before you attempt to post messages to an MQSeries queue, verify that the following Java Archive (JAR) files are installed, and that you have added them to the CLASSPATH in the StartSendMaster.bat file or the StartSendMaster.sh file. These files are installed as part of the MQSeries installation.

• com.ibm.mq.iiop.jar

• com.ibm.mq.jar

• com.ibm.mqbind.jar

• com.ibm.mqjms.jar

• fscontext.jar

• jms.jar

• jndi.jar

• providerutil.jar

See See the IBM MQSeries documentation.

Understanding Input Information for MQSeries Projects

This section discusses the options you can define when working with an MQSeries project type.

Headers Tab

Use the Headers tab to specify header information for MQSeries messages. The following table describes elements on this tab:

Creating MQSeries Project Types

The first step to using an MQSeries project is creating the MQSeries project type. To create a project, from the Send Master menu, select File, New Project. Information about how to complete this task is provided earlier in this chapter.

See Creating Send Master Projects.

Adding Header Information to MQSeries Projects

To add header information to the project:

1. In the Input Information section, select the Header Information tab if it is not already selected:

2. Select or enter values for the following required fields:

   • JMS Provider

   • JMS Queue

   • JMS Factory

   • JMS URL

   • Requesting Node

   • Message Name

   • Message Type

3. Enter values in any of the remaining optional fields as appropriate for your project.

4. Select File, Save Project.

Adding Input Files to MQSeries Projects

Information about creating and adding an input file to a project is provided earlier in this chapter.

See Adding Input Files to Projects.

Posting MQSeries Projects

To post an MQSeries project to a queue, click the Post button.

Viewing Output from MQSeries Projects

If you are working with a synchronous message, the Output Information area displays response information from the target system. If you are working with an asynchronous message, no response information is received.

Working With Groups of Projects

This section describes how to:

• Create groups of projects.

• Manage groups of projects.

• Test groups of projects.

• View test output.

• Share projects and groups.

Creating Groups of Projects

To create a group of projects:

1. Launch Send Master and select File, Batch Processing.

2. Select File, New Group.

3. Enter a name for the new group.

4. Define the project group:

   1. From the Run In drop-down list, select one of the following options to determine how the projects in the group run.

      Parallel	Run all projects in the group at the same time.
      Succession	Run projects in the group in succession.
      Time Lapse	Run projects in the group in the interval that you specify in the Delay field.

   2. (Optional.) In the Override URL field, enter a URL to override the one specified in the Server URL field in the Project work space.

5. Add projects to the group.

   1. In the Group Projects section, from the Projects drop-down list, select a project.

   2. Click the Add a new project button to add the project to the group.

   3. From the Method drop-down list, select an HTTP method.

   4. In the Amount field, enter the number of instances of the project to include in the group.

   5. From the Run In drop-down list, select one of the following options to specify how the projects run among themselves.

      Parallel	Run all instances of the project at the same time. The limited availability of open ports and other system resources requires you to determine the optimal number of projects to run at a single time. Start with 10 projects and slowly add projects to determine how many concurrent requests the system can process.
      Succession	Run instances of the project in succession.
      Time Lapse	Run instances of the project in the interval that you specify in the Delay field.

   6. Repeat steps a through e to add additional projects to the group.

6. Select File, Save Group.

Managing Groups of Projects

You might occasionally need to revise projects that you have added to a group. The following information will help you manage groups of projects:

• To change the order of a project in a group, in the Group Projects section, use the arrow buttons to move the project.

• To temporarily inactivate a project in a group, in the Project Settings section, select Inactive.

• To remove a project from a group, in the Group Projects section, select its file and click the Delete button.

Testing Groups of Projects

After you have created a group of projects, you can test them.

To test a groups of projects:

1. Open Send Master and select File, Batch Processing.

2. In the Group Definitions section, from the Group drop-down list, select the group to test.

   The projects in the group appear in the Group Projects section.

3. Make any needed adjustments to the group, such as changing the order of projects in the group, specifying inactive or active projects, and so forth.

4. Click the Start Projects button to run the test of projects in the group.

Viewing Test Output

After you run a test on a group of projects, you can view processing information and response information for any project in the group.

Viewing Processing Information

After you run a group of projects, the Completed Projects Output section displays all of the projects in the group and the instances for each project in a hierarchical tree format. To expand and collapse a project folder, click the icon to the left of the folder.

When you expand a project folder, the instances for the project appear as shown in the following graphic.

Each page icon represents a project instance. The number in parentheses represents the time needed to process the project instance.

To view detailed processing information about the entire group of projects, select a project, click the Export the Results to File button, and save the contents as a text file. You can then open the text file and view information, such as the total number of project instances in the group, the total time to process all project instances, processing start and end times, and so on. The following example shows the type of output you can view using the Export feature.

   Count                   : 5

   Round-trip times
        Total              : 0.961 (s)
        Minimum            : 0.180 (s) [2]
        Maximum            : 0.200 (s) [3]
        Average            : 0.192 (s)
        Process per second : 5.203

   [1]
        Request            : 0.191 (s) [start = 10:19:20.095, end = 10:19:20.286]
        Response           : 200 - OK
   [2]
        Request            : 0.180 (s) [start = 10:19:20.296, end = 10:19:20.476]
        Response           : 200 - OK
   [3]
        Request            : 0.200 (s) [start = 10:19:20.486, end = 10:19:20.686]
        Response           : 200 - OK
   [4]
        Request            : 0.190 (s) [start = 10:19:20.696, end = 10:19:20.886]
        Response           : 200 - OK
   [5]
        Request            : 0.200 (s) [start = 10:19:21.017, end = 10:19:21.217]
        Response           : 200 - OK

Viewing Response Information for a Project Instance

Send Master enables you to view response information for any project instance in a group of projects.

To view response information for a project instance:

1. Select a project instance in the Completed Projects Output section.

2. Click a project instance.

   Response information appears in the Output Information section.

Sharing Projects and Groups

When you create projects and groups, the system stores all data in the Send Master properties file. The location of this file is <PS_HOME>\webserv\<DOMAIN>\applications\peoplesoft\PSIGW\WEB-INF\classes\com\peoplesoft\pt\sendmaster\sendmasterproperties.xml. This file is not created until you use Send Master.

You can share and reuse projects and groups that you or others have created for other versions of Send Master or that have been used on other workstations. You do so by copying the sendmasterproperties.xml file into the Send Master directory. You must rename or delete the existing properties file before you copy the new file into the directory.

After you copy the sendmasterproperties.xml file into the Send Master directory, you can access the project and groups in the normal manner, by accessing them from the Project drop-down list in the Project work space, or from the Group drop-down list in the Batch Processing work space.

Using Send Master to Ping Remote Nodes

To ping a remote node from the Send Master, you post an example message to the node’s application server using an Integration Broker (MIME) or Integration Broker (XML) project that specifies a ping Message Type. You then use the Post button to post the message to the application server.

The following table describes the type of response returned based on project type.

You can also use Integration Broker Monitor and the Simple Post utility to ping remote nodes.

See Also

Pausing, Testing, and Pinging Nodes

Pinging Remote Nodes

Viewing Send Master Processing Performance Statistics

When working with Integration Broker MIME projects, you can gather processing performance statistics.

Enabling the Send Master Statistics Feature

To enable the Send Master processing performance feature, select Gather Statistics on the Headers Cont. tab.

Accessing Send Master Processing Statistics

When the Gather Statistics feature is enabled, Send Master returns processing statistics in the Output Information section after a Post.

To access statistics information , from the View drop-down list, select Meta Data and then click the If Valid XML, Format button.

The data is contained in the following tag:

<IBProfileInformation>

Interpreting Send Master Processing Statistics

Send Master returns statistics relating to processing on the application server and gateway, as well as response processing.

Note. All values returned are expressed in milliseconds.

This table describes the statistics that Send Master returns related to processing on the application server.

This table describes the statistics that Send Master returns related to processing on the integration gateway.

This table describes the statistics that Send Master returns related to processing the response message.

Statistics Example

The following example shows a sample of statistics that Send Master returns.

<?xml version="1.0"?>
<IBInfo>
    <TransactionID>
        <![CDATA[QE_UNDERDOG.QE_SALES_ORDER_SYNC_CHNL.af21859e-f5e7-11d7-
        b7f0-88b716eecd9a]]>
    </TransactionID>
    <Status>
        <StatusCode>0</StatusCode>
        <MsgSet>158</MsgSet>
        <MsgID>10000</MsgID>
    </Status>
    <ContentSections>
        <ContentSection>
            <ID>ContentSection0</ID>
            <NonRepudiation>N</NonRepudiation>
            <Headers>
                <version>
                    <![CDATA[VERSION_1]]>
                </version>
            </Headers>
        </ContentSection>
    </ContentSections>
    <IBProfileInformation>
        <keyword><AppServer></keyword>
            <keyword><TransformInbound>0</TransformInbound></keyword>
            <keyword><OnRoutePeopleCode>0</OnRoutePeopleCode></keyword>
            <keyword><OnRequestPeopleCode>0</OnRequestPeopleCode></keyword>
            <keyword><TransformOutbound>0</TransformOutbound></keyword>
            <keyword><DataBase>0</DataBase></keyword>
            <keyword><AppServerSendTime>0</AppServerSendTime></keyword>
            <keyword><AppServerRecvTime>0</AppServerRecvTime></keyword>
        <keyword></AppServer></keyword>
        <keyword><GatewayRequest></keyword>
            <keyword><Connector>24844</Connector></keyword>
            <keyword><Transform>0</Transform></keyword>
            <keyword><GatewayTime>651</GatewayTime></keyword>
        <keyword></GatewayRequest></keyword>
        <keyword><GatewayResponse></keyword>
            <keyword><Transform>0</Transform></keyword>
            <keyword><GatewayTime>211</GatewayTime></keyword>
        <keyword></GatewayResponse></keyword>
    <keyword></IBProfileInformation></keyword>

</IBInfo>

Using Send Master to Export Request Messages

This section describes how to export request messages. When working with Integration Broker MIME or Integration Broker XML project types, you can use Send Master to export a request message to a text file to examine the raw data that gets sent during a transaction.

Exporting Request Messages

To export a request message:

1. Open an Integration Broker MIME project or an Integration Broker XML project.

2. SelectFile, Export IBRequest .

   A Save dialog box appears.

3. Enter the location to save the file.

You can also view the raw data for a message in the integration gateway message log.

Allocating Additional Memory to Accommodate Posting Large Files

When posting files that are five MB or larger to the integration gateway, you should allocate additional random access memory (RAM) in Send Master to accommodate larger file sizes.

If Send Master does not have enough memory for a task, an “out of memory” error can occur.

To allocate additional RAM in Send Master:

1. Close Send Master.

2. Open StartSendMaster.bat (in Windows) or StartSendMaster.sh (in UNIX).

3. Add the –XmxZZm parameter, where ZZ equals the amount of RAM, in MB, to allocate.

4. Save the file.

5. Reopen Send Master.

For example, the value – Xmx128m indicates to allocate 128 MB of RAM. The following example shows how to add the parameter in the StartSendMaster.bat file:

cd "applications\peoplesoft\PSIGW\WEB-INF\classes\com\peoplesoft\pt\sendmaster\"
java -Xmx128m -classpath "c:\ptdvl\webserv\peoplesoft\applications\
peoplesoft\PSIGW\WEB-INF\lib\xalan.jar;c:\ptdvl\webserv\peoplesoft\applications\
peoplesoft\PSIGW\WEB-INF\lib\xerces.jar;c:\ptdvl\webserv\peoplesoft\applications\
peoplesoft\PSIGW\WEB-INF\classes;c:\ptdvl\webserv\peoplesoft\applications\peoplesoft\
PSIGW\WEB-INF\lib\mail.jar;c:\ptdvl\webserv\peoplesoft\applications\peoplesoft\PSIGW\
WEB-INF\lib\activation.jar;c:\ptdvl\webserv\peoplesoft\applications\peoplesoft\PSIGW\
WEB-INF\lib\jmq.jar;c:\ptdvl\webserv\peoplesoft\applications\peoplesoft\PSIGW\WEB-INF\
lib\jms.jar;c:\ptdvl\webserv\peoplesoft\applications\peoplesoft\PSIGW\WEB-INF\lib\
jndi.jar" com.peoplesoft.pt.sendmaster.SendMaster

You can increase the amount of memory in Send Master to any value you that you want, as long as your machine has the RAM to support the value that you choose.