Installing ARCHIBUS Web Central with Oracle WebLogic and BEA WebLogic 8.x

This topic covers installing ARCHIBUS Web Central with the Oracle WebLogic application server. The text presumes you are familiar with this application server.

Note: The exact name of the WebLogic directory on your machine will depend on the version of WebLogic installed on your machine. To cover all versions, the below directions use the format "weblogicxx" as the directory name.

If you are using WebLogic 8.x, see Installing ARCHIBUS Web Central with BEA WebLogic 8.x later in this topic.

Oracle WebLogic 9.1 and later

Step 1: Build the EAR File

Build the deployment ARCHIBUS .WAR file in to an Enterprise Archive (.EAR) file that contains your ARCHIBUS license file.

Create two temporary folders:
\temp
\temp\tools
Copy these files from the release media:
WebLogic\_ear_buildarea folder into the \temp folder
ai-licenses.bin file into the \temp\tools folder.
If you are using WebLogic 10, create a weblogic.xml file that contains the entries below, and place this weblogic.xml file in the ARCHIBUS WEB-INF folder

<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns="http://www.w3.org/2001/XMLSchema-instance"
<session-descriptor>
<cookie-http-only>false</cookie-http-only>
</session-descriptor>
</weblogic-web-app>

Navigate to the \temp\tools folder and start _MakeEarFile.bat. The process will create the .ear file. It will take a minute or two.
You will find the archibus.ear file in the \temp\_ear_buildarea folder.

Note: WebLogic 10.3 and later turn on the “cookie-http-only” attribute in the servlet session descriptor by default. This default disables JavaScript from obtaining the contents of a session cookie. However, the Direct-Web Remoting (DWR) subsystem that ARCHIBUS uses for AJAX screen refreshes needs to have access to the session cookie in the JavaScript, as DWR uses the session cookie as a token to protect against cross-site request forgeries (CSRF). ARCHIBUS recommends that sites concerned with session spoofing and cross-site scripting use HTTPS. Notice that the “cookie-http-only” attribute value is sticky for the HTTP session in WebLogic 10.3.1 - WebLogic 10.3.3, meaning that the first webapp sets it and subsequent webapps cannot override the value.

Step 2: Deploy ARCHIBUS

Open the Configuration Wizard.
When the dialog opens, the "Create a new Weblogic domain" radio button is selected. Choose Next.
The "Select Domain Source" window opens. Keep the default values and choose Next.
The "Configure Administrator Username and Password" dialog opens. Enter a username and password and choose Next.
The "Configure Server Start Mode and JDK" dialog opens. Select the "Development Mode" radio button and the "Oracle Supplied JDKs" radio button.
Select "Sun SDK" and choose Next.
The Customize Environment and Services Setting dialog opens. Keep the default values and choose Next.
The Create WebLogic Domain dialog opens. Enter a domain name. Choose Create.
The Domain is now created. Choose Done.

The new domain is located in \\bea\user_projects\<domain name>
Create an ‘Archibus’ folder in this location.
Expand the EAR file in the Archibus folder.
After EAR file is expanded, copy the license file into the config folder located in \\archibus\WEB-INF\config and edit the afm-projects.xml to point to the correct project.
Start the Weblogic Admin server and login to the Admin Server Console.
In the Domain Structure section, select the Deployments link.
Click Lock & Edit and click Install.
The Install Application Assistant page opens. Navigate to the location of the archibus project, select the radio button for archibus, choose Next.
The next page opens and ‘Install this deployment as an application’ is selected by default. Choose Next.
When the next page opens, keep all default values. Choose Next.
When the next page opens, keep all default values. Choose Finish.
The Setting for Archibus page opens. Choose Save.
‘Settings updated successfully’ displays. Choose Activate Changes.
Under ‘Domain Structure’ select ‘Deployments’.
The Summary of Deployments page opens. Check the box next to archibus, and click ‘Start’ and ‘Servicing all requests’.
The Start Application Assistant page opens. Choose Yes.

C. Install the ARCHIBUS Help Systems

The ARCHIBUS online help files are not included in the standard EAR archive file because the WebLogic EAR deployment fails with files that have the deeply nested structure found in the help systems.

To install the help systems:

