Table of Contents
List of Figures
Figure 1: Bea WebLogic Server 9.2 Console. 6
Figure 2: Create a new JDBC data source. 8
Figure 3: Specify the database and login. 9
Figure 4: Complete creation of JDBC data source. 10
Figure 5: Deploy the datasource to a target server. 11
Figure 6: Enable WebLogic security. 12
Figure 7: Create global roles. 13
Figure 8: Add conditions. 14
Figure 9: Add groups to users. 15
Figure 10: Deploy the opencrx-core-CRX-App EAR. 16
Figure 11: Select Deploy EJBs. 17
Figure 12: Install deployment as application. 17
Figure 13: Deployment optional settings. 18
Figure 14: Verify the deployment settings. 19
Figure 15: Deployment of opencrx-core-CRX-Web.ear 20
Figure 16: Activate changes. 20
Figure 17: Deploy the Web EAR and check show me all installation options. 21
Figure 18: Enterprise applications in state Active. 21
List of Listings
Listing 1: startWebLogic.cmd with openCRX-specific properties. 7
This book describes the installation of openCRX for BEA WebLogic Server 9.2.
The intended audience are openCRX and application server system administrators.
This book describes the installation of openCRX for BEA WebLogic Server 9.2. The book assumes that you are familiar with BEA WebLogic Server 9.2 administration and deployment concepts.
We make use the following pictograms:
As a first you must download and install the following software:
• Install BEA WebLogic Server 9.2.
• Download openMDX from here (http://sourceforge.net/project/showfiles.php?group_id=75132).
• Download openCRX from here (http://sourceforge.net/project/showfiles.php?group_id=95219).
In a first step install WebLogic. You should be able to start and stop WebLogic and launch the WebLogic Server Console as shown below:
Figure 1: Bea WebLogic Server 9.2 Console.
The openCRX installation requires the following steps:
Copy the openMDX and JDBC driver libraries to a place where WebLogic has access to it. You can do this as follows:
Then you must add openCRX-specific options to the WebLogic startup script. Modify startWebLogic.cmd as shown in Listing 1. Restart WebLogic in order to activate the settings.
Listing 1: startWebLogic.cmd with openCRX-specific properties.
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" %*
The openCRX application requires the configuration of a JDBC datasource which connects to the openCRX database. You do this a follows:
Navigate to Services > JDBC > Data Sources and click on New. Fill the fields as follows:
Figure 2: Create a new JDBC data source.
On the next screen you must configure the following properties as shown below:
Figure 3: Specify the database and login.
Then click Next. Verify the database connection properties on the next page as shown below and then click Test Driver Configuration.
Figure 4: Complete creation of JDBC data source.
If everything works fine you should see the Connection successful message. Click Next. On the next page you must select the servers where the new datasource should be deployed to. You must select the servers to which you plan to deploy the openCRX application. This is shown below:
Figure 5: Deploy the datasource to a target server.
openCRX requires that each user is properly authenticated. This allows openCRX to correlate a session to user-specific application data and to perform access control. openCRX does not support non-authenticated sessions. User authentication must be configured as follows:
Figure 6: Enable WebLogic security.
Then select Roles and Policies > Realm Roles > Global Roles. Create the roles OpenCrxRoot, OpenCrxAdministrator and OpenCrxUser as shown below:
Figure 7: Create global roles.
In a next step you must add the Caller is a member of the group membership condition to the newly created global roles as follows:
The global role OpenCrxAdministrator should then look as shown below:
Figure 8: Add conditions.
You now have successfully mapped the role names defined by openCRX to WebLogic-defined role names.
You are now ready to create users and make them member of the groups OpenCrxRoot, OpenCrxAdministrator or OpenCrxUser. The servlets in EAR opencrx-core-CRX-Web.ear require the users to be member of the groups OpenCrxUser, OpenCrxAdministrator or OpenCrxRoot. Standard users are member of the group OpenCrxUser. Segment administrators are member of the group OpenCrxAdministrator. This is shown in the figure below.
As a start add the following users:
Figure 9: Add groups to users.
openCRX comes with two enterprise application archives (EAR):
In a first step you deploy opencrx-core-CRX-App.ear. Select Deployments > Applications > Deploy a new Application > Upload your files. Click Browse and select the file opencrx-core-CRX-App.ear as shown below:
Figure 10: Deploy the opencrx-core-CRX-App EAR.
Repeat this step for the file opencrx-core-CRX-Web.ear. The files are now ready for deployment. Navigate to Deployments > Applications > Deploy a new Application and then to the upload directory of your administration server, e.g. domains/mydomain/myserver/upload. In this directory you should find the files you have just uploaded. Select the file opencrx-core-CRX-App.ear:
Figure 11: Select Deploy EJBs.
Then click Next. On the next screen you must select whether to install the archive as library or application. Check Install this deployment as an application as shown below:
Figure 12: Install deployment as application.
Click Next. On the next screen specify optional settings. Make sure that the security model DD only is selected as shown below. Leave the application name unchanged.
Figure 13: Deployment optional settings.
On the next screen specify the deployment targets and the application name. Leave the default values unchanged and then click Deploy as shown below:
Figure 14: Verify the deployment settings.
Repeat the deployment step for the archive opencrx-core-CRX-Web.ear. The summary screen should look as shown below:
Figure 15: Deployment of opencrx-core-CRX-Web.ear
Do not forget to activate the changes by clicking on Activate Changes:
Finally, the the deployed applications should look as shown below:
Figure 17: Deploy the Web EAR and check show me all installation options.
Before you can use openCRX you must start the applications opencrx-core-CRX-App and opencrx-core-CRX-Web. Check the corresponding boxes and then select Start > Servicing all requests. Make sure that the state changes to Active as shown below:
Figure 18: Enterprise applications in state Active.
Before you proceed to the openCRX QuickStart guide make sure that you have deployed and started all applications. The application is initialized the first time a user calls the login page. If the startup fails consult the following log files: