Skip Headers

Oracle9i Application Server Certified Configuration Deployment and Cloning Guide
Release 2.0.6 for Linux x86
Part No. B10953-02
  Go To Table Of Contents
Contents		 Go To Index
Index
Previous Next  

4 Configuring Portal Against the Customer Database

This chapter provides instructions on how to configure an Oracle9i Application Server Certified Configuration (Oracle9iAS CC) Portal Middle-Tier with an existing Oracle9i release 2 (9.2.0.x) database.

This chapter contains the following sections:

In this chapter, the database in which the Oracle9iAS Portal repository is created is referred to as the target or customer database, and Oracle net service name is used interchangeably with TNS alias.

Configuring the Portal Database Tier

Complete the following tasks on the customer database for Oracle9iAS Portal. This release is certified against Oracle9i Release 2 (9.2.0.2).

Configuring Oracle9i release 2 (9.2.0.x) Database

If you use an Oracle9i release 2 (9.2.0.x) database for the portal metadata repository database, then complete the following procedure:

  1. Log in as the user who owns the Oracle9i Release 2 database.

  2. Shutdown the database.

  3. Download from Oracle iSupport ARU patch 2392197 (for bug number 2646865), and unarchive the patch files. Ensure that all appropriate environmental variables point to the Oracle9i release 2 (9.2.0.x) ORACLE_HOME, and then follow the instructions in the patch README.txt file to install the patch.


    Note:

    This is only required for Oracle9i release 2 (9.2.0.2) database.


    Note:

    You might encounter the bug 2947799 while applying the database patch. Follow the workaround mentioned in the bug to apply the database patch.

  4. Restart the database.

  5. Restart the Oracle Net Listener in the Oracle9i release 2 CC ORACLE_HOME environment.

  6. Using the following procedure, install PL/SQL LDAP APIs packages (DBMS-LDAP_UTIL) in the target database:

    1. Using the following command, change directory to $ORACLE_HOME/rdbms/admin: 

      $ cd $ORACLE_HOME/rdbms/admin/

    2. As shown in the following example, log in to the target database as the SYS administrative user, and run the SQL file catldap.sql: 

      $ sqlplus ’sys/sys_password as sysdba’

SQL> @catldap.sql

      where the variable sys_password is the SYS password for the target database.

  7. Complete the procedure under "Completing Portal Repository Database Configuration" to finish configuring the repository.

Completing Portal Repository Database Configuration

Complete the following procedure:

  1. Create a TNS alias to connect to the Oracle9iAS metadata repository database from the target database. Do this by adding the appropriate entry to the target database tnsnames.ora file, which is located in the target database ORACLE_HOME. The following is an example: 

    CUSTDB_TO_INFRADB.us.oracle.com =

  (DESCRIPTION =

    (ADDRESS_LIST =

      (ADDRESS = (PROTOCOL = TCP)(HOST = host1.us.oracle.com )(PORT = 1521))

    )

    (CONNECT_DATA =

      (INSTANCE_NAME = SID1)

      (SERVICE_NAME = SID1)

    )

  )

    where:

    • CUSTDB_TO_INFRADB.us.oracle.com is the TNS_to_alias name. You should create this using the format, <custdbsid>_to_<infradbsid>.

    • host1.us.oracle.com is the computer where the Oracle9iAS metadata repository database is running.

    • 1521 is the Oracle Net listener port number to connect to the Oracle9iAS metadata repository database.

    • SID1 is the Oracle9iAS metadata repository database SID.

Configuring the Portal Middle-Tier

