Setting Up Batch Monitoring

This section contains background information about Version 5 batch tools, and explains how to set up the Version 5 Communications Backbone (packaged with Version 5) and the IBM MQSeries product to allow end users run batches in local and remote mode.

For information about how to run the batch monitor and submit batches in both local and remote modes, refer to Using the Batch Monitor in your Infrastructure Users Guide.
The CATIA, DELMIA and ENOVIA DMU Navigator core software features the CATUTIL batch monitor for running and monitoring Version 5 batches. Certain batches are provided as part of the Version 5 core package, others are part of specific configurations/products. Note that certain batches can only be run if you have the corresponding license.

You can run the batch monitor using a variety of methods to launch the batches installed with your software. The batches can be:

  • run locally on the machine on which you are using the batch monitor
  • or submitted to a remote machine to be run on the remote machine.

As far as batch execution is concerned, two implementations are possible:

  • with the first implementation, the batch monitor requires no external software as a prerequisite since it can work using the communications backbone packaged with the core Version 5 software described in Communications Backbone Files; the backbone is used for both local and remote batch execution
  • if you install and configure the IBM MQSeries Version 5.2 product, you will be able to run and monitor batches on both your local computer and remote computers:
    • using the batch monitor in Version 5
    • or using the MQSeries command line syntax

    The batches can be either those provided with the Version 5 core software, or your own customized batches.

What Is a Version 5 Batch?

A Version 5 batch is a non-interactive program with the following characteristics:

  • it is described in an XML file referred to as the descriptor file
  • its inputs and outputs are described in an XML file referred to as the parameter file.

Role of the Descriptor File

So that each batch can be listed and recognized, a descriptor file is delivered for each batch on Windows in:

