Oracle Universal Installer should launch with the Welcome screen. Click Next.

Enter portal as the name and E:\portal as the path on the Specify File Locations screen, and then click Next.

Select Oracle Application Server 10g on the Select a Product to Install screen and then click Next.

.

Select Portal and Wireless on the Select Installation Type screen and click Next.

You must have administrator privileges on the host for the installation to be successful. Select the Administrator privileges check box and click Next.

Select Oracle Application Server 10g Portal on the Select Configuration Options screen.

Specify ten.mydomain.com as the Host value (or the host name in your environment where OID has been preinstalled) and 13060 as the Port value (or the port for OID in your environment) for the OID instance which has been preinstalled on the Register with Oracle Internet Directory screen. Leave Use only SSL connections with this Oracle Internet Directory check box deselected.

Specify cn=orcladmin and abcd1234 as the username and password, respectively, on the Specify OID Login screen, and then click Next.

On the Select Oracle Application Server 10g Metadata Repository screen, Database Connect String should be prepopulated with the hostname:port:Global Database name: Service name for the metadata repository. In this case, it is ten.mydomain.com:1521:infra.mydomain.com:infra.mydomain.com. Click Next.

Specify portal as the Instance Name with abcd1234 as the ias_admin password (confirm the same password) on the Specify Instance Name and ias_admin Password screen, and then click Next.

Click Install on the Summary screen.

After the installation is completed, the End of Installation screen is displayed. Review the information and click Exit.

To verify that the installation of Oracle Portal was successful, open Internet Explorer and enter the following URL: http://ten.mydomain.com:7778/pls/portal

Click the Login link and specify orcladmin as the username and abcd1234 as the password. Click OK. You should be logged in as orcladmin.

You need to have the administrative privileges to run the installation. If you are logged in as a different user, you need to exit the installation, log in as the Administrator, and then restart the installation. Then click Next.

In the Destination Name text box, set the installation directory to E:\identity and click Next.

Review the location to which Oracle Access Manager Identity Server is getting installed and the total disk size it would take for the installation. Then click Next.

Notice that the installer begins copying the Oracle Access Manager Identity Server files. Next select the Open Mode: No Encryption option for the Identity client and Identity Server to communicate. Click Next.

You need to provide the Identity Server ID, host name, and port number for the Identity Server connection. For this installation, you can provide the following values and then click Next.

Note: You can use your own values for all these parameters on the basis of any changes made to the environment setup.

If you are installing the first Identity Server instance on the host, keep the default selected option Yes and click Next.

The OID will be used as user repository. This is used to host the user data for the Identity Server. In this case, you select Oracle Internet Directory from the Directory Server Type drop-down menu and click Next.

The directory server hosting user data and Oracle data could be in same or different directories. In this case, the same OID instance will host both user and Oracle (Oblix) data. Select Oracle data will be in the user data directory and click Next.

The directory server schema needs to be extended to store the Oracle Access Manager schema. To configure the user repository with the OAM Access Manager schema, retain the Yes option and click Next.

Provide the following information for the Oracle Internet Directory that hosts user data and click Next.

Enter identity as the Windows Service Name and click Next.

You can view the Readme page and then click Next.

You can review the server settings and click Finish.

Start the Oracle Access Manager Identity Server (identity) service.

Note: In this environment, you start it from a batch file that runs a NET START command to start the identity service. You can also start it by navigating to Start > Control Panel > Administrative Tools > Services, right-clicking the Oracle Access Manager Identity Server (identity) service, and selecting Start.

You can verify the schema for Oracle data (Oblix) in the OID by navigating to Oracle Directory Manager > Oracle Internet Directory Servers > orcladmin@ten.mydomain.com:13060 > Schema Management. You will find the Oracle (Oblix)-specific objectclasses (on the Object Classes tabbed page) and attributes (on the Attributes tabbed page) created when the OID schema was extended by the Identity Server installer.

To install Oracle Access Manager WebPass, you need to have administrative privileges. If you are logged in as a different user, you need to exit the installation, log in as the Administrator, and then restart the installation. Then click Next.

In the Destination Name text box, set the installation directory to E:\webpass and click Next.

