Home » Fusion Middleware & Colab Suite » WebCenter Suite & Portal » portlets in Oracle9iAS
portlets in Oracle9iAS [message #76778] Fri, 01 August 2003 09:05 Go to next message
marcos
Messages: 8
Registered: March 2002
Junior Member
Hi everybody,

I'd like to know what can i do to customize the login page in Oracle9iAS, in other words i want to have my own page to register the users in the portal. Something else, could you tell me the steps to establish a connection with a database in a page, what's the best way? jdbc, plsql, etc.

Thanks very much for your attention.
Re: portlets in Oracle9iAS [message #76780 is a reply to message #76778] Mon, 04 August 2003 07:35 Go to previous message
e-ffx
Messages: 1
Registered: August 2003
Junior Member
There is a lot of documentation out there that directly explains how this is achieved. It is done differently based on the Portal release you are using. For 9.0.2 follow below:

SCOPE & APPLICATION
-------------------

The following instructions pertain to 9iAS Release 2 (9.0.2). You will need to have completed an Infrastructure installation and one of the Midtier installations. Please refer to the Installation Guide appropriate for your platform for specific instructions on installing both the Infrastructure and Midtier. If you need to customize any of the default pages for the Single Sign-On Server that control logging into an application using SSO, you can use the following as a guide to configure the SSO server to use the sample customized pages from Chapter 8 - "Customizing the Single Sign-On Interface" located in the Oracle9iAS Single Sign-On Administrator's Guide Release 2 (9.0.2).

Creating the OC4J WAR File Directory Structure -----------------------------------------------------------

To make deployment as easy as possible, you will create a simple OC4J .war file to deploy via the Enterprise Manager (EM) Website. Once this .war file is created, you will deploy the .war file into OC4J_home System Component.

1) Create a temporary working directory on your file system. This will be the location were we will built the OC4J .war file. (i.e. /u01/mySSO)

%> cd /u01
%> mkdir mySSO

2) Change to your working directory. %> cd mySSO 3) In your working directory, create a META-INF. Your complete directory structure should resemble the following: u01 | `---mySSO | `--- WEB-INF

Creating the JSP Files
-----------------------

Now you will need to create the .jsp files. These files will be serve as your new SSO Login, Change Password and Sign Off pages. 1) Create the followings files in the mySSO directory, using the sample code from SSO Admin Guide. login.jsp change_password.jsp single_sign_off.jsp Your directory will now be populated with three files and will look like the following: u01 | `---mySSO | &#124--- WEB-INF | &#124---login.jsp &#124---change_password.jsp `---single_sign_off.jsp

Create the web.xml File
------------------------

To have a complete .war file for OC4J to be a considered a J2EE application, you need to have a web.xml file. 1) Cut and paste the following into a text editor and save the file the name of web.xml: <?xml version="1.0"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"> <web-app> </web-app> Your directory structure is now complete and should resemble the following. u01 | `---mySSO | &#124--- WEB-INF | `---web.xml | &#124---login.jsp &#124---change_password.jsp `---single_sign_off.jsp

Creating and Deploying the WAR File ------------------------------------

With the above directory structure, you are now ready to create a mySSO.war file. 1) Change to the mySSO directory and run the following command: jar cvf mySSO.war . Once this is complete, you will now have a mySSO.war file in the mySSO directory. You will now use this file to deploy via the EM Website. 2) Using a browser, connect to your EM Website. The URL is often like the following: http://<host.domain>:1810 NOTE: Where <host.domain> is the hostname and domain of your web server where the Infrastructure is installed. 3) After entering your ias_admin password, navigate to your Midtier installation. 4) Listed under the 'System Components', click on 'OC4J_home'. This will take you to a page listing all the 'Deployed Applications' for this component. 5) Click on the 'Depoly WAR file' button. 6) From the 'Deploy Web Application' screen, locate and click on the 'Browse...' button to locate the mySSO.war file for the 'Web Application' field. 7) In the 'Application Name' field, enter 'mySSO' (without the surrounding quotes). Cool In the 'Map to URL', enter '/mySSO' (without the surrounding quotes). 9) Click the 'Deploy' button to complete deployment of the mySSO WAR file.

Testing the JSP Files
----------------------

Once this is complete, you can test to see if the JSP files are working and there are no coding problems with them. http://<host.domain>:<port>/mySSO/login.jsp http://<host.domain>:<port>/mySSO/change_password.jsp http://<host.domain>:<port>/mySSO/single_sign_off.jsp NOTE: Where <host.domain> is the hostname and domain of your web server where the Midtier is installed and <port> is the port number of your Midtier HTTP Server. (default is 7778) At this point, when each of the JSP files are called from a browser, you should receive the the following error message: ERROR: This page can not be accessed directly! This is normal. You do not want a client to access these JSP files directly. The SSO Server will be able to access them once you complete the following section.

Modifying the SSO Metadata Repository Table --------------------------------------------

As outlined in Chapter 8 - Customizing the Single Sign-Of Interface document: The customized Login, Change Password, and Single Sign-Off pages are controlled in the Metadata Repository of the Infrastructure installation of your 9iAS Release 2 (9.0.2). The WWSSO_LS_CONFIGURATION_INFO$ table in the Single Sign-On schema, orasso, contains the LOGIN_URL column, which controls these pages. The LOGIN_URL column contains three values separated by a space. The first value specifies the URL for the Login page, the second the URL for the Change Password page, and the third the value for the Single Sign-Off page. By default, the LOGIN_URL column contains the values UNUSED UNUSED UNUSED, which specify that the Login, Change Password, and Single Sign-Off pages use the standard Single Sign-On pages. For our example, we will modify all three values. For more information on how to only modify specific pages, please refer to Chapter 8. 1) On the database where the Single Sign-On server is installed, log in to the Single Sign-On schema using SQL*Plus, as in the following example: sqlplus orasso/orasso NOTE: By default your orasso password is randomized during the installation of the Infrastructure. You may need to do a ldap search to determine the actual password. 1a) To use the ldapsearch command to determine the randomized password for the orasso schema, enter the following command on the Infrastructure machine command line: ldapsearch -D cn=orcladmin -w <superuser_password> -p 4032 -h <hostname> -b "cn=IAS,cn=Products,cn=OracleContext" -s sub -v OrclresourceName=ORASSO | grep orclpasswordattribute NOTE: Where <superuser_password> is the password of the orcladmin user of OID. By default, this is the same as your ias_admin user after a new Infrastructure install. Where <hostname> is the hostname where the Infrastructure is installed. 2) To replace Login, Change Password, and Single Sign-Off pages with the customized pages, update the LOGIN_URL column as shown: UPDATE WWSSO_LS_CONFIGURATION_INFO$ SET LOGIN_URL='http://<host.domain>:<port>/mySSO/login.jsp http://<host.domain>:<port>/mySSO/change_password.jsp http://<host.domain>:<port>/mySSO/single_sign_off.jsp'; 3) Commit your changes and log out of sqlplus. You now can test your customized pages by opening a new browser and logging into an application that utilizes SSO. For example: htp://<host.domain>:<port>/pls/orasso NOTE: Where <host.domain> is the hostname and domain of your web server where the Infrastructure is installed and <port> is the port number of your Midtier HTTP Server. (default is 7777) Click on the 'Login' link in the upper right corner. You should now see a new customized SSO login page.
Previous Topic: portal login page?
Next Topic: variables of environment as in php
Goto Forum:
  


Current Time: Tue Aug 11 17:46:39 CDT 2020