14.1.1 When changes take effect
- Organization of this subsection
(1) When JP1/Base troubleshooting settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
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 |
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) When user management settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
You can modify settings for the authentication server while JP1/Base is active provided that no JP1 products are using JP1/Base user authentication. The new settings take effect when you click the OK button in the GUI or when you execute the command. |
|
2 |
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. |
|
3 |
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. |
|
4 |
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. |
|
5 |
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 |
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. |
(3) When changes to service start and stop sequences take effect (Windows only)
No. |
When settings are reflected |
See: |
---|---|---|
1 |
If you modify the start sequence definition file (JP1SVPRM.DAT), the new settings take effect once you restart Windows. |
(4) When changes to the event service environment take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
If you modify settings in the event server index file (index), the new settings take effect once you restart the event service. |
|
2 |
If you modify settings in the event server settings file (conf), the new settings take effect once you restart the event service. |
|
3 |
If you modify settings in the forwarding settings file (forward), the new settings take effect once you execute the reload command. |
|
4 |
If you modify settings in the API settings file (api), the new settings take effect once you start or restart the event conversion functionality or a program (such as JP1/IM and JP1/AJS) that is linked with the event service. |
(5) When changes to event conversion settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
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. |
|
2 |
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) |
(6) When changes to the health check function take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
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. |
(7) When changes to Hitachi Network Objectplaza Trace Library (HNTRLib2) settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
Settings take effect when you restart the Hitachi Network Objectplaza Trace Library (HNTRLib2). |
(8) When changes to communication settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
If you modify jp1hosts information, the settings take effect once you execute the command and then restart JP1/Base. |
|
2 |
If you modify jp1hosts2 information, the settings take effect when you execute the command. However, when you change the following settings, the new setting will not take effect until you restart JP1/Base:
|
|
3 |
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 |
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. |
(9) When changes to local action function settings take effect
No. |
When settings are reflected |
See: |
---|---|---|
1 |
If you modify settings in the local action execution definition file, the new settings will take effect after you start or reload JP1/Base. |