Review the location to which Oracle Access Manager WebPass is getting installed and the total disk size it would take for the installation. Then click Next.

.

Notice that the installer begins copying the Oracle Access Manager WebPass files. Select the Open Mode: No Encryption option for the WebPass and Identity Server to communicate and click Next.

You need to provide the WebPass ID, host name, and port number for the Identity Server connection. For this installation, you can provide the following values and then click Next.

Note: You can use your own values for all these parameters on the basis of any changes made to the environment setup.

The Web server needs to be configured by modifying the configuration of the Web server directory. This change is reflected in the httpd.conf file for the OHS instance that is part of the infrastructure installation. To automatically update this configuration, retain the automatic update selection and click Next.

Notice that the Web server configuration has been modified for the OHS. You need to restart the Identity Server and the Web server for the changes to take effect. To restart the Identity Server, select Start > Control Panel > Administrative Tools and double-click Services. Right-click the Oracle Access Manager Identity Server (identity) service and select Restart.

Note: Do not click Next before you start the Identity Server and restart the Web server.

To restart the Web server, execute the following commands in sequence from <OHS_home>\opmn\bin:

E:\infra\opmn\bin>opmnctl stopproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl startproc process-type=HTTP_Server

You can view the Readme page and then click Next.

Review the WebPass configuration settings and click Finish.

To verify the WebPass installation, access the Identity Administration page using the following URL:

http://<hostname>.<domainname>/identity/oblix

Note: For this environment, use the URL http://ten.mydomain.com:7777/identity/oblix where 7777 is the port on which the OHS will route the access to the Identity Server.

Notice that the System Console Application is not set up. Then click Setup to perform the configuration.

For the Directory Server type for User data, select Oracle Internet Directory and then click Next.

You can view the note for the schema changes where the installer needs to update the Oracle Access Manager Identity schema into the directory. Scroll down and click Next.

You need to specify the location of the LDAP Server that will store user data. For this, provide the following parameters for the OID Server and then click Next.

The configuration DN is the directory tree where Oracle Access Manager stores the configuration data. Oracle Access Manager Identity System and Oracle Access Manager System need to use the same configuration data. The searchbase is the node in the directory tree where user data is stored. In this case, the searchbase will point to the parent of the cn=Users container and the ou=vendors container configured in OID. The configuration DN will point to the location where the o=oblix container will be created in OID. To set the searchbases and the configuration DN, provide the following values and click Next:

The Person Object Class defines the primary objectclass for people in the user directory. This will vary by the specific type of directory used for user information or if directory schema extensions are made to define a new type of ‘person’ object. Provide the value for the Person Object Class as inetOrgPerson and click Next.

Note: By default, retain the Auto configure objectclass check box selected.

The Group Object Class defines the primary objectclass for groups in the user directory. This will vary by the specific type of directory used for user information or if directory schema extensions are made to define a new type of default "group" object. Provide the values for the Group Object Class as groupOfUniqueNames and click Next.

Note: By default, retain the Auto configure objectclass check box selected.

The basic connection information for the directories is completed. You need to restart both the Identity Server and the OHS Web Server for these changes to take effect and then perform the basic configuration schema mappings. After you perform the restart (from the next four steps), click Next.

Note: You need to click Next only after you perform step 10 through 13.

To stop the Identity Server, select Start > Control Panel > Administrative Tools and double-click Services. Right-click the Oracle Access Manager Identity Server (identity) service and select Stop.

To stop and start the OHS, browse to <Infra_home>\opmn\bin and execute the following commands:

E:\infra\opmn\bin>opmnctl stopproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl startproc process-type=HTTP_Server

To start the Identity Server, select Start > Control Panel > Administrative Tools and double-click Services. Right-click the Oracle Access Manager Identity Server (identity) service and select Start.

You can verify the configuration values set for the inetOrgPerson objectclass. After you review the complete schema mapping for this objectclass, click Yes.

You can verify the configuration values set for the groupOfUniqueNames group objectclass. After you review the complete schema mapping for this groupclass, click Yes.

