uc.pngInstalling, configuring and deploying the RRDI p2pd.ear file on WAS in a federated environment

Authors: PhilippeChevalier
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.

#Introductory paragraph

Configuring the report server

During installation you opted to manually install the report server, configure the WebSphere Application Server instance to host the report server, and build, deploy, and install the enterprise archive (EAR) files.

Here is a high-level list of the configuration tasks

  1. Create and configure a new WebSphere Application Server profile to host the report server on a federated instance.
  2. Setup the Jazz Name Space
  3. Configure the RationalReport profile to host the report server.
  4. Build the report server enterprise archive (EAR) file.
  5. Install the report server enterprise archive (EAR) file.

Create and configure a new WebSphere Application Server profile to host the report server on a federated instance

  1. Create a new WebSphere Application Node and Server profile called RationalReport to host the report server.

  1. Navigate to the $WAS_INSTALL/bin/ProfileManagement directory.

Example: /opt/IBM/WebSphere/AppServer855/bin/ProfileManagement

Note: The WAS_HOME by default is usually /opt/IBM/WebSphere/AppServer in the case of this document the value will reflect the version WebSphere application server version number used /opt/IBM/WebSphere/AppServer855

  1. Start the Profile Management tool using the following command:


This pmt.sh tool will open a GUI interface to create WebSphere profiles.



To create Profiles, user the “Create” button on the right side of the window. You will be sent to the next panel called 'Environment Selection'.


As shown in the figure above, Use the option 'Custom profile', and click 'Next' at the bottom of the window.

The next panel will be the 'Profile Creation Options'.


You will be selecting the profile type, To create a managed node select the 'Advance profile creation' option, and then select next.

This will lead you to the 'Profile Name and Location' panel.


Replace the 'Profile name' and 'Profile directory' fields with the name for the profiles and its location, in this case we will use RationalReport for the profile name and update the profile location to target the $WAS_HOME/profiles/RationalReport, See above figure. Click on the 'Next' button at the bottom of the window.

The following panel will be called 'Node and Host Name', On this panel you will be assigning the node name and the host name for the profile you will be creating.


In this panel we selected to call the node myserver2Node2 and the host name was myserver2.ibm.com. The Node reference *Node2 because on the machine used for this example was *Node1 was already existing.

Click Next to move to the next panel. Called 'Federated'. You will need a few details to setup the federated environment

The host name of the Deployment Manager (Dmgr) The SOAP port for the Dmgr The WebSphere administrator user name and password

Caution: the Dmgr service must be up and running already, make sure that it is.


In this case the host name was myserver.ibm.com and the SOAP port was 8879 (default), the user name was wasadmin.

Note: To collect the SOAP port of the Dmgr, log in to the Dmgr console and navigate to the 'System administration → Deployment manager' using the right side panel of the console, select the link. On the Left you will find a link called 'Ports' with a + sign beside it. Select the + sign and this will reveal the ports assigned to the Dmgr.


You may see a check box to 'federate the node later' make sure it is unchecked.

Click on the Next Button.

The new panel will be Security Certificate (Part 1),


Leave the default values and click on the Next Button

The new panel will be Security Certificate (Part 2)


Like the previous Panel leave the default values. The Default keystore password is WebAS.

Click on the 'Next' button.

The Panel will now be called 'Port Value Assignment' generally the profile creation will target port that have not already been assigned on the server. Review the values to find any port conflicts.


Click the Next button.

The last panel will be called 'Profile Creation Summary'. You will find a short summary of the details you selected for the profile creation.


To Complete the task, click on the 'Create' button. You will see a new panel called 'Profile Creation Progress' which will report back the progress of the setup task.


The last panel is the 'Profile Creation Complete' panel,


Select the Finish button and close the Profile Management Window.

To validate that the new profile, or in this case the server node was added to the Dmgr. Log in to the Dmgr console, and on the left Panel of the Console navigate to the 'System administration → Nodes'. On the Right Panel you will see the new registered node.


It is possible that you find that the status of the node Is not consistent with the other nodes. If this is the case, select the check box beside the myserver2Node2, and click on the Synchronize button at the top of the table view.


The status will become consistent with the other nodes.

It is also possible to review the node up status in the 'System administration → Node Agents'


You may expect since the server Node was added to the Dmgr, the RationalReport server be already in place. To verify, navigate to the '!WebSphere application servers' link on the left panel of the Dmgr console.


As you see the image above, the RationalReport server was not added. Running the Profile management tool with the option selected in the process above only created a WebSphere node to support new server instances on the myserver2Node2.

It is now time to create the RationalReportServer. Click on the 'New...' button at the top of the table view. The view will change to a panel called 'Create a new application server'. Using the 'Select node' field select the arrow on the right and click on the newly created node 'myserver2node2' and provide a name for the new server. In this case we will use 'RationalReportServer'


Click on the 'Next' button.

This will lead you to a new panel. Select the template for the Application server you are creating.


Use the template 'default', and click on the 'Next' button.

The new panel will be port selection.


To simplify the process this example will use the 'Generate Unique Port' option, and click next.

The last panel is a summary panel.


Review details and click on 'Finish'.

This will return you back to the 'Application servers' table. You will also have an extra message panel at the top of the panel. This is message will be a reminder to same the master configuration. You should also see the new 'RationalReportServer' instance


Click the 'save' link to save the master configuration.

Note: WebSphere application server configuration very often required the master configuration save action. It is recommended that you select the save link as often as possible to avoid losing any configuration points. This document will not repeat this action item, please keep it in mind.

After the master configuration has been saved, return to the '!WebSphere application server' link on the left panel. The newly created server status will be marked as down. We now need to test the server by starting the application and reviewing the SystemOut.log.

To start the server, select the check box beside the RationalReportServer and click on the start button at the top of the table view.


If the start process should be completed with a green arrow in the status column.

To double check the status of this new server you should review the SystemOut.log file. This files will be located in the WAS_HOME/profiles/$PROFILE_NAME/logs/$SERVER_NAME

Example: /opt/IBM/WebSphere/AppServer855/profiles/RationalReport/logs


Generally if you do not see any Java Exception and you see the message “Server RationalReportServer open for Business”.



At this point you have successfully created the WebSphere application node and server instances.

Configure the RationalReport profile to host the report server

Using the Dmgr Console, And verify if the RationalReportServer is up and running. Using the let panel of the console navigate to the '!WebSphere application servers' and select the link/


Click the RationalReportServer link and, in the Server Infrastructure section, expand the Java and Process Management node, continue and select the Process Definition link, and click the Java Virtual Machine link.


The bread crumbs links should be Application servers > RationalReportServer > Process definition > Java Virtual Machine.

In the configuration tab, Enter inital and maximum JVM heap size. In the field 'Initial heap size' set the value to 256 and the 'Maximum heap size' set the value to 1024.


Click the 'Apply' Button at the bottom of the page. Your page should be be back to Application servers > RationalReportServer > Process definition

On the top right side of the page, select the 'Environment Entries' link


In this configuration panel you will be entering three environment variable.





Click Apply, and click Save.

If you are using administrative security, expand the Security node on the left sidebar and then disable administrative security by clearing the Enable application security option. Click Apply, and click Save.

Restart the RationalReport profile. by stopping and starting the report server.


Setup the Jazz Name Space, create the jazzns_config.xml file

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project