Oracle® Access Manager for AS/400 Installation and User's Guide 10g Release 2 (10.2) for IBM iSeries OS/400 Part Number B16223-01 |
|
|
View PDF |
The installation of the Oracle Access Manager for AS/400 is divided into two parts, installation and postinstallation. Before you begin installation, ensure that you have the required hardware and software that are described in Chapter 3, "System Requirements".
This chapter contains the following topics:
Use these checklists when installing the Oracle Access Manager for AS/400.
Before installing Oracle Access Manager for AS/400, you must log on with a user profile that has the *SECADM
and *ALLOBJ
special authorities. The user profile QSECOFR
usually has that authority.
Caution:
Oracle recommends that you back up any existing Access Manager library before upgrading to a new release.The panels are shown as they appear when first displayed. The values that are documented in this installation guide are the default values that are provided by Oracle Corporation at the time that you install the Oracle Access Manager for AS/400. The default values are used unless they are manually changed before continuing.
LODRUN CD_drive
where CD_drive
is the name of the CD drive where you mounted the product CD-ROM. The default is usually OPT01
.
When the Install Access Manager Product Panel is displayed, use the default name of ORAAM400
or enter a name with a length from 1 to 10 characters long.
Example 4-1 Install Access Manager Product Panel
_______________________________________________________________________________________ Install Oracle Access Manager product 10.2.0.1.0 Type Choices, press Enter. System: HQAS400 Install library name ......... ORAAM400 Name (up to 10 characters) Auxiliary storage pool id .... 1 1-16 ===> Bottom F1=Help F4=Prompt F9=Retrieve F12=Cancel (C) Copyright Oracle Corporation, 2006 _______________________________________________________________________________________
The specified library name must denote an existing (but empty) library, or must denote a nonexistent library. The installation procedure will not install into a library with existing objects. The specified library name is also used to create an AS/400 User Profile. The password for that profile is also identical to the User Profile name. The password should be changed after installation using the CHGUSRPRF
command.
For auxiliary storage pool ID, use the default of 1, or enter another ID.
After entering your information on the panel, press Enter to continue.
The following panel appears:
Example 4-2 Verify Access Manager Install Panel
_______________________________________________________________________________________ Verify Oracle Access Manager Install at V10.2.0.1.0 System: HQAS400 Verify that you want to install the product. Once this process has started, it will create a library and other objects. Enter *YES to verify this operation before it is started. New Install Library name ........ ORAAM400 Enter *YES to verify ............ *NO *NO, *YES ===> Bottom F1=Help F4=Prompt F9=Retrieve F12=Cancel (C) Copyright Oracle Corporation, 2006 _______________________________________________________________________________________
Enter *YES
to continue the installation process. Press Enter to continue.
If you entered *YES
, then status messages will be displayed on the bottom of the screen as the installation proceeds. After a few minutes, a screen will appear, stating:
Install complete. Press ENTER. Check Job log for any errors.
When the installation is finished, use the following command to check the job log for error messages:
DSPJOBLOG
Installation of Oracle Access Manager for AS/400 is complete.
Note:
During the installation, an AS/400 User Profile was created with the same name and password as the library in which the Access Manager was installed. You need to use theCHGUSRPRF
command to change the password for that User Profile.You need to change the password by using the following command syntax:
CHGUSRPRF USRPRF(install_lib) PASSWORD(new_password)
where:
install_lib
is the installation library. The default is ORAAM400
.
new_password
is the new userid password that you want to use.
This section describes the steps to be performed after the initial installation of Oracle Access Manager for AS/400.
Before attempting to use any of the Access Manager configuration utilities, you must add the Access Manager library to your library list. To do this, enter the following command on any command line:
ADDLIBLE library_name
where library_name
is the name of your Access Manager installation library.
The default position is *FIRST.
You do not need to manipulate the library list when running the Access Manager itself. Access Manager will determine which libraries need to be added to the library list, and it will add those libraries to the top of the user portion of the library list.
Use the CHGUSRPRF
command to change the password for the user profile that was created during the install. The name for that user profile is identical to the name of the library in which the Access Manager objects were installed. So, if you used the default instance name of ORAAM400
, then Access Manager objects were placed into library ORAAM400
, a user profile with a name of ORAAM400
was created with password ORAAM400
.
Configure Oracle Net on the Oracle integrating server. Refer to Chapter 5, "Oracle Net" for more information.
Refer to "Connecting through the STRSQL (Interactive SQL) Commands" in Chapter 8, "Using Access Manager" for information about connecting to an Oracle server.
Configure Oracle Access Manager for AS/400. All options have defaults that are used unless you change them. Refer to Chapter 6, "Configuring Access Manager" for more information.
Note:
Steps 6 and 7 need to be performed only if you will be using two-phase commit.If you want to use two-phase commit processing, then you need to configure it now. Refer to Chapter 7, "Distributed Transaction Coordination" for the steps to use in configuring two-phase commit processing.
At this point, you can retest your connectivity to the Oracle server by using two-phase commit processing. Refer to "Connecting through the STRSQL (Interactive SQL) Commands" for information about connecting to an Oracle server.