Oracle Access Manager administrators have access to system configuration and system management functions. In this setup, one or more Oracle Access Manager Master Administrators need to be assigned. These users can configure the rest of the Oracle Access Manager installations. To identify these users, click Select User.

Search for Rohit Younger as Full Name and click Go.

You can view the user Rohit Younger. Click Add to select him as the master administrator.

Click Done to return to the Configure Administrators section. You can view that Rohit Younger is now listed as Master Administrators. Click Next.

The default directories of the Oracle Access Manager Identity Server installation should be secured. Next click Done.

Open the browser and enter the URL in the following format to access the Identity System Console. Then click Identity System Console.

http://<hostname>.<domainname>/identity/oblix

You can authenticate as a Master Administrator you selected earlier. Enter rohit.younger as the username and abcd1234 as the password. Click Login.

You need to have the administrative privileges to run the installation. If you are logged in as a different user, you need to exit the installation, log in as the Administrator and then restart the installation. Then click Next.

In the Destination Name text box, set the installation directory to E:\webpass and click Next.

Note: The destination directory for WebPass installation further creates subdirectories for WebPass as E:\webpass\identity and for policy manager as E:\webpass\access.

Review the location to which Oracle Access Manager Policy Manager is getting installed and the total disk size it would take for the installation. Then click Next.

The Policy Manager needs to connect to an LDAP server to store the policy data. Select Oracle Internet Directory from the drop-down menu and click Next.

Note: The policy data (similar to configuration data) is being accessed from OID (under o=oblix container).

Notice that the installer prompts you to extend the LDAP schema with the Oracle schema. You have already extended the schema during the installation for Identity Server. Select the No option button and click Next.

Note: Because you are storing both the configuration and policy data in the same instance of OID and you have already extended the schema for that instance of OID during the configuration data set up earlier, you choose not to extend the schema again. However, if you choose to store the policy data in a different instance of OID or in another LDAP directory, you would need to extend the schema for that directory server instance in this step.

In this setup, you do not use SSL for any of the directory services. Leave the check box options deselected and click Next.

Select the Open Mode: No Encryption option for the Policy Manager and Access Server to communicate and click Next.

The installation of Policy Manager needs to update the Web server (OHS). In this case, the httpd.conf configuration file is updated. To confirm this update, retain the Yes option and then click Next.

Note: You have already updated the httpd.conf file during the WebPass installation and now you are again updating the same httpd.conf for Policy Manager installation.

Enter E:\infra\Apache\Apache\conf\httpd.conf in the file location and click Next.

You need to restart the Web server (OHS) so that the changes done by the Policy Manager installer takes effect. Execute the following commands in sequence from <infra_home>\opmn\bin and then click Next.

E:\infra\opmn\bin>opmnctl stopproc processs-type=HTTP_Server

E:\infra\opmn\bin>opmnctl startproc process-type=HTTP_Server

You can view the Readme page and then click Next.

Notice that Policy Manager has been successfully installed. Click Finish.

To verify the Policy Manager installation, access the Access Administration page using the following URL:

http://<hostname>.<domainname>/identity/oblix

To configure the Access System Console, click Access System Console and then click Setup.

OID will be the user directory server where access system can route the information for accessing user repositories. Select the Oracle Internet Directory option from the drop-down menu and click Next.

Provide the following information for the directory server hosting the user data and click Next.

You need to select the directory server hosting the configuration data. For this setup, select Oracle Internet Directory and click Next.

You can store the configuration data and user data either in the same LDAP server or in different LDAP servers. For this setup, you select the Store Configuration Data in the User Directory Server option and click Next.

You can store the policy data and user data either in the same LDAP server or in different LDAP servers. For this setup, you select the Store Policy Data in the User directory server option and click Next.

Provide the following information for the location for Oracle Access Manager Configuration data, Searchbase, and Policybase. Then click Next.

Note: o=oblix,dc=mydopartners,dc=com stores both the configuration and policy data.

Enter inetOrgPerson as the Person Object Class and click Next.

You need to restart the Web server (OHS). For this, perform the following steps and then click Next.

E:\infra\opmn\bin>opmnctl stopproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl startproc process-type=HTTP_Server

