Job Management Partner 1/Base User's Guide

12.1 Modifying settings for JP1/Base

The following table shows when changes made in JP1/Base settings during JP1/Base operation take effect. For details of how to modify settings, see the relevant section. In the See: column, the upper row indicates the relevant section for Windows and the lower row indicates that for UNIX.

Item When settings are reflected See:

JP1/Base troubleshooting settings If you modify settings for restarting an abnormally ended process, the new settings take effect when you restart JP1/Base or execute the reload command. 2.4.2

If you modify the settings for issuing a JP1 event at abnormal termination of a process controlled by the process management function or at failover of the authentication server, you must restart JP1/Base and the products that require JP1/Base (JP1/IM and JP1/AJS) after executing the command. 2.4.2

User management settings You can modify the authentication server settings while JP1/Base is active if no jobs, automated actions, or commands that use JP1/IM or JP1/AJS are being executed.
The new settings take effect when you click the OK button in the GUI or when you execute the command. 6.1.1

6.3.1

You can modify the JP1 user settings any time after the authentication server has started.
The new settings take effect when you click the OK button in the GUI or when you execute the command. However, if the JP1 user who changed the settings is still logged in, the new settings will not take effect until the JP1 user logs in again.
You do not need to restart JP1/Base. 6.1.2, 6.2.2

6.3.2

You can modify the authority levels for JP1 resource groups any time after the authentication server has started.
The new settings take effect when you click the OK button in the GUI or when you execute the command.
You do not need to restart JP1/Base. 6.1.3

6.3.3

If you are using a secondary authentication server, the settings take effect when you copy the setting files from the primary authentication server to the secondary authentication server. 6.1.4

6.3.4

You can modify the settings of login authentication linking with the directory server any time after the authentication server has started.
If you modify the settings in the directory server linkage definition file (jp1bs_ds_setup.conf), the new settings will take effect after you execute the command. 6.2.1

You can modify the user mapping settings without stopping JP1/Base.
The new settings take effect when you click the OK button in the GUI or when you execute the command. 6.1.6
6.1.7

6.3.5

Settings for service start and stop sequences (Windows only) If you modify the start sequence definition file (JP1SVPRM.DAT), the new settings take effect once you restart Windows. Start sequence definition file (Windows only)

Event service environment settings If you modify settings in the event server index file (index), the new settings take effect once you restart the event service. Event server index file

If you modify settings in the event server settings file (conf), the new settings take effect once you restart the event service. Event server settings file

If you modify settings in the forwarding settings file (forward), the new settings take effect once you execute the reload command. Forwarding settings file

If you modify settings in the API settings file (api), the new settings take effect once you restart the event service. API settings file

Event conversion settings If you modify settings in the action definition file for log file trapping, the definitions of some parameters take effect once you execute the reload command. Action definition file for log file trapping

If you modify settings in the action definition file for event log trapping (ntevent.conf), the new settings take effect once you execute the reload command. Action definition file for event log trapping (Windows only)

Health check settings If you modify settings in the health check definition file (jbshc.conf), the new settings take effect when you restart JP1/Base or execute the jbs_spmd_reload command. Health check definition file

Settings for Hitachi Network Objectplaza Trace Library (HNTRLib2) Settings take effect when you restart the Hitachi Network Objectplaza Trace Library (HNTRLib2). hntr2util (Windows only), hntr2util (UNIX only), hntr2conf, hntr2getconf

Communication settings If you modify jp1hosts information, the settings take effect once you execute the command and then restart JP1/Base. 4.3.2

If you modify the protocol for JP1/Base, the settings take effect once you execute the command and then restart JP1/Base, the products requiring JP1/Base (JP1/IM and JP1/AJS), and the programs that depend on JP1/Base. 4.3.3

If you modify the protocol for the event service, the settings take effect once you restart JP1/Base, the products requiring JP1/Base (JP1/IM and JP1/AJS), and the programs that depend on JP1/Base. 4.3.4

