Configuring the Event Server › Configure CA Workload Automation AE to Run in Dual Event Server Mode

Configure CA Workload Automation AE to Run in Dual Event Server Mode

By default, CA Workload Automation AE is configured to run in single event server mode during installation. You can configure CA Workload Automation AE to run in dual event server mode during installation or later using the Event Server - CA Workload Automation AE Administrator window of CA Workload Automation AE Administrator.

If you configured CA Workload Automation AE to run in dual event server mode and one event server goes down, CA Workload Automation AE automatically rolls over to the second event server and continues running in single event server mode. After you recover the event server that failed, you can reconfigure CA Workload Automation AE to run in dual event server mode.

Important! Do not try to run CA Workload Automation AE in dual event server mode if it was previously running in single event server mode or if it rolled over to single event server mode. You must synchronize the two event servers before configuring CA Workload Automation AE to run in dual event server mode.

Notes:

• The A Database Rollover Has Occurred check box indicates whether a database rollover has occurred from dual event server mode to single event server mode. If there has been a rollover and a switch to single event server mode, the A Database Rollover Has Occurred check box is selected and the Status field displays which event server is down.
• For more information about how to install and configure dual event servers, see the Windows Implementation Guide.

Follow these steps:

1. Click Start, Programs, CA, Workload Automation AE, Administrator.

   The Instance - CA Workload Automation AE Administrator window opens.

2. Select an instance from the Instance drop-down list in the Settings pane.
3. Click the Event Server icon on the toolbar.

   The Event Server - CA Workload Automation AE Administrator window appears.

4. Verify that the A Database Rollover Has Occurred check box is disabled.

   Note: By default, the A Database Rollover Has Occurred check box is disabled.

5. Stop the scheduler and the application server services as follows:
   1. Click the Services icon on the toolbar.

      The Services - CA Workload Automation AE Administrator window appears, displaying a list of services installed on the selected instance.

   2. Right-click the scheduler and select Stop. Repeat this action for the application server.

      The scheduler and application server stop.

6. Enter the following command at the instance command prompt:

   cd %AUTOSYS%\dbobj\dbtype
   

   dbtype

   Specifies the type of database in use: MSQ (Microsoft SQL Server), ORA (Oracle), or SYB (Sybase).

   The database type is identified.

7. Run the bulk copy script. The script that you run depends on your database vendor.
   • Oracle

     perl autobcpORA.pl source_server target_server source_userid source_password target_userid target_password dump_file oracle_directory
     

   • Sybase

     perl autobcpSYB.pl source_server source_db target_server target_db source_userid source_password target_userid target_password dump_file blk_size
     

   • Microsoft SQL Server

     perl autobcpMSQ.pl source_server source_db target_server target_db source_userid source_password target_userid target_password dump_file
     

   source_server

   Defines the name of the source Oracle System ID (for example, AEDB), Sybase server (for example, SourceServer), or Microsoft SQL Server server (for example, SourceServer). For Sybase, the source server name is defined in the interfaces file. For Microsoft SQL Server, you can view the source server name using Microsoft SQL Enterprise Manager.

   Note: On Windows, the entire value of the database server name and the database name can be up to 64 characters.

   source_db

   Defines the source Microsoft SQL Server or Sybase database (for example, AEDB).

   source_userid

   Defines the user ID that is used to connect to the source Oracle System ID, Microsoft SQL Server server, or Sybase server.

   Note: On Oracle, use aebadmin as the source user ID.

   source_password

   Defines the password that corresponds to the user ID that is used to connect to the source Oracle System ID, Microsoft SQL Server server, or Sybase server.

   target_server

   Defines the target Oracle System ID (for example, AEDB2), Microsoft SQL Server server (for example, DestinationServer), or Sybase server (for example, DestinationServer). For Sybase, the target server name is defined in the interfaces file. For Microsoft SQL Server, you can view the target server name using Microsoft SQL Enterprise Manager.

   Notes:

   • For Oracle, the source server must be different from the target server.
   • On Windows, the entire value of the database server name and the database name can be up to 64 characters.

   target_db

   Defines the target Microsoft SQL Server or Sybase database (for example, AEDB2).

   Note: The autobcpDB script deletes all of the data in the target database and replaces it with the data in the source database. If you want to save the data in the target database, archive it before you run the autobcpDB script.

   target_userid

   Defines the user ID that is used to connect to the target Oracle System ID, Microsoft SQL Server server, or Sybase server.

   Note: On Oracle, use aedbadmin as the target user ID.

   target_password

   Defines the password that corresponds to the user ID that is used to connect to the target Oracle System ID, Microsoft SQL Server server, or Sybase server.

   dump_file

   Defines the temporary file that is used in the transfer of data from one database to the other database.

   Note: Specify a file that is local to the computer where this script is running.

   oracle_directory

   Defines the path to the Oracle home directory.

   blk_size

   (Optional) Specifies the number of rows that can be inserted from the dump_file to the destination database at a time.

   Default: 5000

   Note: The default value is used if you run the autobcpSYB.pl script in the interactive mode or you do not specify the blk_size value. Do not specify a large value because the transaction log encounters problems when it becomes too full.

   The event servers are synchronized.

8. Enable the second event server as follows:
   1. Click the Event Server icon on the toolbar.

      The Event Server - CA Workload Automation AE Administrator window appears.

   2. Click the Event Server 1 or Event Server 2 tab based on the event server you want to enable and click Enable.

      The second event server is enabled. The status of the second event server is displayed as UP and the A Database Rollover Has Occurred check box is cleared and disabled.

9. Start the scheduler and the application server services as follows:
   1. Click the Services icon on the toolbar.

      The Services - CA Workload Automation AE Administrator window appears, displaying a list of services installed on the selected instance.

   2. Right-click the scheduler and select Start. Repeat this action for the application server.

      The scheduler and application server start.

   CA Workload Automation AE is configured to run in dual event server mode.