Oracle B32100-01 Manual de usuario Pagina 183

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 258
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 182
Post-Installation Steps
Installing in High Availability Environments: OracleAS Cluster (Identity Management) 9-25
9.7.2 Changing the Ports for Oracle Internet Directory
Although it is recommended that the ports for the LDAP virtual server and the Oracle
Internet Directory are the same, it is possible for the ports to be different.
See the section "Changing Oracle Internet Directory Ports" in the Oracle Application
Server Administrators Guide for details on changing the Oracle Internet Directory ports.
9.7.3 Update targets.xml (Case 2 only)
The following configuration steps are needed only in the installation scenario
described in Section 9.4.2, "Case 2: Client ---[HTTPS]---> Load Balancer ---[HTTPS]--->
Oracle HTTP Server".
In this case the oracle_sso_server entry in the targets.xml file, on each physical host
of the cluster, must be reconfigured to monitor the local SSL port.
Perform the following steps to update targets.xml on each node of the cluster:
1. Back up the targets.xml file:
cp ORACLE_HOME/sysman/emd/targets.xml
ORACLE_HOME/sysman/emd/targets.xml.BACKUP
2. Open the file and find the oracle_sso_server target type. Within this target entry,
locate and edit the following two attributes:
HTTPPort - the server SSL port number
HTTPProtocol - the server protocol, which in this case is HTTPS
For example, you could update the two attributes this way:
<Property NAME="HTTPPort" VALUE="4443"/>
<Property NAME="HTTPProtocol" VALUE="HTTPS"/>
3. Save and close the file.
4. Reload the OracleAS console:
ORACLE_HOME/bin/emctl reload
Note: When choosing a multicast address, ensure that the address
does not collide with the addresses listed in:
http://www.iana.org/assignments/multicast-addresses
Also, if the low order 23 bits of an address is the same as the local
network control block, 224.0.0.0 – 224.0.0.255, then a collision may
occur. To avoid this problem, provide an address that does not have
the same bits in the lower 23 bits of the address as the addresses in
this range.
Note:
Keep in mind that the hostname should remain the same. Please do
not change the hostname.
Vista de pagina 182
1 2 ... 178 179 180 181 182 183 184 185 186 187 188 ... 257 258

Comentarios a estos manuales

Sin comentarios