weblogic修改hostname

Host Name or IP Address Change

http://docs.oracle.com/cd/E12890_01/ales/docs32/HowTo/reconfigure.html#wp1079877

This section describes post-installation configuration changes. The following topics are described:

•  Configuration for New Host Name
•  Configuration for a New IP Address

 

---

Configuration for New Host Name

This section describes how to reconfigure components if you change the host name of the system on which the Administration Server is installed.

•  Administration Server Host Name Change
•  SSM Machine Host Name Change
•  Server and SSM On Same Host

Administration Server Host Name Change

This section provides instructions for modifying the necessary files when the Administration Server’s host name is changed.

1.  Shut down the Administration Server and SCM.
2.  In BEA_HOME/ales32-scm/apps/scm-asi/sar-inf/config.xml, update the host name in the following settings:

<listener host="<hostname>"
<proxy best="<hostname>"
<pd best="<hostname>"
)<scm domain="asi" localName="adminconfig", instanceName="SCM.< hostname>.asi"/>

1.  In BEA_HOME/ales32-admin/bin/WLESadmin.bat, update the host name in the following settings:

https://<hostname>:7011/services/ManagedServer
https://<hostname>:7013

1.  In BEA_HOME/ales32-admin/config/WLESWebLogic.conf, update the host name in the following settings:

1.  Change https://<hostname> to https://<hostname>.

1.  In BEA_HOME/ales32-admin/config/WLESarme.properties, update the host name in the following settings:

https://<hostname>
instanceName = ARME.admin.server.asi.<hostname>

1.  In BEA_HOME/ales32-admin/config/WLESblm.properties, update the host name in the following setting:

BLM.host = <hostname>

1.  In BEA_HOME/ales32-admin/config/asi.properties, update the host name in the following settings:

ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses

1.  On the SSM machines, update the host name in the following files:

BEA_HOME/ales32-ssm/<ssm>/adm/ssm_install.properties
BEA_HOME/ales32-ssm/<ssm>/template/adm/ssm_instance.properties
BEA_HOME/ales32-ssm/<ssm>/template/config/WLESarme.properties

1.  Modify the policy database (Oracle and Sybase) to specify the new IP address.

For Sybase, assuming a username of wles, a password of password, and a sybase server name of MYHOST, perform the following steps:

1.  Start one command window and run isql -Dwles -Ppassword -SMYHOST.
2.  Run select * from engine_addresses to verify the old address are being used.
3.  Delete the records in the engnie_addresses table that refer to the old address.

For Oracle:

1.  sqlplus wles/password@ASI
2.  select * from engine_address;
3.  truncate table engine_addresses;

1.  If an SSM was enrolled in secure mode, shut it down and run enroll.bat secure to enroll it with the new host name.

SSM Machine Host Name Change

This section provides instructions for modifying the necessary files when a SSM’s host name is changed.

1.  If the SSM is enrolled in secure mode, run unenroll.bat secure before you change the host name.
2.  Update the following settings in BEA_HOME/ales32-ssm/<ssm>/adm/silent_install_ssm.xml

<data-value name="SCM_PRIMARY_ADMIN_URL" value="https://<hostname>:7010/" />

<data-value name="SCM_BACKUP_ADMIN_URL" value="https://<hostname>:7010/" />

1.  Modify BEA_HOME/ales32-ssm/<ssm>/template/adm/ssm_instance.properties, update the host name in the following setting:

host.name = <hostname>

If the host name of the Administration Server machine is also changed, update the admin.host setting.

1.  For WebLogic SSMs, update the following setting in BEA_HOME/ales32-ssm/<ssm>/template/bin/set-wls-env.bat.

-Dwles.config.signer=<hostname>

1.  Update the host name in BEA_HOME/ales32-ssm/<ssm>/template/WLESWeblogic.conf or WLESws.wrapper.conf.
2.  In BEA_HOME/ales32-ssm/<ssm>/template/config/WLESarme.properties, update the host name in the following settings:

PDAddress = https://<hostname> 
instanceName = ARME.....asi.<hostname>

1.  Re-enroll the SSM in secure mode.

Server and SSM On Same Host

This section provides instructions for changing the necessary files when the Administration Server and an SSM are running in separate BEAHOMES on the same machine.