Use WinZip or another archive utility to expand \help\archibus-help.zip (located on the product DVD) into a temporary directory, preserving all subfolders.
The expansion process will create a series of folders, such as:
\webapps\archibus\schema\ab-system\help\archibus_fm_help\
\webapps\archibus\schema\ab-system\help\system-management\
From the temporary location, copy the \help\archibus_fm_help\ and \help\system-management\ directories to the\webapps\archibus\schema\ab-system directory on your system.
There is no need to stop the application server if it is already running.

D: Configure the Basic Rule Wizard for Java 6

Application servers that use Java 6, such as Oracle WebLogic 10 , require a Java 6-compatible version of the Basic Rules Compiler. The manual deployment procedure for this version is as follows. For information, see Installing the Basic Rule Compiler on Java 6 Web Servers,

BEA WebLogic 8.x

Note: ARCHIBUS does not formally support WebLogic 8.x.

Note: The Web Central WAR file does not include WEB-INF/lib/jsp-api.jar file because it is not necessary for the currently supported servers, which already include this jar file. However, if you are using an older version of the application servers, such as Web Logic 8, download this jar file and copy it to the WEB-INF/lib folder.

Step 1: Create the Domain

Before installing ARCHIBUS, you must first create a domain.

Use the Configuration Wizard and select the option to create a "New WebLogic Configuration."
Select "Basic WebLogic Server Domain." Press "Next."
Select "Express." Press "Next."
Enter a username and password for the administrative user of this WebLogic Domain, and press "Next."
Select the Configuration Startup Mode and the SDK you wish to use, then press "Next."
Enter a configuration name for your WebLogic domain, e.g. "archibus". Then press "Next." The wizard will install a new user domain in C:\bea\user_projects\domains\archibus (if you chose to name your configuration "archibus").

Step 2: Install the ARCHIBUS Web Central Files

Extract the WAR file to a directory inside C:\bea\user_projects\domains\archibus. Instructions for doing so are covered in the "Installation/Configuring ARCHIBUS Web Central" section of the Contents pane of System Management Help.

Typically you will name this folder C:\bea\user_projects\domains\archibus\archibus. As such, your config folder, for instance, is located at C:\bea\user_projects\domains\archibus\archibus\WEB-INF\config.

Copy your ai-licenses.bin file to your config folder. Configure your WEB-INF\config\context\compatibility.afm-config.xml file per the standard instructions.
Upgrade your XML parser to the version required by ARCHIBUS Web Central per the upcoming instructions.
Update your project database connections in afm-projects.xml per the standard instructions.
If you have a Windows server and wish to use the Sybase Runtime server for demonstration or testing of your configuration copy the JDBC-ODBC bridge file dbjodbc9.dll from \webapps\archibus\WEB-INF\lib to <bea_home>weblogicxx\server\bin.

See also the following web site: http://e-docs.bea.com/wls/docs81/deployment/overview.html

Step 3: Start the WebLogic Server

Start the server by clicking on Start/Programs/WebLogic Platform /User Projects/archibus/Start Server, or by running C:\bea\user_projects\domains\archibus\startWebLogic.cmd.

You will need to provide the administrative username and password that you specified when you created your WebLogic domain using the Configuration Wizard.

Step 4: Add a Web Application Domain

Next, add a new Web Application Domain through the Admin Console.

Open the Admin Console by browsing the URL http://localhost:7001/console/.
Enter the administrative username and password to open the console.
Open archibus/Deployments/Web Application Domains.
Choose "Deploy a new Web Application Domain."
Browse to the parent directory of the location where you put the extracted files from the WAR file (e.g. C:\bea\user_projects\domains\archibus).
You should now see three folders, one of which is another "archibus" folder which contains the extracted documents from the WAR file. Select the control next to this folder, and then click on "Target Module."
The console will deploy the Web application. Wait until the console says the deployment is complete.

Step 5: Configure WebLogic to Use the Parser Version Required by Web Central

The default parser provided with the WebLogic server is written to an older standard than that required by ARCHIBUS Web Central. You must install the parser version required by ARCHIBUS Web Central.

To do so, you must copy the parser JAR files into “endorsed” folder.

Create folder “endorsed” in C:\bea\jdk142_05\jre\lib.
Copy xercesImpl.jar, xalan.jar, xml-apis.jar files from your \archibus\WEB-INF\lib folder into “endorsed” folder (e.g. from C:\bea\user_projects\domains\archibus\archibus\WEB-INF\lib\ into C:\bea\jdk142_05\jre\lib\endorsed).
Restart your server so the new settings take effect.