Job Management Partner 1/Client Security Control Description, User's Guide and Operator's Guide
This section explains how to install and set up a new installation of JP1/CSC - Manager to be run in a cluster system.
The following figure shows the procedures for installation and setup. Setup of the cluster environment for the OS, JP1/Software Distribution, and AIM must be completed and logical IP addresses must be usable before you can set up JP1/CSC - Manager for operation in the cluster system.
Figure D-3 Procedures for JP1/CSC - Manager installation and setup (new installation)
- Organization of this subsection
- (1) Setting up the environment for the server machine and OS cluster software
- (2) Installing and setting up JP1/Software Distribution and AIM
- (3) Performing a new installation of JP1/CSC - Manager
- (4) Copying information carried over to the shared disk (for the active server only)
- (5) Setting up JP1/CSC - Manager
- (6) Registering service names in the cluster software (for the active server only)
(1) Setting up the environment for the server machine and OS cluster software
To set up the environment, perform the following on the active server and standby server:
- Set up the server machine.
- Install and set up the OS cluster software.
- Prepare the shared disk and logical IP address.
For details about installing and setting up the cluster software, see the cluster software documentation.
(2) Installing and setting up JP1/Software Distribution and AIM
Install and set up JP1/Software Distribution and AIM to run in the cluster environment. For details about installing and setting up JP1/Software Distribution (and Asset Information Manager Subset Component of JP1/Software Distribution Manager), see the manual Job Management Partner 1/Software Distribution Setup Guide, for Windows systems. For details about installing and setting up Asset Information Manager, see the manual Job Management Partner 1/Asset Information Manager Planning and Setup Guide.
(3) Performing a new installation of JP1/CSC - Manager
Install JP1/CSC - Manager on the local disk of both the active server and standby server. If you did not choose the automatic setup option during installation, restart the system after installation is completed. When the system has restarted, stop the World Wide Web Publishing Service and execute the cscsetup command.
(4) Copying information carried over to the shared disk (for the active server only)
An administrator manually copies the following JP1/CSC - Manager installation folders to the shared disk path specified during setup.
Table D-2 Folders copied to the shared disk
Contents Copy source Copy destination Environment settings information JP1/CSC - Manager-installation-folder\conf shared-disk-path\conf Policy file JP1/CSC - Manager-installation-folder\dat shared-disk-path\dat Policy import execution file (manual) JP1/CSC - Manager-installation-folder\spool shared-disk-path\spool History file JP1/CSC - Manager-installation-folder\db shared-disk-path\db Log file JP1/CSC - Manager-installation-folder\log shared-disk-path\log
- Legend:
- installation-folder indicates the installation folder for JP1/CSC - Manager.
- The default installation folder for JP1/CSC - Manager is as follows (when the OS is installed under C:\):
- For Windows Server 2003 (x64):
- C:\Program Files(x86)\HITACHI\jp1netmcscm
- For other OSs:
- C:\Program Files\HITACHI\jp1netmcscm
(5) Setting up JP1/CSC - Manager
Set up JP1/CSC - Manager on the active server first, and then on the standby server.
JP1/CSC - Manager can be set up from the Client Security Control - Manager Setup dialog box. For the items in the Basic Settings page, Agent page, and Remote Option page, set the same information for the active server and standby server.
For details about setting up JP1/CSC - Manager, see 5.4.3 Setting up JP1/CSC - Manager.
- Active server
Choose the Basic settings page in the Client Security Control - Manager Setup dialog box, and set the following items for Cluster information.
Table D-3 Setup items for Cluster information (active server)
Setup item Description Cluster environment Be sure to specify Use. Logical IP address Specify the logical IP address of the cluster system. This item is required. Logical host This item is optional. For JP1/IM linkage, specify the name of the logical host when messages are sent to the event server on the logical host.
For details about the logical host name, see the manual Job Management Partner 1/Base User's Guide.Shared disk Specify the shared disk path of the cluster system. JP1/CSC - Manager creates on the shared disk information carried over to the standby server. This item is required. - Standby server
In the Client Security Control - Manager Setup dialog box, set the same information as for the active server in the items in the Basic Settings page, Agent page, and Remote Option page.
(6) Registering service names in the cluster software (for the active server only)
In the cluster software (MSCS or WSFC), register the names of the JP1/CSC - Manager services that you want to be able to fail over. If a remote management server is configured in the system, also register the name of the remote service. The services whose names are registered in the cluster software are as follows.
Product name Service name Resource type Description JP1/CSC - Manager JP1_NETM_CSCM Generic service Name of JP1/CSC - Manager service JP1_NETM_CSCM_RS Generic service Name of remote service For details about how to register service names, see the MSCS or WSFC documentation. When registering service names, note the following:
- Have the service carried over from the active server to the standby server, with the IP address and shared disk used.
- Have the JP1/CSC - Manager service also fail over when the AIM service is failed over.
- Once the logical IP address and shared disk can be used, set JP1/CSC - Manager to start. Also set JP1/CSC - Manager to stop in the reverse order from how it starts.
All Rights Reserved. Copyright (C) 2009, 2011, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated