If the ETERNUS DX S2 series that is registered in the Management Server is deleted and removed as a management target, the required work is as follows.
Point
Perform the work after confirming that the ETERNUS DX S2 series is not registered in the Management Server.
For Windows environments
Log on to the Management Server using Administrator privileges.
Stop the ETERNUS SF Manager service.
When the Management Server is in a non-clustered system
Execute the following batch to stop the ETERNUS SF Manager service.
> $INS_DIR\Common\bin\Stop_ESFservice.bat
From this step onward, $INS_DIR is "Program Directory" specified at the ETERNUS SF Manager installation.
When the Management Server is in a clustered system
Use the Failover Cluster Manager to stop the ETERNUS SF Manager service.
Copy the following file over the copy destination file.
To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.
Copy Source File | Copy Destination File |
|---|---|
$INS_DIR\Common\sys\tomcat\webapps\esf\WEB-INF\config\java.security | $INS_DIR\Common\jre\conf\security\java.security |
$INS_DIR\CCM\tools\java.security | $INS_DIR\CCM\jre\conf\security\java.security |
Start the ETERNUS SF Manager service.
When the Management Server is in a non-clustered system
Execute the following batch to start the ETERNUS SF Manager service.
> $INS_DIR\Common\bin\Start_ESFservice.bat
When the Management Server is in a clustered system
Use the Failover Cluster Manager to start the ETERNUS SF Manager service.
For Solaris or Linux environments
Log in to the Management Server as a superuser.
Stop the ETERNUS SF Manager daemon.
When the Management Server is in a non-clustered system
Execute the following command to stop the ETERNUS SF Manager daemon.
# /opt/FJSVesfcm/bin/stopesf.sh
When the Management Server is in a clustered system
Use the cluster software in use to stop ETERNUS SF Manager daemon.
Copy the following file over the copy destination file.
To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.
For Solaris environments
Copy Source File | Copy Destination File |
|---|---|
/opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security | /opt/FJSVesfcm/JRE/lib/security/java.security |
/opt/FJSVcccm/tools/java.security | /opt/FJSVccm/jre/lib/security/java.security |
The command execution example is as follows.
# cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security /opt/FJSVesfcm/JRE/lib/security/java.security # cp -p /opt/FJSVccm/tools/java.security /opt/FJSVccm/jre/lib/security/java.security
For Linux environments
Copy Source File | Copy Destination File |
|---|---|
/opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security | /opt/FJSVesfcm/JRE/conf/security/java.security |
/opt/FJSVccm/tools/java.security | /opt/FJSVccm/jre/conf/security/java.security |
The command execution example is as follows.
# cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security /opt/FJSVesfcm/JRE/conf/security/java.security # cp -p /opt/FJSVccm/tools/java.security /opt/FJSVccm/jre/conf/security/java.security
Start the ETERNUS SF Manager daemon.
When the Management Server is in a non-clustered system
Execute the following command to start the ETERNUS SF Manager daemon.
# /opt/FJSVesfcm/bin/startesf.sh
When the Management Server is in a clustered system
Use the cluster software in use to start ETERNUS SF Manager daemon.