•  WebLogic Server
•  Apache Tomcat

WebLogic Server

In this scenario, the Administration Server and an SSM are running in separate WebLogic servers on the same machine. Each component uses a separate BEAHOME. In the steps that follow the Administration Server is in BEAHOME1 and the SSM is in BEAHOME2.

Follow these steps:

1.  If the SSM is enrolled in ‘secure’ mode, run unenroll.bat secure.
2.  Shut down all services, including the Administration Server, SCM, and SSM instance. If a component was started in console mode, type CTRL-C to stop it.
3.  Modify BEA_HOME1/ales32-scm/apps/scm-asi/sar-inf/config.xml, update the host name in the following settings:

<listener host="<hostname>" port="7013" protocol="https">
<proxy best="<hostname>" port="7011" protocol="https">
<pd best="<hostname>" port="7011" protocol="https">
<scm domain="asi" localName="adminconfig", instanceName="SCM.<hostname>.asi"/>

1.  In BEA_HOME1/ales32-admin/config/WLESadmin.bat, update the host name in the following settings:

https://<hostname>:7011/services/ManagedServer
https://<hostname>:7013 to https://<hostname>:7013
https://<hostname>:7013

1.  In BEA_HOME1/ales32-admin/config/WLESWebLogic.conf, update the host name in the following setting:

https://<hostname>

1.  In BEA_HOME1/ales32-admin/config/WLESarme.properties, update the host name in the following settings:

PDAddress = https://<hostname>
instanceName = ARME.admin.server.asi.<hostname>

1.  In BEA_HOME1/ales32-admin/config/WLESblm.properties, update the host name in the following setting:

BLM.host = <hostname>

1.  Modify BEA_HOME1/ales32-admin/config/asi.properties to replace the old host name for the following:

ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses

1.  In BEA_HOME2/ales32-ssm/<ssm>/adm/ssm_install.properties, update the host name in the following settings:

host.name = <hostname>
full.host.name = <full hostname>
admin.host = <hostname>
scm.primary.admin.url = https://<hostname>:7010
scm.backup.admin.url = https://<hostname>:7010

1.  In BEA_HOME2/ales32-ssm/<ssm>/adm/silient_install_ssm.xml as follows:

<data-value name="SCM_PRIMARY_ADMIN_URL" value="https://<hostnamename>:7010/" />

<data-value name="SCM_BACKUP_ADMIN_URL" value="https://<hostname>:7010/" />

1.  In BEA_HOME2/ales32-ssm/<ssm>/template/adm/ssm_instance.properties, update the host name in the following settings:

host.name = <hostname>
admin.host = <hostname>

1.  For WebLogic SSMs, change the following settings in BEA_HOME2/ales32-ssm/<wls ssm>/template/bin/set-wls-env.bat:

-Dwles.config.signer=

1.  Replace the host name in BEA_HOME2/ales32-ssm/<ssm>/template/config/WLESWeblogic.conf or WLESws.wrapper.conf.
2.  In BEA_HOME2/ales32-ssm/<ssm>/template/config/WLESarme.properties, replace the host name in the following settings:

PDAddress = https://<hostname> 
instanceName = ARME.....asi.<hostname>

1.  Modify the policy database (Oracle and Sybase) to specify the new IP address.

For Sybase, assuming a username of wles, a password of password, and a sybase server name of MYHOST, perform the following steps:

1.  Start one command window and run isql -Dwles -Ppassword -SMYHOST.
2.  Run select * from engine_addresses to verify the old address are being used.
3.  Delete the records in the engnie_addresses table that refer to the old address.

For Oracle, the steps are similar to those for Sybase:

1.  sqlplus wles/password@ASI
2.  select * from engine_address;
3.  truncate table engine_addresses;

1.  If the SSM was enrolled in ‘secure’ mode, run enroll.bat secure to enroll the SSM instance with the new host name.

Apache Tomcat

In this scenario, the Administration Server and an SSM are running in separate Tomcat applications on the same machine. Each component uses a separate BEAHOME. In the steps that follow the Administration Server is in BEAHOME1 and the SSM is in BEAHOME2.

Follow these steps:

1.  If the SSM is enrolled in ‘secure’ mode, run unenroll.bat secure.
2.  Shut down all services, including the Administration Server, SCM, and SSM instance. If a component was started in console mode, type CTRL-C to stop it.
3.  In BEA_HOME1/ales32-scm/apps/scm-asi/sar-inf/config.xml update the host name in the following settings:

<listener host="<hostname>" port="7013" protocol="https">
<proxy best="<hostname>" port="7011" protocol="https">
<pd best="<hostname>" port="7011" protocol="https">
<scm domain="asi" localName="adminconfig", instanceName="SCM.<hostname>.asi"/>

1.  In BEA_HOME1/ales32-admin/bin/WLESadmin.bat, update the host name in the following settings:

https://<hostname>:7011/services/ManagedServer
https://<hostname>:7013

1.  In BEA_HOME1/ales32-admin/config/WLESTomcat.conf, update the host name in the following setting:

Change https://<hostname>

1.  In BEA_HOME1/ales32-admin/config/WLESarme.properties, update the host name in the following settings:

PDAddress = https://<hostname> 
instanceName = ARME.admin.server.asi.<hostname>

1.  In BEA_HOME1/ales32-admin/config/WLESblm.properties, update the host name in the following setting:

BLM.host = <hostname>

1.  In BEA_HOME1/ales32-admin/config/asi.properties, update the host name in the following settings:

ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses

1.  In BEA_HOME2/ales32-ssm/<ssm>/adm/ssm_install.properties, update the following settings:

host.name = <hostname>
admin.host = <hostname>
scm.primary.admin.url = https://<hostname>:7010
scm.backup.admin.url = https://<hostname>:7010

1.  In BEA_HOME2/ales32-ssm/<ssm>/adm/silent_install_ssm.xml, update the following:

<data-value name="SCM_PRIMARY_ADMIN_URL" value="https://<hostname>:7010/" />
<data-value name="SCM_BACKUP_ADMIN_URL" value="https://<hostname>:7010/" />

1.  In BEA_HOME2/ales32-ssm/<ssm>/template/adm/ssm_instance.properties, update the following settings:

host.name = <hostname>
admin.host = <hostname>

1.  Update the host name in BEA_HOME2/ales32-ssm/<ssm>/template/config/WLESTomcat.conf or WLESws.wrapper.conf.
2.  In BEA_HOME2/ales32-ssm/<ssm>/template/config/WLESarme.properties, update the host name in the following setting:

PDAddress = https://<hostname>
instanceName = ARME.....asi.<hostname>

1.  Modify the policy database (Oracle and Sybase) to specify the new IP address.

For Sybase, assuming a username of wles, a password of password, and a sybase server name of MYHOST, perform the following steps:

1.  Start a command window and run isql -Dwles -Ppassword -SMYHOST.
2.  Run select * from engine_addresses to verify the old address are being used.
3.  Delete the records in the engnie_addresses table that refer to the old address.

For Oracle:

1.  sqlplus wles/password@ASI
2.  select * from engine_address;
3.  truncate table engine_addresses;

1.  If the SSM was enrolled in ‘secure’ mode, re-enroll it.

 

---

Configuration for a New IP Address

This section describes how to reconfigure OES components if the IP address is subsequently changed. The steps you follow depend on how the OES components are installed:

•  Administration Server IP Address Change
•  SSM IP Address Change

Administration Server IP Address Change

If the host IP of the Administration Server and SCM is changed, follow these steps.

1.  Shut down the Administration Server and SCM.
2.  Update the following settings in BEA_HOME/ales32-scm/config/SCM.properties:

OS.interface = <ipaddress>

1.  Modify BEA_HOME/ales32-ssm/<ssm>/adm/ssm_install.properties to replace the old IP address with the new IP address in the following line:

scm.interface.list = 10.120.3.140

1.  Restart the SCM, Administration Server, and the SSM.

SSM IP Address Change

If the host IP of the SSM is changed, follow these steps.

1.  Modify BEA_HOME/ales32-ssm/<ssm>/adm/ssm_install.properties to replace the old IP address in the following line:

scm.interface.list = 10.120.3.140

1.  Restart the SCM, the Administration Server, and the SSM.