A Using the Portal Dependency Settings Tool and File

A.1.1 Configuration Mode

Updates a specific OracleAS Portal instance from the Portal Dependency Settings file.

A.1.2 Encryption Mode

Encrypts any plain text passwords in the Portal Dependency Settings file. For example:

ptlconfig -encrypt

A.1.3 Load Mode

Creates and updates entries in iasconfig.xml with the configuration settings of a specific portal schema.

A.2.1 Name and Location

The name of the Portal Dependency Settings file is iasconfig.xml, and is located by default in ORACLE_HOME/portal/conf, where ORACLE_HOME is the OracleAS Portal and Oracle Application Server Wireless middle-tier home.

When using any of the tools that access the Portal Dependency Settings file, you can override the default location of the file by setting the environment variable IASCONFIG_LOC to the directory in which your file is stored, for example:

set IASCONFIG_LOC=/usr/local/as101202

A.2.2 Configuration Elements

The Portal Dependency Settings file is an XML file, that is made up of a number of elements that describe the settings of specific Oracle Application Server components and the dependencies portal instances have on them. Figure A-1 shows all the elements that can be modeled in the Portal Dependency Settings file. The Portal Dependency Settings file definition is modeled in the schema file iasconfig.xsd, which is located in ORACLE_HOME/portal/conf.

Figure A-1 Elements in the Portal Dependency Settings file

Description of "Figure A-1 Elements in the Portal Dependency Settings file"

The individual elements are:

• IASFarm

• IASInstance

• PortalInstance

• WebCacheComponent

• OIDComponent

• EMComponent

• WebCacheDependency

• OIDDependency

• EMDependency

IASFarm

The IASFarm element represents a logical farm of Oracle Application Server instances, commonly used when modeling a multiple middle-tier scenario front-ended by a load balancing router (LBR). See Section 5.3, "Configuring Multiple Middle Tiers with a Load Balancing Router" for more information.

IASInstance

The IASInstance element represents a specific Oracle Application Server instance, which usually maps to an Oracle home.

PortalInstance

These are the OracleAS Portal instance settings.

WebCacheComponent

These are the OracleAS Web Cache settings.

OIDComponent

These are the Oracle Internet Directory settings.

EMComponent

These are the Oracle Enterprise Manager 10g Application Server Control Console settings.

WebCacheDependency

This is the OracleAS Portal instance reference to the OracleAS Web Cache it is using.

OIDDependency

This is the OracleAS Portal instance reference to the Oracle Internet Directory it is using.

EMDependency

This is the Oracle Enterprise Manager 10g Application Server Control Console managing this OracleAS Portal instance.

A.2.3 Sample Portal Dependency Settings File

The XML in Example A-1 represents the contents of a sample Portal Dependency Settings file.

<IASConfig XSDVersion="1.0">

   <IASInstance Name="iAS-1.abc.company.com" Host="abc.company.com">
      <WebCacheComponent ListenPort="3002" InvalidationPort="3003" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false"/>
   </IASInstance>

   <IASInstance Name="iAS-2.abc.company.com" Host="xyz.company.com">
      <OIDComponent AdminPassword="welcome1" PortSSLEnabled="false" LDAPPort="3002" AdminDN="cn=orcladmin"/>
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>

   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="welcome1" ConnectString="xyz.company.com:1521:s901dev3">
      <WebCacheDependency ContainerType="IASInstance" Name="iAS-1.abc.company.com"/>
      <OIDDependency ContainerType="IASInstance" Name="iAS-2.abc.company.com"/>
      <EMDependency ContainerType="IASInstance" Name="iAS-1.abc.company.com"/>
   </PortalInstance>

</IASConfig>

In this example, the OracleAS Portal instance is:

• Accessed from the Database Access Descriptor (DAD) /pls/portal.

• Dependent on:

  • OracleAS Web Cache component running in Oracle Application Server instance iAS-1

  • Oracle Internet Directory component running in Oracle Application Server instance iAS-2

  • Oracle Enterprise Manager 10g Application Server Control Console component running in Oracle Application Server instance iAS-1

