Rational Portfolio Manager – Websphere Application Server Setup

Below is the Websphere Application Server Environmental Variables that needs to be create for Rational Portfolio Manager EAR installation:

RPMEnvironmental Variable

After these variables has been defined you can deploy the EAR file.

Configure the Rational Portfolio Manager to the Websphere Application Server EAR file that has been successfully deployed by specifying the IP address of the application.

Login to the Rational Portfolio Manager with username and password as specified in LDAP or specified in the Oracle or DB2 Database.

Web Services from Stateless Session EJB3 with Websphere Integration Developer

How to create a bottoms-up Websphere with Websphere Integration Developer that is deployed to Websphere Application Server V7.

Below is the steps to create an simple Web Service using Websphere Integration Developer:

1. Open up Websphere Integration Developer and create an new EJB Project

Step 2: Click on the ‘New’ button to create a new EAR Membership.

The following 3 files will be created

Step 3: Create a new Stateless Session Bean

Step 4: Complete the following information below (Important to select Remote)

Step 5: Open the Bank interface object and add a method.

Step 6: Open your Stateless Session Bean File and right click and select ‘Override/Implementation Methods’, make sure the @Override notation is added to your code (see in red block)

Step 7: Add code inside your method

Step 8: Verify that there is no error.

Step 9: Add an Application Server to your WID IDE and start the server.

Step 10: Right click on your Application Server and click on ‘Add and Remove Projects’ and Select the BankAccount project

Step 11: Verify that the Application Server has successfully synchronized the new project and no errors occurred.

Step 12: Creating the Web Service is done in the following Steps, right click on your Stateless Session Bean and Select Web Service -> Create Web Service.  Your will see the following screens:

Confirm that the right Server type is selected, being WAS, WPS, WBM or any Application Server

For this example the binding type is HTTP, you can change it to JMS or EJB.

As we only have one method, select the method BankAccount. WS-Security can be added in this step to create a more secure Web Service.

Optional you can deploy your WSDL to the Websphere UDDI for Web Services discovery. Click Finish to complete. Confirm that Web Service creation was successful.

Step 13. Test your new Web Service by opening Web Services Explorer and browsing for the Bank.wsdl

Step 14: Enter the relevant information into the two fields provided and click ‘GO’

Web Service Completed successfully.  This Web Services can now be deployed to Websphere Registry and Repository to be discovered by all other systems in your environment.

Setup Rational Jazz Team Server with Rational Jazz Team Client

Following steps will help you setup Jazz Team Server for RAD.

Step 1: Start Jazz Team Server:

Step 2: Confirm that server has started up successfully:

Step 3: Open your web browser to: https://localhost:9443/jazz/admin.

Username: ADMIN

Password: ADMIN

Step 4: Load license file for Jazz Team Server

Step 5: Open Rational Team Client

Step 6: Create a new repository connection

Step 7: Enter the IP address and Username and Password of your Rational Jazz Team Server

Build Web services with Rational Application Developer Version 6.0

Use IBM WebSphere Application Server to deploy Web services and publish them onto a UDDI registry using IBM Rational Application Developer Version 6.0. Part 1 of this tutorial series focused on the use of Rational Application Developer for designing a work order creation service. The example used in this tutorial uses a Web service to facilitate multiple clients creating work orders in your system.

This tutorial shows you how to:

  • Deploy a Web service and its implementation code on a machine running WebSphere Application Server Version 6.0.
  • Use Rational Application Developer Version 6.0 and the Web Services Explorer tool to publish your Web service onto a UDDI registry.
  • Discover services published on the registry from client applications.


Defining Datapower XB60 components and Profile Linkage

IBM WebSphere DataPower B2B Appliance XB60 simplifies, helps secure, and accelerates your B2B trading partner connectivity. The XB60 is a purpose-built B2B Gateway for simplified deployment and hardened security. This 1U (1.75 inch thick) rack-mountable network device is powered by unique technology to help your business:

– Easily manage and connect to trading partners using industry standards

– Extend integration beyond the enterprise with a securely deployed B2B Gateway in the DMZ

– Improve the performance and scalability of B2B interfaces

– Govern B2B integration points through consolidated trading partner management

Datapower XB60 Profile Linkage

The B2B Partner Profile is the configuration object where the trading partner information is defined. This information includes the profile name, profile type, business IDs, AS security, destinations for document routing, and contact information.

A trading partner is either an internal or external trading partner based on the understanding that an internal trading partner exists within the corporate enterprise and an external trading partner exists outside of the enterprise. Trading partners have unique business IDs. However, if a profile is defined as internal, that trading partner might also have the same business ID defined in their external definition, because an internal trading partner and an external trading partner are different objects.

Web Service Security Testing with Rational AppScan

How secure are you web service really?Are you web services more secure going through Datapower?Do you need answers for these and many more security question then Rational AppScan is the answer.

Topology for my test: EJB running on WAS -> Web Service (wsdl) Front Side Handler through Datapower.
Import wsdl file into Rational AppScan there Datapower is the Front side handler. Click on the Run button to start the Web Service Testing. AppScan tests the web service for different, random parameters.

After the scan completed a report was generated for the errors, information or warning for specific Web Service parameters and how to fix the errors in your Java code.

This is a great way to see how you can improve web service security where Datapower is the from side handler managing web service security.

Issue Information

Advisory – Application Error

Fix Recommendation