You need to specify the Root directory for the policy domains. The subdirectories for policy domains will be created under the location that you specify. Enter / and click Next.

Select the Yes option to configure the authentication schemas and click Next.

To configure the authentication schema, select the Basic Over LDAP check box and click Next.

Review the Basic Over LDAP authentication scheme configuration (retain all the default values) and click Next.

Select the Yes option to configure policies that will protect the NetPoint Identity System and Access manager and click Next.

The installation for Policy Manager is complete. You need to restart the Identity Server and the Web server (from the next three steps), and then click Done.

To stop the Identity Server, click Start > Control Panel > Administrative Tools and double-click Services. Right-click the Oracle Access Manager Identity Server (identity) service and select Stop.

You need to restart the Web server (OHS). For this, perform the following steps and then click Next.

E:\infra\opmn\bin>opmnctl stopproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl startproc process-type=HTTP_Server

To start the Identity Server, select Start > Control Panel > Administrative Tools and double-click Services. Right-click the Oracle Access Manager Identity Server (identity) service and select Start.

To verify access system console setup, access the following URL and click Access System Console:

http://<hostname>.<domainname>/access/oblix

Enter rohit.youngeras the username and abcd1234 as the password, and then click Login.

You can view the Access System Console information.

To install Access Server, you need to have administrative privileges. If you are logged in as a different user, you need to exit the installation, log in as the Administrator, and then restart the installation. Then click Next.

In the Destination Name text box, set the installation directory to e:\access and click Next.

Review the location to which Access Server is getting installed and the total disk size it would take for the installation. Then click Next.

Notice that the installer begins copying the Access Server files. Next select the Open Mode: No Encryption option for the Access client (Web gates) and Access Server to communicate and click Next.

You need to provide configuration information for the Access Server connection to the directory server containing Oracle configuration data. For this installation, you can provide the following values and then click Next.

Note: You can use your own values for all these parameters on the basis of any changes made to the environment setup.

The policy data is stored in OID. Select the Oracle Directory option and click Next.

Note: The policy data and configuration data are both stored in the same directory server instance of OID.

Provide the following values for the access server configuration details and click Next.

You can view the Readme page and then click Next.

You can review the Access Server configuration settings and click Finish. Next you need to start the Access Server service.

Start the Oracle Access Manager Identity Server (Access) service.

Note: You can start it by navigating to Start > Control Panel > Administrative Tools > Services, right-clicking the Oracle Access Manager Identity Server (Access) service, and selecting Start.

Enter rohit.younger as the username and abcd1234 as the password. Click Login.

Click Add New Access Gate, provide the following values, and click Save.

Note: Leave all the other values in the form in their default state.

Note the warning regarding associating an Access Server with this AccessGate. Scroll down and click List Access Servers to associate the AccessGate with an Access Server.

Click Add to select a new Access Server for the AccessGate.

Select ten.mydomain.com:6035 from the drop-down menu and then click Add. Note that the AccessServer you installed previously is now associated with this AccessGate and will accept communication requests from the AccessGate.

In Windows Explorer, navigate to E:\install_files\oam101401 and double-click the Oracle_Access_Manager10_1_4_0_1_Win32_OHS_WebGate.exe file, and then click Next. This command launches the Oracle Access Manager installer that will install the WebGate for OHS.

You need to have administrative privileges to run the installation. If you are logged in as a different user, you need to exit the installation, log in as the Administrator and then restart the installation. Then click Next.

In the Destination Name text box, set the installation directory to E:\webgate and click Next.

Review the location to which WebGate for OHS is getting installed and the total disk size it would take for the installation. Then click Next.

Notice that the installer begins copying the WebGate files for OHS. Next select the Open Mode: No encryption option for the transport security mode and click Next.

Provide the following values for the WebGate configuration and click Next.

The Web server needs to be configured by modifying the configuration of the Web server directory. This change is reflected in the httpd.conf file for the OHS. To automatically update this configuration, retain the automatic update selection and click Next.

You need to provide the absolute path for the httpd.conf file to the installer for WebPass. Click Browse and navigate to E:\infra\Apache\Apache\conf\httpd.conf and then click Next.