A.2.4 Updating the Portal Dependency Settings File

If the Portal Dependency Settings file is accessible over a network file system, you can share the file across multiple hosts, avoiding the need to manually replicate it every time the file is modified. If the installation is running on an operating system which supports symbolic links, it is recommended that you use this mechanism to reference a shared file, instead of setting the IASCONFIG_LOC environment variable.

If, however, the Portal Dependency Settings file is not accessible over the network, you must ensure that the file is kept up-to-date with changes to your site topology. The Portal Dependency Settings file is used to configure the OracleAS Portal schema with details of OracleAS Web Cache, Oracle Internet Directory, and Oracle Enterprise Manager 10g that it is using. It is not required that it is copied into each individual middle tier in your site, but you must ensure that any changes to the components modeled in the file that affect OracleAS Portal configuration are updated in the file.

Let's use the configuration defined in Section 5.3, "Configuring Multiple Middle Tiers with a Load Balancing Router", to demonstrate how the Portal Dependency Settings file is kept up-to-date.

1. The Portal Dependency Settings file gets first created in Section 5.3.1, "Step 1: Install a Single Portal and Wireless Middle Tier (M1)", during the installation. Example 5-1, "iasconfig.xml After the First Middle-Tier Installation" shows how it looks.

   This file will be located on computer m1.abc.com, typically in ORACLE_HOME/portal/conf of the middle tier that has just been installed.

2. In Section 5.3.1, "Step 1: Install a Single Portal and Wireless Middle Tier (M1)", the Portal Dependency Settings file is manually changed. Example 5-2, "iasconfig.xml File Edited to Include Farm Element" shows this.

   This file will be on computer m1.abc.com, typically in ORACLE_HOME/portal/conf of the middle tier installed in Step 1. You use the ptlconfig tool as shown in Section A.1, "Portal Dependency Settings Tool", after you make changes to the file. For example:

   ptlconfig -dad <portal_dadname> -wc -site
   
   

   Any future changes to the OracleAS Web Cache, Oracle Internet Directory, or Oracle Enterprise Manager 10g settings in iasconfig.xml should be made using the Application Server Control Console, or manually on m1.abc.com. If you edit iasconfig.xml manually, then you must also use the ptlconfig tool again after you make changes.

   
   

   Note: Changes to OracleAS Portal's OracleAS Web Cache settings can also be made on the Portal Web Cache Settings page. See Section 7.3.3, "Portal Web Cache Settings Link" for more information. Typically, the host name and port number, by which OracleAS Portal is addressed, uses the OracleAS Web Cache host name and port number. This is because, in a simple configuration, browser requests go directly to OracleAS Web Cache. However, in a configuration that has a load balancing router (LBR), or reverse proxy server front-ending OracleAS Web Cache, the host name and port number defined on this page may need to reflect that of the LBR, or reverse proxy server. In this configuration, you want OracleAS Web Cache invalidation messages to be sent directly to the OracleAS Web Cache host, as opposed to the LBR, or reverse proxy server. In the scenario where your published host name is different from the host name used for OracleAS Web Cache invalidation, you can use the Portal Dependency Settings file iasconfig.xml to establish these settings. See the section "Specify the OracleAS Portal Published Address and Protocol" for details.

   
   

3. In Section 5.3.5, "Step 5: Configure the New Middle Tier (M2) to Run Your Existing Portal", the Portal Dependency Settings file on m2.abc.com needs to be updated manually with the settings defined in the iasconfig.xml file on m2.abc.com.

Specify the OracleAS Portal Published Address and Protocol

Typically, the host name and port number, by which OracleAS Portal is addressed, uses the OracleAS Web Cache host name and port number. This is because, in a simple configuration, browser requests go directly to OracleAS Web Cache. However, in a configuration that has a reverse proxy server front-ending OracleAS Web Cache, the host name and port number defined should reflect that of the reverse proxy server.

In this configuration, you want OracleAS Web Cache invalidation messages to be sent directly to the OracleAS Web Cache host, as opposed to the reverse proxy server. In the scenario where your published host name is different from the host name used for OracleAS Web Cache invalidation, you can use the Portal Dependency Settings file, to establish these settings.

