How to check if your Web Service is WS-I compliant. You can use SOAPUI which is an open source tool to test Web Services.
Step 1. Import your WSDL file into a new SOAPUI project.
Step 2: Right click on your Project Name and select ‘Check WSI Compliance’
Step 3: Download the report created by SOAPUI, an example is an WS-I compliant Web Service looking like the following:
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.
So where does Cast Iron fit into the IBM Websphere stack?Cast Iron primary used for Cloud to on-premise integration. Where you can create a message flow diagram using the Cast Iron Studio and deploy that flow to the following environments:
1. Cast Iron Appliance (which is now the Datapower XH35 Cast Iron V5.1)
http://www.castiron.com/ibm/websphere/datapower/castiron/appliance/xh35
2. The virtual Cast Iron appliance which can be installed in VMWare.
3. Amazon EC2
So how can you integrate Cast Iron with current IBM ESB’s:
1. Datapower XI50
2. Websphere Message Broker
3. WESB (Websphere ESB)
The simple answer is:
1. Websphere MQ
2. Web Services
Cast Iron integrates natively to Websphere MQ and any Web Services call can be made. This is a great addition to the IBM Stack and will be a great solution for customers that want to do any cloud integration.
Configure WebSphere DataPower SOA Appliance and WebSphere Application Server to implement WS-Policy for SOA service governance. User credentials are transformed in an LPTA common token format for authorization and single-sign-on between DataPower and an application hosted on WebSphere Application Server. Offloading policy management to DataPower lets WebSphere Application Server provide better application-level functionality, while DataPower provides enterprise-wide, high-performance service governance.
http://www.ibm.com/developerworks/websphere/library/techarticles/0911_rasmussen/0911_rasmussen.html
The Service Integration Bus can be used as a backbone for enterprise messaging, a key component to Service-Oriented Architecture. This article shows how IBM® WebSphere® Application Server V6 makes it easy to build message buses and deploy applications, and how IBM Rational® Application Developer enables developers to create and test JMS applications that communicate using the message bus.
http://www.ibm.com/developerworks/websphere/library/techarticles/0504_barcia/0504_barcia.html
The Web Services Description Language has a lot of versatility in its methods of use. In particular, WSDL can work with UDDI registries in several different ways depending upon the application needs. In this first of a three-part series, we will look at these different methods of using WSDL with UDDI registries.
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:
Below is a good graphical view of the SOA approach to Web Services. For all of these blocks there is IBM Software to successfully implement a Web Service solution.
1. Create WSDL – Rational Application Developer
2. UDDI – Websphere Application Server
3. Web Service Registry – Websphere Registry and Repository
Thys Michels Blog 