Notice that the Web server configuration has been modified. To restart the HTTP server, perform the following steps and click Next:

E:\infra\opmn\bin>opmnctl status

E:\infra\opmn\bin>opmnctl restartproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl status

You can view the Readme page and then click Next.

You can review the WebGate for OHS configuration settings and click Finish.

To verify the status of the installed WebGate, access the following URL:

http://ten.mydomain.com:7777/access/oblix/apps/webgate/bin/webgate.cgi?progid=1

Define the list of host identifiers for Oracle HTTP Server that is serving Oracle Single Sign On. Use the Host Identifiers feature to enter the official name for the host, and every other name by which the host can be addressed by users. A request sent to any address on the list is mapped to the official host name, and applicable rules and policies are implemented.

Log in to the Access System Console as rohit.younger.

To create a list of host identifiers for OHS serving OSSO, select Access System Configuration > Host Identifier > Add .

Enter all possible variations of the host name using your host name and IP address combinations. Click + beside the host name variations to add more variations. Click Save when finished. Log out of the Access System Console.

Log in to the Policy Manager as rohit.younger.

Now configure resources protected by this policy domain. Click the Resources tab of the OSSO Policy Domain. Click Add to add the first resource.

.

Using a policy domain, you will protect two resources of the type http - /sso/auth and /pls/orasso/orasso.wwsso_app_admin.ls_login.

Using the values shown in the following table, create two resources. Click Save after configuring each resource and click OK to confirm:

Configure default rules. Click the Default Rules tab and then click Add to create a new Authentication Rule with the following values. Click Save when done.

Click the Actions subtab to configure authentication success or failure actions. Click Add and configure Return Attributes for Authentication Success with the following information. Click Save when done.

Configure Policies for the OSSO policy domain. Click the Policies tab and then click Add to create the policy with the following values. Click Save when done.

Click the Authorization Rules tab. Click Add to create the authorization rule with the following values. Click Save when done.

Click the Allow Access subtab within the Authorization Rules tab and then click Add. Set the Role to Any one and click Save.

Click the Default Rules tab and click the Authorization Expression subtab. Click Add to add an Authorization Expression. Select OSSOAuthZ from the Authorization rules list and click Add. Scroll down and click Save.

Click My Policy Domains in the left pane. Select the check box beside OSSO policy and click Enable.

Now you will install and configure Oracle Single Sign On Authentication Plug-in. Compile the SSOOblixAuth.java file found here. Include e:\infra\sso\lib\ipastoolkit.jar and e:\infra\lib\servlet.jar in the class path. Use the command as shown below (all in one line). Assume that the location of SSOOblixAuth.java is the e:\input_files directory :

cd e:\input_files

e:\input_files>e:\infra\jdk\bin\javac –classpath e:\infra\sso\lib\ipastoolkit.jar;e:\infra\lib\servlet.jar -d e:\infra\sso\plugin SSOOblixAuth.java

The above command creates SSOOblixAuth.class and places it in the e:\infra\sso\plugin\oblix\security\ssoplugin directory.

You will now register the Java class with Oracle Single Sign On. Edit the policy.properties file in e:\infra\sso\conf and replace the simple authentication plug-in with the plug-in that you created in the previous steps. Navigate to the line:

MediumSecurity_AuthPlugin=oracle.security.sso.server.auth.SSOServerAuth

Comment out the existing line and add a new line to register your Java class. (When editing policy.properties, take care not to insert blank space at the end of a line.)

MediumSecurity_AuthPlugin=oblix.security.ssoplugin.SSOOblixAuth

Restart the single sign-on middle tier for the changes to take effect:

E:\infra\opmn\bin>opmnctl restartproc process-type=HTTP_Server

E:\infra\opmn\bin>opmnctl restartproc process-type=OC4J_SECURITY

Finally, you will verify the completion of integration. Using a separate browser window, access the Oracle Portal home URL http://ten.mydomain.com:7778/pls/portal. Click the Login link. The Basic over LDAP challenge should appear instead of the standard Oracle Single Sign On login page. Enter Bart.Lenox as the username with abcd1234 as the password, and click OK. You are now logged in to Oracle Portal.