To configure this appropriately, perform the following steps:

1. Edit iasconfig.xml (located by default in ORACLE_HOME/portal/conf) and specify a new property, InvalidationHost, within the WebCacheDependency element. The InvalidationHost property should point to the OracleAS Web Cache host. A sample WebCacheDependency entry in iasconfig.xml would look like this:

   <WebCacheDependency ContainerType="IASInstance" Name="Farm-1.abc.com" InvalidationHost="internal.company.com"/>
   
   

2. To prevent access to Oracle Enterprise Manager 10g from the outside, the Oracle Enterprise Manager 10g link provided by OracleAS Portal needs to be changed back to point to the internal server. To do this, edit iasconfig.xml and:

   1. Add a new IASInstance element pointing to the OracleAS Web Cache host. This element should contain the EMComponent entry.

   2. Set the EMDependency entry to point to the internal server.

   An example is shown here:

   <IASInstance Name="iAS.internal.company.com" Host="internal.company.com"> 
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>
   
   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal"
   SchemaPassword="@Beyh8p2bOWELQCsA5zRtuYc=" ConnectString="cn=iasdb,cn=oraclecontext">
      <EMDependency ContainerType="IASInstance" Name="iAS.internal.company.com"/> 
   </PortalInstance>
   
   

3. Run ptlconfig (typically located in the directory MID_TIER_ORACLE_HOME/portal/conf) as shown in the following example:

   ptlconfig -dad portal -site -wc -em
   
   

4. Optionally, re-register the Wireless gateway URL with the load-balancer's address. See Section 5.11, "Configuring OracleAS Wireless" for more information.

A.2.5 Post-Installation Mapping in the Portal Dependency Setting File

When OracleAS Portal is installed, appropriate entries are created in the Portal Dependency Settings file, based on what is installed.

In an Application Server installation, the dependencies of OracleAS Portal on Oracle Application Server Web Cache and Oracle Internet Directory are added to the Portal Dependency Settings file. Existing information is not updated if duplicate entries are encountered during the installation. Instead, a warning is output to the installation log file that the entries already exist.

In a single computer OracleAS Portal and OracleAS Wireless installation, where OracleAS Web Cache and Oracle Internet Directory instances already reside on the same computer, entries to the Portal Dependency Settings file are created as shown in Example A-2:

<IASConfig XSDVersion="1.0">

   <IASInstance Name="iAS-1.abc.company.com" Host="abc.company.com">
      <OIDComponent AdminPassword="welcome1" PortSSLEnabled="false" LDAPPort="3002" AdminDN="cn=orcladmin"/>
   </IASInstance>

   <IASInstance Name="iAS-2.abc.company.com" Host="abc.company.com">
      <WebCacheComponent ListenPort="3002" InvalidationPort="3003" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false"/>
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>

   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="welcome1" ConnectString="xyz.company.com:1521:s901dev3">
      <WebCacheDependency ContainerType="IASInstance" Name="iAS-2.abc.company.com"/>
      <OIDDependency ContainerType="IASInstance" Name="iAS-1.abc.company.com"/>
      <EMDependency ContainerType="IASInstance" Name="iAS-2.abc.company.com"/>
   </PortalInstance>

</IASConfig>

A.2.6 Common Configuration Mapping in the Portal Dependency Settings File

This section shows what the Portal Dependency Settings file looks like in the recommended topologies.

OracleAS Portal and OracleAS Wireless Developer Configuration: Medium Sized Computers

The topology for this common configuration is seen in Figure A-2.

Figure A-2 OracleAS Portal and OracleAS Wireless Developer Configuration

Description of "Figure A-2 OracleAS Portal and OracleAS Wireless Developer Configuration"

This configuration assumes that both the application server and the infrastructure are installed on the same computer, called Host 1.

When you install OracleAS Portal and OracleAS Wireless on Host 1 in ias.host1.xyz.com, referencing the Oracle Internet Directory instance in infra.host1.xyz.com, the Portal Dependency Settings file looks like Example A-3:

