Deploying an OPSS Application

This OBE requires that you have completed the OPSS Environment Set Up OBE.

This OBE requires that you have completed the OPSS Configuring an OID Authentication Provider in WebLogic OBE.

Start myxmldomain:

Click the icon to open a terminal window. Enter the following commands to start the myxmldomain AdminServer:

cd $DOMAINS/myxmldomain
./startWebLogic.sh

Make sure the WebLogic Server is running before continuing on to the next step.

Open FMW Control:

Open Firefox and browse to http://localhost:7001/em to open Enterprise Manager (EM) and gain access to FMW Control. Login using the following credentials:

User name: weblogic
Password: welcome1

Deploy OpssADFDemoApp application:

Expand the WebLogic Domain node in the left-hand pane, then right-clcik myxmldomain to show the FMW Control menu. Select Application Deployment>Deploy to start the deployment process:

Use Deployment wizard:

The FMW Control deployment wizard appears. The first step involves selecting the application you would like to deploy from the file system. In our case, the EAR file is local to where the web browser is running and where Enterprise Manager is running so either choice would work ok. In our case, we just used the "local to web browser" option and browsed for the /home/oracle/labs/apps/OpssADFDemoApp.ear file. Leave the deployment plan options as the default "Create a new deployment plan when deployment configuration is done" selection, and click Next.

The second step in the deployment wizard is for targetting a deployment to the servers of a domain. Your domain only has one server and it should already be selected as the target for the deployment. Ensure that it is and click Next.

The third step in the deployment wizard is for setting attributes related to an application's deployment, such as the application name and the context root of a web application. These options will be different for every application based on what components make up the application. For your application, leave the default OpssADFDemoApp as the name and context root, and click Next:

The fourth step is for configuring deployment settings. This is where you configure OPSS security settings. Click the Configure Security Settings edit icon to look at the current configuration:

This displays the Configure Application Security page. Ensure that Overwrite is selected for Application Policy Migration. This ensures that any remaining policies that may exist for the related application stripe are overwritten with the new policy specified in the application files. You can also ensure that when the application is undeployed that all policies associated with the application stripe are removed from the OPSS security store as part of the process. These options are set by default. Click Apply to save the settings.

This returns you to the previous Deployment Settings page. Click Deploy to start the deployment process:

The deployment process window is displayed. This window shows the status of the deployment. When the process is finished, it should say that the deployment was successful. Click Close to exit the window.:

Run application:

Now that the application is deployed to the domain, you must run the application to verify that it was deployed successfully and that the application's security data was migrated to the OPSS security store..

Using Firefox, browse to http://localhost:7001/OpssADFDemoApp/faces/view1 to use the OpssADFDemoApp application. Click the Start Here button as shown below.

You are then presented with a log in page. This demonstrates that the application is deployed on the server. However, you still need to determine if its security data was migrated to the OPSS security store.

Use each of the credentials below to log in separately to witness the behavior of the application. You will have to restart Firefox for each login to ensure a new session is getting created. Optionally, you can also use Firefox private browsing features to control session handling.

Credential 1:
User name: joeuser
Password: welcome1

Credential 2:
User name: weblogic
Password: welcome1

Within the application, an authorization request is made to determine if the currently logged in user can access the task flow that shows the calendar for the development workspace. Users that can see the calendar are granted access while users that cannot see the calendar are denied access. The joeuser account should be able to see the calendar, and the weblogic user should not be able to see the calendar. If the application behaves this way, then its security data was successfully migrated to the OPSS security store.

Shut down myxmldomain:

Shutdown myxmldomain by pressing Ctrl-C in the terminal window where you started it.