Use the following procedure to configure the Portal Middle-Tier:

  1. Log in as the user who owns the ORACLE_HOME for Oracle9iAS Middle-Tier.

  2. Using the following command, run $HOME/profile.iascc_env: 

    $ . $HOME/profile.iascc_env

    When prompted, enter the option number to select the ORACLE_HOME for the Middle-Tier. This script also sets the variable $ORACLE_CC_ROOT which will be used in subsequent steps.

  3. Create a TNS alias to connect to the target database from the Oracle9iAS Middle-Tier ORACLE_HOME. The following is an example: 

    TORCLO.us.oracle.com =

  (DESCRIPTION =

    (ADDRESS_LIST =

      (ADDRESS = (PROTOCOL = TCP)(HOST =host1.us.oracle.com )(PORT = 1521))

    )

    (CONNECT_DATA =
      (INSTANCE_NAME = TDRCLO)
      (SERVICE_NAME = TDRCLO)

    )

  )

    where:

    • TORCLO.us.oracle.com is the TNS alias name. Follow the standards for creating a service name.

    • host1.us.oracle.com is the machine where the target database is running.

    • 1521 is the Oracle Net listener port number to connect to the target database.

    • SID1 is the target database SID.

  4. Configure the Oracle9iAS Portal parameter file.

    The remaining portal configuration steps use the Oracle9iAS Portal parameter file, $ORACLE_CC_ROOT/portal/portal_dbfiles.conf. You do not have to modify this file unless you want to customize it for your environment. The Oracle9iAS Portal parameter file contains tablespace names, corresponding data file locations, and the size required for creating the Oracle9iAS Portal repository database. The portal parameter file is in the following format:

    Key Name= Tablespace name:Full path of data file:Size (in MB)

    The Full Path of data file contains the prefix %DATADIR%. This string will be replaced with /<SID>/oradata when the subsequent scripts are run. You do not have to manually change it. The <SID> will be the db_name of the database in which the portal repository database will be created. Please ensure the path /<SID>/oradata/data01 and /<SID>/oradata/data02 exist in the system where the portal repository will be created.

    If you choose to customize the values for Tablespace name and Size, then edit these fields in portal_dbfiles.conf file. The size specified in the configuration file is the minimum size required for Oracle9iAS Portal. Do not lower the value. If you do lower the size, then the portal repository creation can fail.

    The following is a sample portal_dbfiles.conf file: 

    #Configuration file for portal to configure against any database#

#

# Format:

# KEY=<value1>:<value2>:<value3>

# Warning : Do not change the KEY#
#    %DATADIR% will be instantiated with /sid/oradata runtime. User does
#    not need to alter this variable
#

# Portal Default tablespace where the portal objects are loaded
PORTAL_DEF_TS=PORTALDATA:%DATADIR%/dat01/portaldata01.dbf:150

#Portal index tablespace
PORTAL_IDX_TS=PORTALIDX:%DATADIR%/data01/portalidx01.dbf:25

#Portal temporary tablespace
PORTAL_TMP_TS=PORTALTMP:%DATADIR%/data02/portaltmp01.dbf:25
 
#Portal Document tablespace
PORTAL_DOC_TS=PORTALDOC:%DATADIR%/data01/portaldoc01.dbf:10
 