Local action functionality settings If you modify settings in the local action execution definition file, the new settings will take effect after you start or reload JP1/Base. Local action execution definition file

Item	When settings are reflected	See:
JP1/Base troubleshooting settings	If you modify settings for restarting an abnormally ended process, the new settings take effect when you restart JP1/Base or execute the reload command.	2.4.2
If you modify the settings for issuing a JP1 event at abnormal termination of a process controlled by the process management function or at failover of the authentication server, you must restart JP1/Base and the products that require JP1/Base (JP1/IM and JP1/AJS) after executing the command.	2.4.2
User management settings	You can modify the authentication server settings while JP1/Base is active if no jobs, automated actions, or commands that use JP1/IM or JP1/AJS are being executed. The new settings take effect when you click the OK button in the GUI or when you execute the command.	6.1.1
6.3.1
You can modify the JP1 user settings any time after the authentication server has started. The new settings take effect when you click the OK button in the GUI or when you execute the command. However, if the JP1 user who changed the settings is still logged in, the new settings will not take effect until the JP1 user logs in again. You do not need to restart JP1/Base.	6.1.2, 6.2.2
6.3.2
You can modify the authority levels for JP1 resource groups any time after the authentication server has started. The new settings take effect when you click the OK button in the GUI or when you execute the command. You do not need to restart JP1/Base.	6.1.3
6.3.3
If you are using a secondary authentication server, the settings take effect when you copy the setting files from the primary authentication server to the secondary authentication server.	6.1.4
6.3.4
You can modify the settings of login authentication linking with the directory server any time after the authentication server has started. If you modify the settings in the directory server linkage definition file (jp1bs_ds_setup.conf), the new settings will take effect after you execute the command.	6.2.1
You can modify the user mapping settings without stopping JP1/Base. The new settings take effect when you click the OK button in the GUI or when you execute the command.	6.1.6 6.1.7
6.3.5
Settings for service start and stop sequences (Windows only)	If you modify the start sequence definition file (JP1SVPRM.DAT), the new settings take effect once you restart Windows.	Start sequence definition file (Windows only)
Event service environment settings	If you modify settings in the event server index file (index), the new settings take effect once you restart the event service.	Event server index file
If you modify settings in the event server settings file (conf), the new settings take effect once you restart the event service.	Event server settings file
If you modify settings in the forwarding settings file (forward), the new settings take effect once you execute the reload command.	Forwarding settings file
If you modify settings in the API settings file (api), the new settings take effect once you restart the event service.	API settings file
Event conversion settings	If you modify settings in the action definition file for log file trapping, the definitions of some parameters take effect once you execute the reload command.	Action definition file for log file trapping
If you modify settings in the action definition file for event log trapping (ntevent.conf), the new settings take effect once you execute the reload command.	Action definition file for event log trapping (Windows only)
Health check settings	If you modify settings in the health check definition file (jbshc.conf), the new settings take effect when you restart JP1/Base or execute the jbs_spmd_reload command.	Health check definition file
Settings for Hitachi Network Objectplaza Trace Library (HNTRLib2)	Settings take effect when you restart the Hitachi Network Objectplaza Trace Library (HNTRLib2).	hntr2util (Windows only), hntr2util (UNIX only), hntr2conf, hntr2getconf
Communication settings	If you modify jp1hosts information, the settings take effect once you execute the command and then restart JP1/Base.	4.3.2
If you modify the protocol for JP1/Base, the settings take effect once you execute the command and then restart JP1/Base, the products requiring JP1/Base (JP1/IM and JP1/AJS), and the programs that depend on JP1/Base.	4.3.3
If you modify the protocol for the event service, the settings take effect once you restart JP1/Base, the products requiring JP1/Base (JP1/IM and JP1/AJS), and the programs that depend on JP1/Base.	4.3.4
Local action functionality settings	If you modify settings in the local action execution definition file, the new settings will take effect after you start or reload JP1/Base.	Local action execution definition file

[Contents][Back][Next]

[Trademarks]