This section describes post-installation configuration changes. The following topics are described:
This section describes how to reconfigure components if you change the host name of the system on which the Administration Server is installed.
This section provides instructions for modifying the necessary files when the Administration Server’s host name is changed.
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"/>
BEA_HOME
/ales32-admin/bin/WLESadmin.bat
, update the host name in the following settings:
https://
<hostname>
:7011/services/ManagedServer
https://<hostname>
:7013
BEA_HOME
/ales32-admin
/config/WLESWebLogic.conf
, update the host name in the following settings:BEA_HOME
/ales32-admin/config/WLESarme.properties
, update the host name in the following settings:
https://
<hostname>
instanceName = ARME.admin.server.asi.
<hostname>
BEA_HOME
/ales32-admin
/config/WLESblm.properties
, update the host name in the following setting:BEA_HOME
/ales32-admin/config/asi.properties
, update the host name in the following settings:
ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses
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
For Sybase, assuming a username of wles
, a password of password
, and a sybase server name of MYHOST
, perform the following steps:
isql -Dwles -Ppassword -SMYHOST
.select * from engine_addresses
to verify the old address are being used.engnie_addresses
table that refer to the old address.sqlplus wles/password@ASI
select * from engine_address;
truncate table engine_addresses;
enroll.bat
secure
to enroll it with the new host name.This section provides instructions for modifying the necessary files when a SSM’s host name is changed.
unenroll.bat
secure
before you change the host name.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/" />
BEA_HOME
/ales32-ssm/<
ssm>/template/
adm/ssm_instance.properties
, update the host name in the following setting:
If the host name of the Administration Server machine is also changed, update the admin.host
setting.
BEA_HOME
/ales32-ssm/<
ssm>/template
/bin/set-wls-env.bat
.
-Dwles.config.signer=
<hostname>
BEA_HOME
/ales32-ssm/<
ssm>/
template/WLESWeblogic.conf
or WLESws.wrapper.conf
.BEA_HOME
/ales32-ssm/<
ssm>
/template/config/WLESarme.properties
, update the host name in the following settings:
PDAddress = https://
<hostname>
instanceName = ARME.....asi.<
hostname
>
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.
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.
unenroll.bat secure
.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"/>
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
BEA_HOME1
/ales32-admin
/config/WLESWebLogic.conf
, update the host name in the following setting:BEA_HOME1
/ales32-admin/config/WLESarme.properties
, update the host name in the following settings:
PDAddress = https://
<hostname>
instanceName = ARME.admin.server.asi.
<hostname>
BEA_HOME1
/ales32-admin
/config/WLESblm.properties
, update the host name in the following setting:BEA_HOME1
/ales32-admin/config/asi.properties
to replace the old host name for the following:
ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses
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
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/" />
BEA_HOME2
/ales32-ssm/<
ssm>/template/
adm/ssm_instance.properties
, update the host name in the following settings:
host.name =
<hostname>
admin.host =
<hostname>
BEA_HOME2
/ales32-ssm/<wls
ssm>/template/
bin/set-wls-env.bat
:BEA_HOME2
/ales32-ssm/<
ssm>/template/
config/WLESWeblogic.conf
or WLESws.wrapper.conf
.BEA_HOME2
/ales32-ssm/<
ssm>/template/
config/WLESarme.properties
, replace the host name in the following settings:
PDAddress = https://
<hostname>
instanceName = ARME.....asi.<
hostname>
For Sybase, assuming a username of wles
, a password of password
, and a sybase server name of MYHOST
, perform the following steps:
isql -Dwles -Ppassword -SMYHOST
.select * from engine_addresses
to verify the old address are being used.engnie_addresses
table that refer to the old address.For Oracle, the steps are similar to those for Sybase:
sqlplus wles/password@ASI
select * from engine_address;
truncate table engine_addresses;
enroll.bat
secure
to enroll the SSM instance with the new host name.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.
unenroll.bat secure
.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"/>
BEA_HOME1
/ales32-admin/bin/WLESadmin.bat
, update the host name in the following settings:
https://
<hostname>
:7011/services/ManagedServer
https://<hostname>
:7013
BEA_HOME1
/ales32-admin
/config/WLESTomcat.conf
, update the host name in the following setting:BEA_HOME1
/ales32-admin/config/WLESarme.properties
, update the host name in the following settings:
PDAddress = https://
<hostname>
instanceName = ARME.admin.server.asi.
<hostname>
BEA_HOME1
/ales32-admin
/config/WLESblm.properties
, update the host name in the following setting:BEA_HOME1
/ales32-admin/config/asi.properties
, update the host name in the following settings:
ASI.BLMAddresses
ASI.ARMEAddresses
ASI.PDAddresses
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
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/" />
BEA_HOME2
/ales32-ssm/<
ssm>/template/
adm/ssm_instance.properties
, update the following settings:
host.name =
<hostname>
admin.host =
<hostname>
BEA_HOME2
/ales32-ssm/<
ssm>/template/
config/WLESTomcat.conf
or WLESws.wrapper.conf
.BEA_HOME2
/ales32-ssm/<
ssm>/template/
config/WLESarme.properties
, update the host name in the following setting:
PDAddress = https://
<hostname>
instanceName = ARME.....asi.<
hostname
>
For Sybase, assuming a username of wles
, a password of password
, and a sybase server name of MYHOST
, perform the following steps:
isql -Dwles -Ppassword -SMYHOST
.select * from engine_addresses
to verify the old address are being used.engnie_addresses
table that refer to the old address.sqlplus wles/password@ASI
select * from engine_address;
truncate table engine_addresses;
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:
If the host IP of the Administration Server and SCM is changed, follow these steps.
BEA_HOME
/ales32-scm/config/SCM.properties
: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
If the host IP of the SSM is changed, follow these steps.