#Portal Logging tablespace
PORTAL_LOG_TS=PORTALLOG:%DATADIR%/data01/portallog01.dbf:10

    In the preceding example, the Portal default tablespace parameters are defined in the following line: 

    PORTAL_DEF_TS=PORTALDATA:%DATADIR%/data01/portaldata01.dbf:150

    where:

    • The key variable PORTAL_DEF_TS is the key that identifies the default tablespace.

    • The default tablespace name for loading portal objects is portaldef. The %DATADIR% will be instantiated when the subsequent steps run.

    • The data file name for the default tablespace is portaldata01.dbf.

    • The initial size of the tablespace is 150 MB.

    If you want to change the default tablespace parameters, then use the following as a model: 

    PORTAL_DEF_TS=portal_newdef:/%DATADR%/data01/portal_newdef.dbf:200

    where:

    • The default tablespace name for loading portal objects is portal_newdef.

    • The data file name for the default tablespace is /%DATADIR%/portal_newdef.dbf.

    • The initial size of the tablespace is 200 MB.


    Note:

    Do not change key variable names such as PORTAL_TMP_TS, PORTAL_DEF_TS, and so forth in the file portal_dbfiles.conf.

  5. If the target database where the Portal repository is to be created is an Oracle9i release 2 (9.2.0.2) database, then you must complete the following Portal preconfiguration step.

    If you are using a Oracle9i release 1 (9.0.1.3) database, then you do not need to preconfigure the portal; go to the next step.

    To preconfigure the Portal:

    1. Using the following command, change to the directory $ORACLE_CC_ROOT/portal: 

      $ cd $ORACLE_CC_ROOT/portal

    2. Log in as user who owns the account for the Oracle9iAS server and run the script portal_preconfig.sh: 

      $ ./portal_preconfig.sh

    3. The prompt Enter the sys user password for target database: appears.

      Enter the SYS administrative user password to connect to the target database where the Portal repository is to be loaded.

    4. The prompt Enter the service name for the target database: appears.

      Enter the service name (TNS alias) that you created in step 1 in the preceding section "Completing Portal Repository Database Configuration".

    5. The script creates a log file, which is available in $ORACLE_CC_ROOT/logs/config/portal_preconfig.<PID>.log Review the log file. If you see any errors, then correct the errors and run the script again.

  6. Using the following procedure, verify and/or create the tablespaces required to create the Portal repository in the target database. This step uses the configuration file $ORACLE_CC_ROOT/portal/portal_dbfiles.conf.

    1. Using the following command, change directory to $ORACLE_CC_ROOT/portal: 

      $ cd $ORACLE_CC_ROOT/portal

    2. As the oracle user (or the user who owns the Oracle9iAS server), run the script portal_dbprepare.sh: 

      $ ./portal_dbprepare.sh

    3. The prompt Enter the SYS user password for the target database: appears.

      Enter the SYS administrative user password to connect to the target database where the Portal repository is to be loaded.

    4. The prompt Enter the service name for the target database: appears.

      Enter the net service name (TNS alias) that you created in step 1 to connect to the target database.

      The script verifies and creates tablespaces in the target database specified in the configuration file that are required objects for the Portal.

    5. The script creates a log file, which is available at $ORACLE_CC_ROOT/logs/config/portal_dbprepare.<PID>.log.

      Review the log file. If you see any errors, then correct the errors and run the script again.

  7. Create the Portal repository in the target database. It takes between one and two hours to create the Portal Repository

    Use the following procedure to create the repository:

    1. As the oracle user (or the user who owns the Oracle9iAS server), run the script portal_repo_create.sh: 

      $ ./portal_repo_create.sh

    2. The prompt Enter the Portal schema name [cust_portal]: appears.

      Enter the Portal schema name in the target database in which the Portal objects will be loaded.


      Note:

      The default schema name for customer portal will be cust_portal. This name follows Oracle Outsourcing standards. You could override it with any name other than portal.

      Do not use "Portal" for the schema name at this step.



      Note:

      The password for the portal schema will be the same as the schema name.

    3. The prompt Enter the connect string for the target database (host:port:sid) for Portal appears.

      Enter the connect string to connect to the target database in the format hostname:port:SID. The SID is the system identifier for the system

    4. The prompt Enter the SYS user password for the target database appears.

      Enter the password for the SYS administrative user on the target database.

      The script creates Portal objects in the target database.

    5. The script creates a log file, which is available in $ORACLE_HOME/assistants/opca/schema_name.log. The variable schema_name is the name of the Portal schema that is supplied to the script. Using the following command, verify that there are no errors in the log file: 

      $ egrep -n ’^ERROR|ERROR:|ORA-|PLS-|SP2-|IMP-’ $ORACLE_HOME/assistants/opca/schema_name.log

      where the variable schema_name is the name of the Portal schema that is supplied to the script.


      Note:

      If you run the script portal_repo_create.sh again, or if you perform step 10, then the log file $ORACLE_HOME/assistants/opca/schema_name.log is overwritten. Save the log file under a new name if you need to run the script again.

  8. Create the Database Area Descriptor (DAD). To do this, start up Oracle Enterprise Manager on the system where you are configuring the Portal.


    Note:

    For more information on Oracle Enterprise Manager, refer to "Using Enterprise Manager Web Site" in Chapter A, " Administering Oracle9i Application Server CC".

    Using the following procedure, create the Database Area Descriptor (DAD) to point to the newly-created Portal repository:

    1. Open an HTML browser, and enter the following Web site address: 

      http://hostname.domainname:1810

      where the variable hostname.domainname is the server where the Portal Middle-Tier is configured. Port 1810 is the default port for Enterprise Manager; if you change the default port, then enter the appropriate port number.

    2. Enter the Enterprise Manager login and password.

    3. In Standalone Instances Section, click the portal Middle-Tier instance link that connects to the Middle-Tier instance.

    4. In System Components Section, click the HTTP Server link.

    5. In Administration Section, click the PL/SQL Properties link.

    6. In the DAD Status section, click the Create button.

    7. In the Create Dad:DAD Type page, select the Portal radio button, and click the Next button.

    8. In the Create DAD: Database Connection page, fill in the following fields:

      - DAD Name: The DAD name should be cust_portal according to Oracle Outsourcing standards.

      - Database User Name: Enter the Portal schema name that you used in Step 7.

      - Database Password: Enter the Portal schema name that you used in Step 7.

      - Database Connection String: Enter the Portal database connection string in the format host:port:SID to connect to the target database.

    9. Click Next, and click OK.

    You should see the DAD you created in the DAD status page.

    The portal DAD that is created should have the NLS language settings in the $ORACLE_HOME/Apache/modplsql/conf/dads.conf file. However, while creating the DAD through Oracle Enterprise Manager, the NLS language is not set. Edit the $ORACLE_HOME/Apache/modplsql/conf/dads.conf and add the following line in the new DAD section that you created using Oracle Enterprise Manager.

    Add the line, PlsqlNLSLanguage <database character set>, before the following line: 

    PlsqlDocumentProcedure cust_portal.wwdoc_process.process_download

    Replace the <database character set> variable with the actual database character set for the customer database. For example, for the database with character set UTF8, you will enter the following line: 

    PlsqlNLSLanguage AMERICAN_AMERICA.UTF8

  9. After successfully creating a DAD, use Enterprise Manager to restart the Oracle HTTP Server:

    1. Open an HTML browser, and enter the following URL address: 

      http://hostname.domainname:1810

      where the variable hostname.domainname is the server where you configured the Portal Middle-Tier. Port 1810 is the default port for Enterprise Manager. If you change the default port, then enter the appropriate port number.

    2. Enter the Enterprise Manager login and password.

    3. In Standalone Instances Section, click the portal Middle-Tier instance link that connects to the Middle-Tier instance.

    4. In System Components Section, click the HTTP Server link.

    5. In General Section, click the Restart button. Click Yes in the warning page

    6. In the next page, click OK

      Verify that the DAD is functioning properly.

    7. The prompt, Enter the Service name (tns alias) connecting customer database to iAS infrastructure database:, appears.

      Enter the tns service name defined in the customer database to connect to infrastructure database on the dbtier system.

    8. In Administration Section on the HTTP Server page, click the PL/SQL properties link.

    9. In the DAD Status section, review the status of the DAD you created.

      If the DAD is successfully created, then the Status indicator icon is a green check mark.

      If the DAD is not successfully created, then the Status indicator is a red X.

      If the Status indicator is a red X, then verify that the target Portal database is running, and that you can connect to it using the connect string you specified in Step 8.

      When the Status icon is a green check mark, which indicates that the DAD is successfully created, then continue to the next step.

  10. Using the following procedure, link (or "wire") the Middle-Tier with the target Portal repository database:

    1. Using the following command, change directory to $ORACLE_CC_ROOT/portal: 

      $ cd $ORACLE_CC_ROOT/portal

    2. Log on as the oracle user (or the user who owns the Oracle9iAS server), and use the following command to run the script wire_portalmt_portalrepo.sh: 

      $ ./wire_portalmt_portalrepo.sh

    3. The prompt Enter the Portal schema name [cust_portal]: appears.

      Enter the schema name that you created in Step 7.

    4. The prompt, Enter the connect string for the Portal database (host:port:sid), appears.

      Enter the connect string to connect to the target Portal database, where the Portal objects are loaded, in the format host:port:SID.

    5. The prompt, Enter the Portal DAD name:, appears.

      Enter the portal DAD name that you created in step 8.

    6. The prompt, Enter the database link name for connecting Portal schema to sso password store:, appears.

      Enter the database name of the metadata repository database.

      The script creates a link in the portal database to connect to the metadata repository database, where the Oracle9iAS Single Sign-On password store is located. The metadata database is part of the Oracle9iAS Infrastructure deployment on the Database Tier System.

    7. The prompt, Enter the service name (the alias) connecting target database to infrastructure database:, appears.

      Enter the alias created in target portal DB ORACLE_HOME to connect to the infrastructure database.

    8. The prompt, Specify the OID administrator password:, appears.

      Enter the password for the metadata repository database on the Oracle9iAS Database Tier Infrastructure deployment.

    9. The prompt, Specify the Web Cache invalidator password (default:invalidator):, appears. Enter the Web Cache Invalidator password. The default password is "invalidator."

    10. The prompt, Enter the Portal user password to log in to Portal:, appears. Enter a password. Remember this password, as you will need it to log in to Portal. The password must be at least five characters long, and should contain at least one numeric character. Example: iasp1

    11. The prompt, Re-enter the Portal user password:, appears.

      The script verifies the supplied input values, and starts connecting the Middle-Tier deployment with the target Portal repository database.

    12. The script creates a log file, which is available in $ORACLE_HOME/assistants/opca/schema_name.log. The variable schema_name is the name of the Portal schema that is supplied to the script. Using the following command, verify that there are no errors in the log file: 

      $ egrep -n ’^ERROR|ERROR:|ORA-|PLS-|SP2-|IMP-’ $ORACLE_HOME/assistants/opca/schema_name.log

      where the variable schema_name is the name of the Portal schema that is supplied to the script.


      Note:

      If you run the script wire_portalmt_portalrepo.sh again, then you will overwrite the log file, $ORACLE_HOME/assistants/opca/schema_name. Save the log file under a new name if you need to run the script again.