C:\Program Files\Dassault Systemes\B18\intel_a\code\bin\resources\batchdesc (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18\win_b64\code\bin\resources\batchdesc (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin\resources\batchdesc (32-bit code on Windows XP Professional x64 Edition)

and on UNIX in:

/usr/DassaultSystemes/B18/OS/resources/batchdesc

where  "OS" is:

  • aix_a
  • hpux_b
  • solaris_a.
The descriptor file must NOT be modified by the batch monitor administrator.

Role of the Parameter File

The syntax of the parameter file for each batch is provided in an empty file.

The person who runs the batch must fill in this XML file to specify the inputs to be passed to the batch.

If the batch is submitted using the CATUTIL interactive batch tool, the file is generated from the user input specified by using the batch user interface.

List of Version 5 Batches

A list of Version 5 batches along with their description is displayed in the Type column. This list may vary according to the licenses you set up during installation:

  • Batch-DXF-IGES-STEP: lets you exchange data between Version 5 and DXF, IGES/STEP
  • ExtractModelFromSequential: lextracts CATIA Version 4 models from CATIA Version 4 sequential files
  • MigrateV4ToV5: converts CATIA Version 4 models into Version 5 documents
  • CATDUAV5: uses the CATIA Version Data Upward Assistant allowing support for Version 5 level changes, diagnostics and, if required, repairing of Version 5 data
  • Data Life Cycle: provides a user interface and capabilities common to all batches dealing with data life cycle, i.e. CATDUAV5, Downward Compatibility and Extract Model From Sequential
  • DownwardCompatibility: lets you reuse Version 5 data, created in the most recent release, in an earlier release
  • UpdateBatch: lets you update a list of CATDrawing documents
  • PrintBatch: lets you print your documents without running Version 5.
Note that not all batches can be run on a remote machine! Furthermore, documents containing links to other documents (for example, CATProducts) cannot be processed in remote batch mode.

Local and Remote Modes

Using the Communications Backbone

In Local Mode

To submit batches for execution on your local machine using the communications backbone, no administration tasks are necessary: the backbone is the default communication driver. The batch will be run as long as the required license is available.

In Remote Mode

On the remote mode:

  • the Version 5 core software containing the communications backbone must be installed
  • the configuration installed on the remote machine must allow end users to run the desired batch
  • a license for the appropriate configuration must be either installed on the remote machine, or be accessible from the remote machine
  • you must start the backbone server monitor, as explained in Configuring the Communications Backbone on the Remote Machine.

Using IBM MQSeries

In Local Mode

If you want to run batches on your local computer, you have to install the IBM MQSeries Server software on the local computer and then configure the MQSeries server on the local computer.

In Remote Mode

If you want to run batches on a remote computer, you have to install the IBM MQSeries Client software on your local computer and configure the client, then install the IBM MQSeries Server software on the remote computer and then configure the server.
 

Configuring the Communications Backbone on the Remote Machine
 

Backbone Configuration

The default port used by the Backbone communication software is 55555. Backbone communication may not work between two remote machines if they use a different backbone port. To get the backbone working correctly, you must ensure that these machines reference the same port. To perform this check, the BBPortChecker tool is available on this installation. It allows to test the backbone communication between two remote machines (-host option) or between your machine and a list of machines (-l file option). Without any option the BBPortChecker tool display the backbone default port on your machine and tells you how to update it if needed. You can launch this tool by following these instructions.

Windows XP

  1. Open an MS-DOS Window.
  2. Change to the default folder in which you installed the product:

    The default folder is, for example for 32-bit Windows XP Pro:

    C:\Program Files\Dassault Systemes\B18\intel_a\code\bin
     
  3. Enter the command:

    BBPortChecker
UNIX
  1. Change to the directory:

    /usr/DassaultSystemes/B18/OS/code/command
     
  2. Run the command:

    ./catstart -run BBPortChecker

Help on the usage of this tool is available using the -h option.

  To allow end users to run a batch on a remote machine, you first have to start the server monitor on the remote machine.

On Windows

  1. Log onto the remote machine.
  2. Open a Command Prompt window.
  3. Go to the following Version 5 installation folder, for example:

    C:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
    C:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
    C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

  4. Run the command:
    catstart -run "CATBatSrvMonitorExe BB"

    A message will confirm that the BB service has been started.

On UNIX

  1. Log onto the remote machine.
  2. Go to the following Version 5 installation folder, for example:
    /usr/DassaultSystemes/B18/OS/code/command

    where  "OS" is:
    • aix_a
    • hpux_b
    • solaris_a.
  3. Run the command:
    catstart -run "CATBatSrvMonitorExe BB"
 

Configuring an IBM MQSeries Server for the Batch Monitor for the First Time
  We assume that you are already familiar with the IBM MQSeries product before setting up the server. If not, refer to the manual MQSeries V5.2 Quick Beginnings for your platform.
 

Export the MQ Library Path

Before starting the batch monitor server, perform the following operations:

  1. Run the command:

    catstart -run cmd (ou catstart -run /bin/ksh)
  2. Update the environment variable for managing libraries to point to the MQ install path (for example, MQ_PATH):

    On SUN: export LD_LIBRARY_PATH=$MQ_PATH/lib:$LD_LIBRARY_PATH

    On HP-UX: export SHLIB_PATH=$MQ_PATH/lib:$SHLIB_PATH

    On AIX: export LIBPATH=$MQ_PATH/lib:$LIBPATH

    On AIX 64-bit: export LIBPATH=$MQ_PATH/lib64:$LIBPATH

    On Windows: set PATH=%MQ_PATH%\lib:$PATH

  3. Run the executable program as explained below.

On Windows
1. Log onto the server computer as administrator.
2. Install the IBM MQSeries Server software.
3. Open a Command Prompt window and go the folder, for example for 32-bit Windows XP Pro:

C:\Program Files\MQSeries\bin
4. Before creating the queue manager, set the following variable:

set MQSNOAUT=yes

For more detailed information about the role of the MQSNOAUT variable, refer to the manual IBM MQSeries System Administration, Chapter 10 : "Protecting MQSeries Objects".
5. Create a queue manager for the hostname of your server computer by entering the command:

crtmqm HostNameMachine

where "HostNameMachine" is the name of your server computer.
The name of the host machine must be in upper case. Make sure that it is in upper case throughout the rest of this scenario.
6. Start the queue manager by entering the command:

strmqm HostNameMachine
7. Configure the queue manager by entering the command:

runmqsc HostNameMachine < ConfigFile

where "ConfigFile" is the path of the following file located in the Version 5  installation directory and installed with the Version 5 software:

C:\Program Files\Dassault Systemes\B18\intel_a\code\bin\resources\batchdesc\CATBatchMQ.conf (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18\win_b64\code\bin\resources\batchdesc\CATBatchMQ.conf (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin\resources\batchdesc\CATBatchMQ.conf (32-bit code on Windows XP Professional x64 Edition)
  8. Before running a batch, select Start->Programs->IBM MQSeries->IBM MQSeries Explorer and check that the queue manager you created earlier is running, and that there are no messages present in existing queues.

The presence of messages in the queues will prevent a batch from being run.

On UNIX
1. Log onto the UNIX workstation as root.
2. Prepare to install the IBM MQSeries Server software.

Refer to the IBM MQSeries documentation for more details. For example, you will find the Quick Beginnings manual very useful if you are using IBM MQSeries for the first time.

For the purposes of our scenario, we installed the IBM MQSeries Server software on a workstation running AIX.

Refer to the manual MQSeries V5.2 Quick Beginnings for your UNIX platform for more information.
  In particular, pay attention to the kernel configuration. MQSeries makes use of semaphores, shared memory, and file descriptors, and it is probable that the default kernel configuration is not adequate.

Refer to the section Kernel configuration in the manual MQSeries V5.2 Quick Beginnings for your UNIX platform for more information.
3. Install the IBM MQSeries Server software.
Note that a user ID with the name mqm whose primary group is mqm is automatically created during the installation. You can create the user and group IDs yourself, as explained in the manual MQSeries V5.2 Quick Beginnings for your UNIX platform, but make sure you do this before installing the server. User ID and group must both be mqm. For stand-alone machines, you can create the new user and group IDs locally, and for machines administered in a network information services domain (NIS), you must create the IDs on the NIS master server machine.

After installation, the mqm user ID owns the directories and files that contain the resources associated with the product.

If you want to run any administration commands, for example crtmqm (create queue manager) or strmqm (start queue manager), your user ID must be a member of group mqm.
4. To configure the server, open a shell window and enter the command:

su mqm

and provide the password mqm when prompted. Using this user ID will now let you perform MQSeries administration tasks.
5. Before creating the queue manager, export the following variable:

export MQSNOAUT=yes

For more detailed information about the role of the MQSNOAUT variable, refer to the manual IBM MQSeries System Administration, Chapter 10 : "Protecting MQSeries objects".
6. Create a queue manager on your workstation by entering the command:

crtmqm HostNameMachine

where "HostNameMachine" is the name of your workstation.
The name of the host machine must be in upper case. Make sure that it is in upper case throughout the rest of this scenario.
7. Start the queue manager by entering the command:

strmqm HostNameMachine
8. Configure the queue manager by entering the command:

runmqsc HostNameMachine < ConfigFile

where "ConfigFile" is the path of the following file located in the Version 5  installation directory and installed with the Version 5 software:

/usr/DassaultSystemes/B18/aix_a/resources/batchdesc/CATBatchMQ.conf
If you encounter an error (execution code other than 0) when running the runmqsc command, you will not be able to run any batches. If this is the case, please contact your IBM MQSeries Administrator.
  9. Run the channel listener:

runmqlsr -m HostNameMachine -t TCP
  10. Before running a batch, check that the queue manager you created earlier is running, and that there are no messages present in existing queues.

The presence of messages in the queues will prevent a batch from being run.
  11. On HP-UX, disable the q3p option on the CATBatSrvMonitorExe program as follows:
  • go to /usr/DassaultSystemes/B18/hpux_a/code/bin
  • run the command:

    chatr +q3p disable     CATBatSrvMonitorExe
 

Configuring an IBM MQSeries Client for the Batch Monitor
 

Export the MQ Library Path

Before starting the batch monitor, perform the following operations:

  1. Run the command:

    catstart -run cmd (ou catstart -run /bin/ksh)
  2. Update the environment variable for managing libraries to point to the MQ install path (for example, MQ_PATH):

    On SUN: export LD_LIBRARY_PATH=$MQ_PATH/lib:$LD_LIBRARY_PATH

    On HP-UX: export SHLIB_PATH=$MQ_PATH/lib:$SHLIB_PATH

    On AIX: export LIBPATH=$MQ_PATH/lib:$LIBPATH

    On AIX 64-bit: export LIBPATH=$MQ_PATH/lib64:$LIBPATH

    On Windows: set PATH=%MQ_PATH%\lib:$PATH

  3. Run the executable program as explained below.

On Windows
Set the MQServer  variable as follows:

set MQSERVER=CATBATCHANNEL/TCP/Hostname_server

where "Hostname_server" if the name of the client computer on which you installed the IBM MQSeries Server software.

On UNIX
  Export the MQServer  variable as follows:

export MQSERVER=CATBATCHANNEL/TCP/Hostname_server

where "Hostname_server" if the name of the client computer on which you installed the IBM MQSeries Server software.
 

Windows and UNIX

Rename a library file libCATComDrvMQss.so to libCATComDrvMQss.old by running the following command, for example on UNIX:

mv libCATComDrvMQss.so libCATComDrvMQss.old
 

Verifying Your MQSeries Installation
  We recommend at this point that you verify your IBM MQSeries installation as described in the section Verifying the installation of MQSeries for your UNIX platform. Read the section about verifying a client/server installation, involving communication links between a server machine and an MQSeries client.

Furthermore, on UNIX,  make sure that you read the information in this section about certain UNIX system files which need to be modified:

  • /etc/services
  • /etc/inetd.conf

Running Batches Using MQSeries on Your Local Computer in Command Line Mode
  For the purposes of the rest of this scenario, the IBM MQSeries Server and Client are located on the same machine.

On Windows
  To run a batch, go to the following Version 5 installation folder, for example:

C:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

and run the command:

CATBatCliMonitorExe MyParameterFile LOCALMQ

where MyParameterFile is the path of an existing XML parameter file saved, for example, by running the batch monitor in interactive mode in a Version 5 session.

The batch is run and a log is created by default in:

C:\Temp
You can monitor the batch queues by selecting the command Start->Programs->IBM MQSeries->MQSeries Explorer.

On UNIX
  To run a batch, go to the following Version 5 installation folder, for example:

/usr/DassaultSystemes/B18/aix_a/code/bin

and run the command:

CATBatCliMonitorExe MyParameterFile LOCALMQ

where MyParameterFile is the path of an existing XML parameter file saved, for example, by running the batch monitor in interactive mode in a Version 5 session.

The batch is run and a log is created by default in:

/tmp
 

Running Batches Using the Batch Monitor on a Remote Computer Using IBM MQSeries

  Full details are provided refer to Using the Batch Monitor in your Infrastructure Users Guide.

However, note that before starting Version 5 on the local computer configured as an MQSeries client, you must export the following variable to specify that you are using IBM MQSeries:

export CATBATCHMQ=1

Running Batches in Command Line Mode on a Remote Computer Using IBM MQSeries

You can also run batches on a remote computer: the  IBM MQSeries Client is on your local computer, and the IBM MQSeries Server is on a remote computer.

The client machine and the server machine on which the batch is to be run must both have Dassault Systemes Version 5 software installed.

On the server machine, the batch server monitor is started. This monitor starts the batches installed on the server submitted from any client. The monitor waits for batch launch requests and must be stopped manually.

The batch server monitor is started once and for all, whereas the client monitor is started once for each batch submitted.

Windows

On the server machine, go to the directory:

C:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

and enter the following command to run the batch monitor server:

CATBatSvrMonitorExe MQ

On the client machine, go to the directory:

C:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

and enter the following command to run the batch:

CATBatCliMonitorExe MyParameterFile MQ ServerMachineName

UNIX

On the server machine, go to the directory:

/usr/DassaultSystemes/B18/aix_a/code/command

and enter the following command to run the batch monitor server:

./catstart -run "CATBatSvrMonitorExe MQ"

On the client machine, go to the directory:

/usr/DassaultSystemes/B18/aix_a/code/command

and enter the following command to run the batch:

./catstart -run "CATBatCliMonitorExe MyParameterFile MQ ServerMachineName"