Help Index

Help Contents

GEBS Reporting » Private: GEBS Reporting Web Publisher » Learn More » Installing and Upgrading » IBM WebSphere Application Server 6.1 or later

IBM WebSphere Application Server 6.1 or later

Pre – installation tasks

IBM Rational Publishing Engine must be installed on the server machine before deploying the ReportingArena Web Publisher. The server has to have installed IBM Websphere Application Server 6.1 or later.


Start the WebSphere Application Server. In order to open the WAS console open a web browser and enter the console URL. This URL is typically https://servername:port/console. The server and port might vary, depending on the server configuration.

Define a new Realm for the Web Publisher

A Realm is a “database” of usernames and passwords that identify valid users of a web application (or set of web applications), plus an enumeration of the list of roles associated with each valid user. You can think of roles as similar to groups in Unix-like operating systems, because access to specific web application resources is granted to all users possessing a particular role (rather than enumerating the list of associated usernames). A particular user can have any number of roles associated with their username.

To administer security realms via the Geronimo Administration Console, the Security Realms portlet is available on the Console Navigation menu on the left hand side. This portlet allows you to add a new security realm or edit an existing one.

Once the WAS console is opened, go to Security Realms section. Use the “add new security realm” link to define a new Realm for our Web Publisher application.

By default WAS supports four types of Realms :

When you create a new realm you will have to choose from the following realm types available:

  • Certificate Properties File Realm
  • Database (SQL) Realm
  • LDAP Realm
  • Properties File Realm

In the following section we will create a Properties File Realm. Also, we need to provide a unique Realm name .

Once the Name of the Security Realm and Realm Type fields are completed, go to the next page by pressing the Next button.

In this page, the User File URI and the Groups File URI fields needs to be completed. The rest of them are optional.

By default WAS contains the and files in the location : var/security/ folder where the var folder is located in the WAS root instalation folder. uses the <user_name>=<password> format uses the <group_name>=<user_name> format.

Note: See the following examples for additional details.

New users and groups can be added by editing this files or by using the Console User Interface.

Provide the file to the Users File URI and the file to the Groups File URI. The files must be prefixed with theire location started from the WAS instalation directory.

By default the values will be :

  1. Users File URI = /var/security/
  2. Groups File URI = /var/security/

After the fields are completed, press Next. The next page will display some options and will allow the realm creator to test the newly created Realm :

Use the Test a Login button to test the realm, or press Skip Test and Deploy button to create the Realm.

Create the security plan files

Now that the realm was created, the security files needs to be created for each war we need to deploy. Since there are two WAR files which need to be deployed (webpublisher-rest-services.war and webpublisher-webui.war), two security plan files are required.

The security plan files needs to contain the following sections :

  1. context-root – the context path of the Web Publisher REST Service (/webpublisher-rest-services for webpublisher-rest-services.war and /webpublisher-webui for the webpublisher-webui.war).
  2. security-realm-name – the name of the newly created Realm
  3. role-mappings – map the rols defined in the web.xml file.

The plan for the webpublisher-webui.war file should be something like this :

And the plan for the webpublisher-rest-services.war file should look similar:

The only difference between the two files is the context-root element.

Both security plans are using the same realm and the same role-names. The role-name represent one of the roles defined in the Web Publisher and the name attribute needs to point to a group from the file.

Deploy the Web Publisher WARS

The Web Publisher WARS can be deployed using the User Interface of the console.Go to Deploy New section from the Application menu and in the first filed select the webpublisher-rest-services.war file using the file browser. For the second filed select the plan file corresponding to the the webpublisher-rest-services.war file and press Install.

The same procedure is used to deploy the webpublisher-webui.war file.