Upgrading the Oracle9iAS Portal Repository in the Customer Database to 9.0.2.3

You must perform steps in this section to upgrade Oracle9iAS Portal schemas in the customer database to a 9.0.2.3 version. If you installed the Oracle9i Application Server release 9.0.2 using the certified configuration gold image, the 9.0.2.3 patch set is already integrated. However, during the installation only the Portal schemas in the Infrastructure database are upgraded. Therefore, every time you create a new Portal repository in an existing database, you must complete the steps in this section.

The Oracle9i Application Server mid-tier Oracle home should be upgraded to portal 9023 patch set level. If you did not upgrade it, upgrade to 9023 patch set level first.

Perform the following steps from the Oracle9i Application Server mid-tier Oracle home:

  1. Login as the user that owns the Oracle9i Application Server mid-tier Oracle home.

  2. Using the following command, set the environment to Oracle9i Application Server mid-tier Oracle home. 

    $ . $HOME/profile.iascc_env

  3. Change directory to $ORACLE_HOME/portal/patch-9-0-2-3-0/p90230 and run the patch.csh script, using the following commands: 

    $ cd $ORACLE_HOME/portal/patch-9-0-2-3-0/p90230 
$ ./patch.csh  -s <portal_schema> -p <portal_schema_password> -c \ <net service name> [<-l log_file_name>]

    In the example above you should enter the:

    • Customer portal schema name for <portal_schema>. The default is cust_portal.

    • Customer portal schema password for <portal_schema_password>. The default is cust_portal.

    • Net service name to connect to the customer database for <net service name>.

      Log file name for <log_file_name>. This is optional, if you do not supply defaults to the portal.log log file.

  4. Check the log file for any errors.

Accessing Portal After Configuration

After you successfully configured the Portal, use the following procedure to access Oracle Portal:


Note:

Ensure that other ORACLE_HOME processes are running prior to beginning this procedure.

  1. Enter the following URL address in a Web Browser: 

    http://hostname.domainname:port/pls/<Portal DAD

    where:

    • hostname.domainname is the computer name where the Middle-Tier Portal host is installed.

    • port is the HTTP Server port number for the Middle-Tier. You can obtain the port number by looking for the following string in the file, $ORACLE_HOME/install/portlist.ini on the $ORACLE_HOME, where the Portal Middle-Tier is installed: 

      Oracle HTTP Server port

    • <Portal DAD> is the DAD that you created in Step 8 of (UNKNOWN STEP NUMBER) "Configuring the Portal Middle-Tier".

  2. The Portal home page opens. Click the Login link.

  3. Enter the portal schema name that you created in Step 7 of "Configuring the Portal Middle-Tier". Provide the portal user password that you created in Step 10 of "Configuring the Portal Middle-Tier".

Preventing Default Portal Access

Oracle Corporation recommends that you remove the default Oracle Portal configured against the Infrastructure metadata database if you do not plan to use it.

To remove the default Portal installation:

  1. Follow the procedure outlined in step 8, "Create the Database Area Descriptor (DAD)", in the section "Configuring the Portal Middle-Tier".

  2. In the DAD status section, click the Portal radio button, and click Delete.

