IMS Enterprise Suite Version 2.1 SOAP: Enabling an IMS application as a web service provider with SAML signed assertion

Product documentation


Abstract

This end-to-end sample demonstrates how to enable an IMS™ application as a web service with WS-Security SAML 1.1 signed assertion, and how to create a client application that sends messages through secure HTTPS communications to the IMS Phonebook web service that is deployed on the SOAP Gateway server.

Content

You can enable the web services security (WS-Security) feature to ensure that the security credentials of the client application is validated each time a message is submitted.

This sample uses the IMS Phonebook sample application (IVTNO) to demonstrate how to enable WS-Security SAML 1.1 signed assertion and how to create a client application that sends messages via secure HTTPS communication (client authentication) to the IMS Phonebook web service that is deployed on the SOAP Gateway server.

Requirements

  • IMS Enterprise Suite Version 2.1 SOAP Gateway
  • IMS Version 11 or Version 12 with integrated IMS Connect
  • The IMS Phonebook sample application files (included in this sample)
  • Optional: IBM® Rational® Developer for System z® Version 8.0.2 or later

Contents of the attached sample zip file

The attached zip file includes the COBOL copybook for the Phonebook sample application to be enabled as a web service. The zip file also includes the generated files from Rational Developer for System z for your reference in case you do not have access to Rational Developer for System z Version 8.0.2 or later.

File name
Description
The client\ folder contains the client binding and policy files
bindings.xml and policy.xml Client binding and policy files
The genericArtifacts folder
The Phonebook copybook and files generated by Rational Developer for System z
IMSPHBK.cpy The IMS Phonebook application copybook
IMSPHBK.wsdl The WSDL file
IMSPHBK.xml The correlator file
IMSPHBKD.cbl The XML converters file
The ADB\ and the XMLBeans\ folders
Files you need for either the ADB approach or XMLBeans approach for generating the client applications. In each folder, files specific for Windows and for z/OS® are separated into the Windows\ and zOS\ folders.
a) Windows batch files, one set each for the ADB approach and the XMLBeans approach
wsdl2java_ADB.bat wsdl2java_XMLBEANS.bat Windows batch files to generate the client proxy code
ant.bat Windows batch file to compile the source file
setpath.bat and setclasspath.bat Windows batch files to set the Java™ path and classpath
runjava_ADB.bat runjava_XMLBEANS.bat Windows batch file to run the Java client
IMSPHBKServiceStub.java in the subdirectory Sample stub file
b) z/OS shell script files, one set each for the ADB approach and the XMLBeans approach
wsdl2java_ADB.sh wsdl2java_XMLBEANS.sh z/OS shell script files to generate the client proxy code
antCompile.sh z/OS shell script file to compile the source file
setpath.sh and setclasspath.sh z/OS shell script files to set the Java path and classpath
runjava_ADB.sh runjava_XMLBEANS.sh z/OS shell script file to run the Java client
IMSPHBK_ADB_Security.java IMSPHBK_XMLBEANS_Security.java Sample Java client applications
IMSPHBKServiceStub.java in the subdirectory Sample stub file
Additional files
SAMLIssuerConfig.properties Configuration file for keystore information for signing the SAML
saml-provider.jceks SAML keystore file
Documentation
IMSEnterpriseSuite21SAMLSignedAssertion.pdf The instructions

IMSEnterpriseSute21SAMLSignedAssertion.zip

Rate this page:

(0 users)Average rating

Document information


More support for:

IMS Enterprise Suite
SOAP Gateway

Software version:

2.1

Operating system(s):

Linux on System z, Windows, z/OS

Reference #:

7023326

Modified date:

2011-10-31

Translate my page

Machine Translation

Content navigation