Instructions for installing the Flights of Fancy application.
*************************************************************


======================================================================
----------------------------------------------------------------------
                   Pre Installation Section 
----------------------------------------------------------------------
======================================================================

----------------------------------------------------------------------
Step 1: If Not Installed, Install The Oracle Web Single Sign-On SDK
----------------------------------------------------------------------
Perform the required setup required by the login server SDK. This is detailed in 
in the Install.txt in the SDK.

This includes:
- Adding your new Partner Application through the Portal UI. This is where
  you register the Flights of Fancy Partner Application with the Login Server.

   You can do this by logging into Oracle Portal, clicking on the Administer tab, 
   and choosing the Login Server Administration link.  You can then administer 
   Partner Applications to add a new Partner Application.  
   Choose an application name for your Partner Application.  
   Note the Application name you choose, for use later on. For the Home URL, 
   you can choose to use the Portal Home URL  since this will be invoked if you 
   press 'Cancel' while logging in with the Login Server.  For the Success URL, 
   you need the URL to the partner application.
- Loading the PL/SQL crypto packages and the OWA packages if not already loaded in your database.
- Create a schema in which to install the Oracle Web Single Sign-On SDK .
- Loading SSOHash.class using loadjava for the Partner schema you created.
- Running loadsdk.sql in the Partner schema you created.

- Editing and running the regapp.sql script as directed.

-------------------------------------------------------------------------------
Step 2: If Not Installed, Install The JPDK On The Partner Application Listener
-------------------------------------------------------------------------------
Follow the instructions to install JPDK which includes adding provider.jar in jserv.properties. 

wrapper.classpath=C:\jpdk\lib\provider.jar

======================================================================
----------------------------------------------------------------------
                        Partner listener setup
----------------------------------------------------------------------
======================================================================

----------------------------------------------------------------------
Step 3 - On The Partner Application Listener
----------------------------------------------------------------------
On the partner applications listener, create a directory ˜FancyFlightsPartner" and copy samples.jar and provider.xml under this directory. 

----------------------------------------------------------------------
Step 4 - On The Partner Application Listener
----------------------------------------------------------------------
In the jserv.properties file add the following section containing the wrapper.classpath statements. 
wrapper.classpath=C:\FancyFlightsPartner\samples.jar 

Save and close the jserv.properties file. 

----------------------------------------------------------------------
Step 5 - On The Partner Application Listener
----------------------------------------------------------------------
In the zone.properties file add the complete path of the directory ˜FancyFlightsPartner" under repositories section. 
repositories=C:\FancyFlightsPartner\samples.jar 

----------------------------------------------------------------------
Step 6 - On The Partner Application Listener
----------------------------------------------------------------------
Under the Servlet Aliases section, add the alias that points to the Provider Adapter: 

servlet.flightsprov.code=oracle.portal.provider.v1.http.HttpProvider 
servlet.flights.code=oracle.portal.sample.v1.devguide.partnerApp.PartnerServlet 

----------------------------------------------------------------------
Step 7 - On The Partner Application Listener
----------------------------------------------------------------------
Under the Aliased Servlet Init Parameters section, add the initial arguments needed by the sample. This points the Adapter (sample) to the location of the provider.xml file. Make sure to modify the directory to point to the correct location of the provider.xml file. 

servlet.flightsprov.initArgs=provider_root=C:\FancyFlightsPartner, sessiontimeout=30000

Note: the sessiontimeout must match the session.timeout setting located in the zone.properties of your Apache listener. Both settings are specified in milliseconds. 

----------------------------------------------------------------------
Step 8 - On The Partner Application Listener
----------------------------------------------------------------------
Also in the Aliased Servlet Init Parameters section, add the initial arguments needed by the sample to connect with the partners database and the SSO server. The parameters need to be set up for both the flightsprove(partner code used with portal) and the flights (partner servlet used independent of the portal). Make sure to modify the the arguments to suit your environment.

servlet.flightsprov.initArgs=listenerToken=flights:portal30_sso:5000
servlet.flightsprov.initArgs=requestedUrl=http://flights.oracle.com/servlets/flights
servlet.flightsprov.initArgs=onCancelUrl=http://flights.us.oracle.com
servlet.flightsprov.initArgs=partnerAppCookieName=SSO_PAPP_SERVLET_ID
servlet.flightsprov.initArgs=partnerAppCookieDomain=oracle.com
servlet.flightsprov.initArgs=partnerAppCookieScope=/
servlet.flightsprov.initArgs=partnerAppCookieDesc=SSO application cookie
servlet.flightsprov.initArgs=dbSchema=scott
servlet.flightsprov.initArgs=dbPassword=tiger
servlet.flightsprov.initArgs=dbhost=flightsdb.oracle.com          
servlet.flightsprov.initArgs=dbport=1521    
servlet.flightsprov.initArgs=dbsid=orcl           

servlet.flights.initArgs=listenerToken=flights:portal30_sso:5000
servlet.flights.initArgs=requestedUrl=http://flights.oracle.com/servlets/flights
servlet.flights.initArgs=onCancelUrl=http://flights.oracle.com
servlet.flights.initArgs=partnerAppCookieName=SSO_PAPP_SERVLET_ID
servlet.flights.initArgs=partnerAppCookieDomain=oracle.com
servlet.flights.initArgs=partnerAppCookieScope=/
servlet.flights.initArgs=partnerAppCookieDesc=SSO application cookie
servlet.flights.initArgs=dbSchema=scott
servlet.flights.initArgs=dbPassword=tiger
servlet.flights.initArgs=dbhost=flightsdb.oracle.com          
servlet.flights.initArgs=dbport=1521    
servlet.flights.initArgs=dbsid=orcl           

The following outlines the syntax for these variables:
-  listenerToken - Listener token for your application. This argument is used to identify the partner application's configuration information located in the partner database's SSO tables .
     syntax - <application name>:<SSO Webserver host name>:<port>
- requestedUrl - The URL to the partner application. This is the URL that the SSO server redirects the user to after the user has succesfully logged in.
- onCancelUrl -  The URL to the partner application's public page. This is the URL that the SSO server redirects the user to after the user fails to succesfully log in.
- partnerAppCookieName - The partner application cookie name.
- partnerAppCookieDomain - The partner application cookie domain.
- partnerAppCookieScope - The partner application cookie scope.
- partnerAppCookieDesc - The partner application cookie description.
- dbSchema - Partner schema where the Oracle Web Single Sign-On SDK is installed
- dbPassword - Password to partner schema
- dbhost -The host address used for the database       
- dbport - The host port used for the database
- dbsid - The host service name used for the database. 

Save and close the zone.properties file. 