Changing the Portal Schema Password

This section describes how to change the Portal schema password after setting up a Portal repository in a separate database. Changing the Portal schema password does not affect access to the Portal pages.

By default, when you create a new Portal schema in the database, the password is the schema name. For security reasons, Oracle Corporation recommends that you change the password after you create and configure the Portal schema.

To change the Portal schema password, you must both change the Portal schema in the database, and reset the password for the Portal DAD.

Use the following procedure to change the Portal schema password:

  1. In the Portal database-tier computer, set Oracle initialization parameters ORACLE_HOME and ORACLE_SID to point to the Portal database.

  2. Using the following command, log in as the administrator SYS to the Portal database: 

    $ sqlplus sys/sys_password as sysdba

    where the variable sys_password is the password for the SYS user.

  3. Using the following SQL command, change the Portal schema password: 

    SQL> alter user schema_name identified by new_password;

    where the variable schema_name is the Portal schema name that you created in Step 7 of "Configuring the Portal Middle-Tier", and the variable new_password is the new password you want to assign to the Portal schema. You should see the response "User Altered" after running the SQL command.

  4. Change the password for the Portal DAD, which you created in Step 8 of "Configuring the Portal Middle-Tier". Ensure that Enterprise Manager is up and running on the Middle-Tier system from where the Portal is configured, and use the following procedure to change the password:

    1. Open an HTML browser, and enter the following URL address: 

      http://hostname.domainname:1810

      where the variable hostname.domainname is the server where the Portal Middle-Tier is configured. Port 1810 is the default port for Enterprise Manager. If you change the default port, then enter the appropriate port number.

    2. Enter the Enterprise Manager login and password.

    3. In Standalone Instances Section, click the portal Middle-Tier instance link that connects to the Middle-Tier instance.

    4. In System Components Section, click the HTTP Server link.

    5. In Administration Section, click the PL/SQL Properties link.

    6. In the DAD Status section, click the portal DAD link for the DAD for which the password is to be changed.

    7. In the field Database Password, enter the new password that you provided for the Portal schema in Step 3. Click the Finish button.

    8. The Confirmation page opens. Click OK.

  5. After you change the DAD password, you need to restart Oracle HTTP Server. Use the following procedure:

    1. Open an HTML browser, and enter the following URL: 

      http://hostname.domainname:1810

      The variable hostname.servername is the server where you configured the Portal Middle-Tier. Port 1810 is the default port for Enterprise Manager; if you change the default port, then enter the appropriate port number.

    2. Enter the Enterprise Manager login and password.

    3. In Standalone Instances Section, click the portal Middle-Tier instance link that connects to the Middle-Tier instance.

    4. In System Components Section, click the HTTP Server link.

    5. In General Section, click the Restart button.

    6. The Warning page appears. Click Yes

    7. The Next page appears. Click OK

      Verify that the DAD is functioning properly.

    8. In Administration Section on the HTTP Server page, click the PL/SQL Properties link.

    9. In the DAD Status section, review the status of the DAD whose password you changed. The Status icon should be a green check mark, indicating that the DAD connection is successful.

      If the status icon is a red X, then verify that the target Portal database is running. Verify that the target Portal database is able to connect using the specified connect string.

      Verify that you are able to access Portal. Use the procedure described in the preceding section "Accessing Portal After Configuration".


      Note:

      The Portal schema password change does not affect the login and password used to access the Portal. They continue to remain the same.

Setting Up Oracle Ultra Search Against the Customer Database (Release 9.2.0.x)

Follow the instructions in Install Ultra Search 9.0.2 document at the following link to configure Ultra Search in the customer database:

http://files.oraclecorp.com/content/AllPublic/Workspaces/Ultra%20Search-Public/Installation%20Info/Install%20Ultra%20Search%20on%20Database%209.2%20%26%20iAS%209.0.2.htm

  Previous Next
Oracle Logo
Copyright © 1999, 2003 Oracle Corporation
All rights reserved
  Go To Table Of Contents
Contents		 Go To Index
Index