<IASConfig XSDVersion="1.0">

   <IASInstance Name="ias.host1.xyz.com" Host="host1.xyz.com">
      <WebCacheComponent ListenPort="7778" InvalidationPort="3003" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false"/>
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>

   <IASInstance Name="infra.host1.xyz.com" Host="host1.xyz.com">
      <OIDComponent AdminPassword="welcome1" PortSSLEnabled="false" LDAPPort="3002" AdminDN="cn=orcladmin"/>
   </IASInstance>

   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="welcome1" ConnectString="host1.xyz.com:1521:iasdb">
      <WebCacheDependency ContainerType="IASInstance" Name="ias.host1.xyz.com"/>
      <OIDDependency ContainerType="IASInstance" Name="infra.host1.xyz.com"/>
      <EMDependency ContainerType="IASInstance" Name="ias.host1.xyz.com"/>
   </PortalInstance>

</IASConfig>

Enterprise Data Center Configuration: Multiple Departments Sharing the Same Data Center

The topology for this common configuration is seen in Figure A-3.

Figure A-3 Enterprise Data Center Configuration

Description of "Figure A-3 Enterprise Data Center Configuration"

This configuration assumes that the application server and the infrastructure are installed on different computers.

As shown in Figure A-3, the OracleAS Web Cache cluster front-ending OracleAS Portal is not yet known. When you install the application server (OracleAS Portal and OracleAS Wireless installation) on host Host 1, referencing the Oracle Internet Directory on host Host 2, the configuration will look like Example A-4:

<IASConfig XSDVersion="1.0">

   <IASInstance Name="infra.host2.xyz.com" Host="host2.xyz.com">
      <OIDComponent AdminPassword="welcome1" PortSSLEnabled="false" LDAPPort="3002" AdminDN="cn=orcladmin"/>
   </IASInstance>

   <IASInstance Name="ias.host1.xyz.com" Host="host1.xyz.com">
      <WebCacheComponent ListenPort="7778" InvalidationPort="3003" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false"/>
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>

   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="welcome1" ConnectString="host1.xyz.com:1521:iasdb">
      <WebCacheDependency ContainerType="IASInstance" Name="ias.host1.xyz.com"/>
      <OIDDependency ContainerType="IASInstance" Name="infra.host2.xyz.com"/>
      <EMDependency ContainerType="IASInstance" Name="ias.host1.xyz.com"/>
   </PortalInstance>

</IASConfig>

If you want the application server on Host 1 to be front-ended by OracleAS Web Cache, you need to manually edit the Portal Dependency Settings file. First, remove the existing OracleAS Web Cache entry and then create an OracleAS Web Cache entry that belongs to a farm. The modified Portal Dependency Settings file will now look like Example A-5:

<IASConfig xmlns="http://www.oracle.com/iAS/iASConfigFile" XSDVersion="1.0">

   <IASInstance Name="infra.host2.xyz.com" Host="host2.xyz.com">
      <OIDComponent AdminPassword="welcome1" PortSSLEnabled="false" LDAPPPort="3002" AdminDN="cn=orcladmin"/>
   </IASInstance>

   <IASFarm name="Farm_1" host="frontend.xyz.com">
      <WebCacheComponent ListenPort="7778" InvalidationPort="3003" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false"/>
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASFarm>

   <IASInstance Name="ias.host1.xyz.com" Host="host1.xyz.com">
      <EMComponent ConsoleHTTPPort="1814" SSLEnabled="false"/>
   </IASInstance>

   <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="welcome1" ConnectString="host1.xyz.com:1521:iasdb">
      <WebCacheDependency ContainerType="IASFarm" Name="Farm_1"/>
      <OIDDependency ContainerType="IASInstance" Name="infra.host2.xyz.com"/>
      <EMDependency ContainerType="IASInstance" Name="ias.host1.xyz.com"/>
   </PortalInstance>

</IASConfig>

The OracleAS Portal instance now references the virtual OracleAS Web Cache front-ending it.