![[Contents]](FIGURE/CONTENT.GIF)
Job Management Partner 1/Software Distribution Setup Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
The following shows how to create an environment in which failover of JP1/Software Distribution is enabled.
If the OS is Windows Server 2008, replace Cluster Administrator with Failover Cluster management. If the OS is Windows Server 2012, replace Cluster Administrator with Failover Cluster Manager.
Create a group for JP1/Software Distribution and register the IP address resource, network name resource, and shared disk (physical disk) resource.
The first time Microsoft Cluster Service or Windows Server Failover Cluster is installed, a group named Cluster Group is created. Create a new group separately from Cluster Group. Also, set the server that is running as the executing server as the primary server.
For details about creating a group resource, see the Microsoft Cluster Service or Windows Server Failover Cluster documentation.
This subsection describes how to create an environment for using the failover facility of JP1/Software Distribution.
Be sure to install and set up JP1/Software Distribution Manager and then set up Database Manager.
Some settings are not displayed, depending on the components to be installed. For the settings that are not listed in the tables below, set them as usual. For details about the installation, setup, and Database Manager settings, see the following chapters:
The following table shows the settings required when Server and Asset Information Manager Subset of JP1/Software Distribution Manager are installed:
Table 11-2 How to set up JP1/Software Distribution Manager
| Program | Item | Setting | Server | AIM Setup# |
|---|---|---|---|---|
| Installation | Type of JP1/Software Distribution Manager | Choose Central manager. | Y | Y |
| Components to be installed | Choose Server or Asset Information Manager Subset, whichever you will be using. | Y | Y | |
| Installation directory setting | Specify the local drive. | Y | Y | |
| Database settings (when Microsoft SQL Server is used) | If you have configured Microsoft SQL Server in a cluster system, specify the logical host name or logical IP address as the host name of the database server. | Y | Y | |
| Database settings (when Oracle is used) | If you have configured Oracle on a failover cluster system, specify the logical host name or logical IP address as the host name of the database server. | Y | Y | |
| Package storage directory setting | Specify a shared disk. | Y | -- | |
| Software operation history storage directory setting | Specify a shared disk or network drive. | Y | -- | |
| Service setting (for new installation only) | In Startup type, select Manual. | Y | -- | |
| Connection destination setting (Remote Installation Manager) | Specify a logical host name or logical IP address. | -- | Y | |
| Virtual directory setting for Asset Information Manager Subset | Specify a shared disk. | -- | Y | |
| Setup | Cluster Settings page |
|
Y | -- |
| Operation Monitoring page | If you select the Compress and move the operation history to the storage directory radio button, specify a shared directory under Storage directory. | Y | -- | |
| Audit Log page | If you select the Output audit logs check box, specify the local disk in Output directory for audit logs. | Y | -- | |
| SQL Server client network utility (when Microsoft SQL Server is used) |
Network library settings | When connecting Microsoft SQL Server in a cluster system, use TCP/IP as the network library for connection. Use the SQL client setup utility to add an entry that uses the logical host name for Microsoft SQL Server. | Y | Y |
| Oracle Net8 Assistant or Net Manager (when Oracle is used) |
Create a net service name | Create a net service name in the format NETM_logical-host-name. If you have configured Oracle on a failover cluster system, specify the logical host name for the destination Oracle as the host name used in the address configuration. |
Y | -- |
| Database Manager (for executing system only) | Detailed database settings (for Microsoft SQL Server) | Specify a shared disk for all database files. | Y | -- |
| Detailed tablespace settings (for Oracle) | Y | -- | ||
| Database Manager (for Embedded RDB) |
Edit HiRDB.ini (Computer on which Server Core facility is installed has more than one NIC) | Specify a logical IP address as the client environment variable PDCLTRCVADDR in the files listed below. JP1/Software-Distribution-installation-directory\Setup_Input\ini\HiRDB.ini JP1/Software-Distribution-installation-directory\Setup_Input_HA\ini\HiRDB.ini |
Y | -- |
| Cluster system environment settings | Select the Use in a cluster system environment option, and then select Execution mode or Standby mode. Specify the logical host name and executing host name. | Y | -- | |
| Management database settings | Specify a shared disk for the management database area path. Specify a local disk for the work table area path. Use the same Automatically increase the size check box setting for both active and standby servers. |
Y | -- | |
| Detailed database settings | Specify a shared disk for all database files. | Y | -- | |
| Asset Information Manager Subset environment setting (creation of data source or net service) (when Oracle is used) | Net service creation | If you have configured Oracle on a failover cluster system, specify the logical host name of the target Oracle for Server. | -- | Y |
| Asset Information Manager Subset environment setting (Database Manager) (execution mode only when Microsoft SQL Server or Oracle is used) | Detailed database settings | Specify a shared disk for all database files. | -- | Y |
| Asset Information Manager Subset environment setting (Database Manager) (when Embedded RDB is used) | Cluster system settings | Select the Use in a cluster system environment option, and then select Execution mode or Standby mode. Specify the logical host name and executing host name. Specify the same port number for both active and standby servers. |
-- | Y |
| Detailed database settings | Specify a shared disk for the storage folder name. Specify the same Storage folder name and Size for both active and standby servers. |
-- | Y |
#: AIM Subset: Asset Information Manager Subset
If you have already constructed an environment for JP1/Software Distribution Manager for a configuration in which failover does not occur, open Control Panel, choose Administrative Tools, and Services, double-click the service Remote Install Server, and then change the startup type from Automatic to Manual.
If system restart is requested at the end of the installation procedure for JP1/Software Distribution Manager, restart the computer.
The standby server becomes the owner of the group.
Construct an environment for the standby server. For details about the installation procedure and settings, see (a) Install JP1/Software Distribution Manager on the executing server.
The standby server becomes the active of the group.
Tables 11-3 through 11-8 list and describe the settings.
Table 11-3 Resource settings when Server is used
| Registered resource | Item | Setting |
|---|---|---|
| Remote Install Server | Name | Specify any name. |
| Resource type | Set Generic Service. | |
| Group | Set the group name that was created by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Executable owner | Set the running system and standby system nodes. | |
| Dependency |
|
|
| Generic service parameter | Remote Install Server | |
| Registry copy# |
|
Table 11-4 Resource settings for HiRDB/ClusterService_JN1 when Embedded RDB is used
| Registered resource | Item | Setting |
|---|---|---|
| HiRDBClusterService_JN1 | Name | Specify any name. |
| Resource type | Set Generic Service. | |
| Group | Set the group name that was created by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Executable owner | Set the running system and standby system nodes. | |
| Dependency | Set the network name and physical disk that were registered by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Generic service parameter | HiRDBClusterService_JN1 | |
| Registry copy | Not specified |
Use Cluster Administrator to set the generic-service resource Remote Install Server to online. Thereafter, to stop and start the Remote Install Server service, use Cluster Administrator to set it to offline or online.
Table 11-5 Resource settings when Asset Information Manager Subset is used
| Registered resource | Item | Setting |
|---|---|---|
| Asset Information Synchronous Service | Name | Specify any name. |
| Resource type | Set Generic Service. | |
| Group | Set the group name that was created by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Executable owner | Set the running system and standby system nodes. | |
| Dependency |
|
|
| Generic service parameter | AssetInformationSynchronousService | |
| Registry copy | Not specified |
Table 11-6 Resource settings for HiRDB/ClusterService_AM1 when Embedded RDB is used
| Registered resource | Item | Setting |
|---|---|---|
| HiRDBClusterService_AM1 | Name | Specify any name. |
| Resource type | Set Generic Service. | |
| Group | Set the group name that was created by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Executable owner | Set the running system and standby system nodes. | |
| Dependency | Set the network name and physical disk that were registered by Cluster Administrator of Microsoft Cluster Service or Windows Server Failover Cluster. | |
| Generic service parameter | HiRDBClusterService_AM1 | |
| Registry copy | Not specified |
Table 11-7 Resource settings for Microsoft Internet Information Services when Asset Information Manager Subset is used (for Windows 2000 and Windows Server 2003)
| Registered resource | Item | Setting |
|---|---|---|
| Microsoft Internet Information Services | Name | Specify any name. |
| Resource type | Set the following value:
|
|
| Group | Set the group name created by Microsoft Cluster Service's Cluster Administrator. | |
| Executable owner | Set the running system and standby system nodes. | |
| Dependency | Set the network name and physical disk registered by Microsoft Cluster Service's Cluster Administrator. | |
| Parameter (for Windows 2000) |
Set to the service that is used for failover. In IIS, select the WWW radio button, and then select Default Web Site in the IIS Server combination box. | |
| Script file path (for Windows Server 2003) |
Set the following value:%systemroot%\System32\Inetsrv\Clusweb.vbs |
Table 11-8 Resource settings for Microsoft Internet Information Services when Asset Information Manager Subset is used (for Windows 2008)
| Resource type | Content input to script file path | Dependency |
|---|---|---|
| Generic script | %systemroot%\System32\Inetsrv\Clusweb.vbs | Set the Shared disk and Client access point resources. |
To set up an environment for a relay system or client immediately below JP1/Software Distribution Manager:
When you want to use the facilities of JP1/Software Distribution, specify the logical host name or logical IP address of the connection destination during installation.
The following table shows how to specify the connection destination for each component you use.
Table 11-9 Specifying the connection destinations for using components
| Component | Name of dialog box | Setting |
|---|---|---|
| Server core facility | Server Setup (AIM page) |
If you have constructed Asset Information Manager Subset on a failover cluster system, specify the connection-target logical host name or logical IP address in URL for Asset Information Manager. |
| Remote Installation Manager | Specify Connection Destination (installer) |
For the connection destination of Remote Installation Manager, specify the logical host name or logical IP address. |
| Software Distribution Manager Logon (Logon window) |
||
| Packager | Specify Connection Destination | Specify a logical host name or logical IP address for Packager's connection destination. |
When you use JP1/Software Distribution Manager in a cluster system configuration containing a firewall, specify the logical and physical addresses for the nodes that data passes through.
The table below shows the actions that should be taken by the user in the event of a failover. If you use an Oracle cluster environment as a relational database environment, you can continue the application without re-connection due to a communication error.
Table 11-10 Actions to be taken by the user after a failover
| No. | When failover occurred | Action to be taken after the failover |
|---|---|---|
| 1 | While starting the Inventory Viewer of Remote Installation Manager | After a dialog box appears indicating a communication error or a database access error, reconnect to the JP1/Software Distribution server. |
| 2 | While registering a job | After a dialog box appears indicating a communication error or a database access error, re-register the job. |
| 3 | While a job was waiting for execution | Re-execute the job. |
| 4 | While a job was being executed (20%) | Re-execute only the failed job (you do not need to take any action for a job waiting for execution, a job resulting in a startup error, a suspended job, a job placed in installation-rejecting status, a completed job, or a normally terminated job) |
| 5 | While re-executing a job that was executed at least 20% | For jobs contained in the job execution status folder RETRY_RELAY_SYSTEM, perform steps 3 and 4. |
| 6 | After editing an ID group (adding/deleting the relay managing the ID, adding/deleting clients, or changing the password) | For the jobs contained in the job execution status folder Edit ID Group, perform steps 3 and 4. |
| 7 | When the options that are enabled on the System Configuration page in JP1/Software Distribution Manager's Server Setup dialog box are Apply the system configuration information automatically and Linkage when system configuration is changed | For jobs contained in the job execution status folder Edit System Configuration Information, perform steps 3 and 4. |
| 8 | While editing a job definition | After a dialog box appears indicating a communication error or a database access error, re-create a new job definition. The job definition you were editing is invalid, so delete it. |
| 9 | While executing the CSV output utility | After a dialog box appears indicating a communication error or a database access error, re-execute the job. |
| 10 | While executing Database Manager | After a dialog box appears indicating a database access error, take appropriate action for the situation.
|
| 11 | While executing a command | Re-execute the command that returned the communication error or connection error. |
| 12 | While the packager was packaging software | After a dialog box appears indicating a communication error, use Remote Installation Manager to delete the failed packages and then re-execute packaging. |
| 13 | While a client was being registered into an ID group or being deleted from an ID group | After a dialog box appears indicating a communication error, re-execute registration into the ID group or deletion from the ID group. |
| 14 | While Package Setup Manager was installing a package | After the error is detected, reinstall the package. |
| 15 | While the Operation Log List window is displayed | Close the Operation Log List window, and then re-display it. |
| 16 | While Data maintenance and Take operation history tasks are executing | The tasks are cancelled. Re-execute the tasks. |
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.