Enable an IMS application as a Web service

running in IMS SOAP Gateway

Abstract
This tutorial takes you through a series of intensive hands-on exercises to transform an Information
Management System (IMS) application to a We service y using I!M" #ational" $eveloper
for System % and IMS S&'( )ate*ay+
About this tutorial
This tutorial takes you through a series of intensive hands-on exercises designed to transform an
IMS application to a We service y using I!M" #ational" $eveloper for System % and IMS
S&'( )ate*ay+ IMS S&'( )ate*ay is a We service solution that integrates IMS assets in a
service-oriented architecture (S&') environment+ It enales IMS applications as We services
through easy deployment and configuration processes+ The IMS S&'( )ate*ay solution integrates
*ith the IMS ,onnect -M. adapter function/ *hich provides -M. conversion support+ This
enales users to send and receive -M. data *ithout modification of existing IMS applications+
Through the tooling in #ational $eveloper for System %/ We service artifacts can e easily
generated+ 'rtifacts include a We Services $escription .anguage (WS$.) file/ the correlator file/
and the -M. converter+ #ational $eveloper for System % generates the -M. converter from
,&!&. copyooks to e used y the IMS ,onnect -M. adapter+ The IMS S&'( )ate*ay
deployment utility completes the ackend IMS connection configurations+ IMS S&'( )ate*ay runs
on multiple platforms/ including %0&S (IMS S&'( )ate*ay 123+2)/ Microsoft "Windo*s" -(/
Microsoft Windo*s 4333/ I!M" 'I-"/ and %.inux"+
Objectives
To help you understand and gain hands-on experience in extending IMS applications to the We as a
part of We services+ This tutorial demonstrates ho* using #ational $eveloper for System % and the
S&'( )ate*ay utility makes the transformation processes easy+ 5pon completion of this tutorial/
you *ill e ale to6
5se #ational $eveloper for System %+
5se the IMS S&'( )ate*ay deployment utility to deploy an IMS application as a We
service+
1 of 23
System requirements
Soft*are installed on the Microsoft Windo*s operating system6
IMS S&'( )ate*ay 1ersion 23+2 *ith the latest i7ix
#ational $eveloper for System % 1ersion 8+9
System soft*are installed on I!M" %0&S"
IMS 1ersion 23
IMS ,onnect 1ersion 23 *ith -M. 'dapter configured
IMS &TM'
T,(0I(
Overview o !evelopment tas"s
Internet Management Specification (IMS) applications can be enabled as Web services running in an IMS
SOAP ate!a" !it#out t#e need for a full$fledged application server% suc# as I&M' WebSp#ere' Application
Server( )ifferent t"pes of client applications% suc# as Microsoft' (*+,% -ava% and t#ird$part" applications% can
send SOAP re.uests into IMS to drive t#e business logic of "our IMS applications(
,#is tutorial uses t#e IMS p#oneboo/ application (I0,*O) as an e1ample to demonstrate #o! to ma/e it
accessible as a Web service( ,#e client application (a -ava2 application) for accessing t#e Web service is
provided #ere(
,o complete t#is tutorial% "ou !ill go t#roug# t#e steps of enabling an IMS application as a Web service b"
using I&M 3ational )eveloper for S"stem 4 to generate t#e necessar" artifacts and t#en complete t#e
deplo"ment processes b" using t#e IMS SOAP ate!a" utilit"(
,o complete t#is tutorial% "ou !ill perform t#e follo!ing five tas/s5
1( Generate the artiacts by using #ational $eveloper or System % (see t#e diagram in 6igure 1)(
A( Import t#e 7O&O8 cop"boo/(
&( Specif" t#e input and output data structure(
7( Set t#e IMS SOAP ate!a" #ost name and port number(
)( Set t#e IMS transaction code and connection information(
+( Specif" t#e converter names(
Figure 1. Input and output when using Rational Developer for System z
2( &ranser the generate! 'M( converter to I)M %*OS+ 7ompile and lin/ t#e converter for t#e IMS
7onnect 9M8 adapter (6igure 2)(
2 of 23
,igure -+ $eploying the 'M( converter to IMS .onnect
3( Enable the IMS application as a Web service+ )eplo" t#e generated WS)8 file and configuring t#e
correlation properties b" using t#e IMS SOAP ate!a" 01:(1 )eplo"ment ;tilit" (6igure 3)(
A( Provide t#e WS)8 file t#at is generated b" 3ational )eveloper for S"stem 4(
Set t#e connection information to connect to IMS(
Set t#e IMS 7onnect #ost name and port number(
&( Set t#e IMS data store name (IMS I))(
7( Provide t#e correlator file pat#(
,igure /+ $eploy the correlator ile an! WS$( ile by using the IMS SOAP Gateway !eployment utility
<( $eploy a client application to access the IMS Phone)oo" Web service+ Write or modif" an
e1isting -ava application to access t#e IMS application t#at #as been deplo"ed as a Web service(
0+ Invo"e the 1ava application that accesses the IMS application+
3 of 23
&as" 2+ Generate the artiacts by using I)M #ational $eveloper
or System %
IBM Rational Developer for System z is an application development tool that helps in the development of
traditional mainframe applications. You can generate the Web service artifacts shon in !able " by using the
#nterprise Service !ools $#S!% izard provided.
Table 2. eb servi!e artifa!ts
"enerated
file
Des!ription
WSD& file !he WSD& file is the Web service interface for the IMS application. It describes
here the Web service is located and hat the input and output message format
is hen the IMS application is invo'ed.
You can create a WSD& file by hand or by using an application development tool
$such as IBM Rational Developer for System z% and then customize it to be used
ith IMS S()* +ateay.
Based on the language structures from your application, the #nterprise Service
!ools izard needs to 'no hich data structure is the input to invo'e the
application.
-M& converter
driver file
IMS .onnect has an -M& adapter function that, based on this converter driver,
transforms -M& messages from the client into .(B(& bytes for the IMS
application and then from bytes bac' to -M& for the response. !his file needs to
be deployed to IMS .onnect.
.orrelator file !his file contains information that enables the IMS S()* +ateay to set IMS
properties and call the IMS application.
Open the Enterprise Service &ools an! create an IMS SOAP Gateway project
1( ,#e I&M 3ational )eveloper for S"stem 4 0 =(> is started and "ou are using t#e
Wor/spaces=(>?SA*)&O9(
Important3
6or t#is tutorial% "ou are using C:\Workspaces7.5\SANDBOX as "our !or/ !or/space(
/. (pen the #nterprise Service !ools perspective $0igure 1%2 indow # $pen %erspe!tive # $ther.
Figure &. $pening the 'nterprise Servi!e Tools perspe!tive
The wor(spa!e
< of 23
) or'space is a directory that stores files for your pro3ects. You can select your on directory or ta'e the
default directory. )rtifacts created by Rational Developer for System z ill be stored in this directory.
1. When the (pen *erspective indo opens, select 'nterprise Servi!e Tools and then clic' $) $0igure
4%.
Figure *. The $pen %erspe!tive window for !hoosing a perspe!tive
5e6t, you ill see the #S! *ro3ect #6plorer tab $0igure 7%.
Figure +. The 'ST %ro,e!t '-plorer in Rational Developer for System z
> of 23
4. Right8clic' in the #S! *ro3ect #6plorer indo $0igure 9%, and select .ew # I/S S$0% "ateway
%ro,e!t.
Figure 1. 2reating an I/S S$0% "ateway pro,e!t
@( When the 5e IMS S()* +ateay *ro3ect izard opens $0igure :%, enter a pro3ect name $use
IMSPhoneBook for this e6ample%.
Figure 3. Spe!ifying a pro,e!t name4 development s!enario4 appli!ation mode4 and !onversion type

@ of 23
!he folloing are the default selections. #nsure that these options are selected2
Development scenario2 2reate .ew Servi!e Interfa!e 5bottom6up7
)pplication mode2 Servi!e %rovider
.onversion type2 2ompiled 8/9 2onversion
)ey terms
:ottom6up development s!enario
!he #nterprise Service !ools izard supports the creation of service interfaces for several different types of
pro3ects, one of hich is the IMS S()* +ateay. Different pro3ects support different options.
2reate .ew Servi!e Interfa!e
!his creates a bottom8up development scenario, hich is for scenarios here you already have an enterprise
application ith e6isting language structures that you ant to turn into a Web service.
Servi!e %rovider appli!ation mode
!he Service *rovider application mode means that the enterprise application serves as a Web service
provider that receives re;uests from e6ternal clients, rather than initiating an outbound re;uest to an
e6ternal Web service.
9. .lic' .e-t. ) indo opens for you to import the application source file.
)ey step;
Import the .(B(& copyboo'.
:. .lic' File System to import the .(B(& copyboo' that describes the format of the input and output
messages of your IMS application into the pro3ect that you created.
<. 5avigate to 2;<I/S %hone:oo( $0igure <%. !his directory contains the *honeBoo' .(B(& copyboo' and
other files that you ill need later.
=>. Select the I/S%=:).!py file, and clic' $pen.
Figure >. Spe!ifying the I/S appli!ation sour!e file
= of 23
==. Ma'e sure that the content of the ?Source files to import? field is pointing to the correct file $0igure =>%,
and then clic' Finish.
Figure 1?. Importing the !opyboo( from the File System
) ne pro3ect called IMS*honeBoo' is no available in your #S! *ro3ect #6plorer.
=". Right8clic' the pro3ect name, I/S%hone:oo(, in the #S! *ro3ect #6plorer and then select "enerate
I/S S$0% "ateway resour!es $0igure ==%.
Figure 11. "enerating I/S S$0% "ateway resour!es
A of 23
!he #nterprise Service !ools Wizard launches and the .reate 5e Service Interface page is displayed.
!o start, the #nterprise Service !ools izard needs to gather the host runtime, development scenario,
application mode, and -M& conversion type.
". .lic' Start to open the dialog bo6 for specifying the re;uest and response message layouts.
hat you have done so far
You have created an IMS S()* +ateay pro3ect in Rational Developer for System z by using the
#nterprise Service !ools izard. You imported the .(B(& copyboo' for the IMS phoneboo' application,
the type of pro3ect, the host runtime, the development scenario, the application mode, and the
conversion type so that the izard can proceed to gather specific data based on your selections so far.
Select !ata structures or the request an! response message converters
)ey step;
Specify the re;uest message and response message structure.
Based on the phoneboo' .(B(& copyboo', the #nterprise Service !ools needs to gather the information that
!able / shos
Table @. Information the 'nterprise Servi!e Tools wizard gathers
Information Des!ription
!he re;uest message
layout in your
application
Based on the language structures from your application, the #nterprise Service !ools izard needs to
'no hich data structure is the input $re;uest message% to invo'e the application.
!he response
message layout in
your application
Based on the language structures from your application, the #nterprise Service !ools izard needs to
'no hich data structure is the output $response messasge% from the application.
!he prefi6 for the
converter name
!he #nterprise Service !ools izard generates the converters based on the prefi6. !he izard lets users
choose to generate either separate converter files for inbound and outbound messages or one driver for
all converters. If users choose the former, the izard appends a different character to the prefi6 to create
different converter files. If users choose the latter, the izard appends a D to the prefi6.
.haracter encodings !his is the code page to use for encoding the inbound and outbound -M& messages and the code page
that is used by the z@(S host system.
!ransaction code for
your IMS application
!he transaction code is re;uired to run the IMS application.
Soc'et timeout and
e6ecution timeout
values
!he time that the IMS S()* +ateay should ait for a response from IMS .onnect and for IMS .onnect
to send a message to IMS and receive a response before a timeout.
B of 23
=/. In the .reate 5e Service Interface page, specify the layout of the re;uest and response messasges2
a. In the ReAuest 9anguage Stru!ture tab, ensure I5*A!8MS+ is listed as the language
structure for the re;uest message.
Figure 12. Spe!ifying the reAuest message layout
b. .lic' the Response 9anguage Stru!ture tab, and ensure (A!*A!8MS)+ is listed as the
language structure for the response message.
Figure 1@. Spe!ifying the outbound language stru!ture
1: of 23
=1. .lic' .e-t to display IMS message layouts $0igure =1%. Because there is only one language structure
for the re;uest message and one language structure for the response message. We do not need to
ma'e any ad3ustment or modification here. .lic' .e-t to continue to the Generation options page.
Figure 1&. I/S message layouts
11 of 23
Speciy generation options
)ey step;
Set the IMS S()* +ateay host name and port number.
=4. In the +eneration options page, under the -M& .onverters tab $for this tutorial%, ensure that the
converter program prefi6 I/S%=:) is unchanged. You can leave other default options as they are $see
0igure =4%.
Figure 1*. Spe!ifying the !onverter generation options
.ote;
You must use this IMS*BBC prefi6 for this tutorial so that you do not need to manually deploy the -M&
converters to IMS .onnect. ) converter driver ith that name is already deployed for this tutorial.
12 of 23
=7. Select the SD9 and 8SD tab.
=9. In the Service location field, change the hostname and port number to the location of IMS S()*
+ateay2 http2@@localhost2:>:>@imssoap@services@IMS*BBC*ort. !his AR& specifies the address of the
Web service.
Figure 1+. Spe!ifying the eb servi!e properties
1. .lic' .e-t to continue.
13 of 23
Speciy the IMS SOAP Gateway correlation properties
)ey step;
Set the IMS transaction code and connection information.
=:. In the IMS S()* +ateay .orrelator file tab, enter the folloing values $shon in 0igure =9%2
Transa!tion !ode; IVTNO
Inbound !onne!tion bundle; IMSPBCon
So!(et timeout; 6000
=<. Ase the default values for the other IMS .onnect interaction properties and clic' .e-t.
Figure 11. Spe!ifying I/S 2onne!t intera!tion properties
1< of 23
.otes;
!he inbound connection bundle name must match the name of the connection bundle that you ill
specify later in the IMS S()* +ateay deployment utility.
!he soc'et timeout value should be larger than the e6ecution timeout value. 0or this tutorial, 7>>>
is arbitrarily selected.
">. Ander the -M& .onverters tab $0igure =:%, use the default value for the converter driver file name. !he
inbound and outbound converter file names are automatically filled in based on the converter driver file
name.
Important;
0or this tutorial, you must use the default converter file names to use the -M& converters that are already set up
for you in IMS .onnect. !his setting ensures that the demo system can function properly for everyone.
"=. Ma'e sure that the ?+enerate all to driver? chec' bo6 is chec'ed.
"". .lic' Finish.
Figure 13. Spe!ifying 8/9 !onverters options
!he folloing files are generated in your Rational Developer for System z or'space $see 0igure =<%2
I/S%=:).wsdl; WSD& file
I/S%=:).-ml; .orrelator file
I/S%=:)D.!bl; .(B(& converters in one driver file
I/S%=:)I.-sd; Inbound -SD file $not used by the IMS S()* +ateay%
I/S%=:)$.-sd; (utbound -SD file $not used by the IMS S()* +ateay%
1> of 23
,igure 24+ &he generate! iles in the ES& Project E5plorer view
hat you have done so far
You specified the input and output data structures in the phoneboo' .(B(& copyboo', -M& conversion options,
and IMS .onnect interaction properties in the #nterprise Service !ools izard. !he izard generated the WSD&
file, the correlator file $an -M& file%, and an -M& converter driver. !hese files are located in your Rational
Developer for System z or'space.
&as" -+ &ranser the generate! 'M( converter to I)M %*OS
IMS .onnect has an -M& adapter function that converts data beteen -M& and bytes, based on a deployed
converter driver. !ypically, to deploy a converter driver, you need to complete these to tas's2
=. Ase 0!* to transfer the -M& converter driver that is generated by Rational Developer for System z to the
z@(S system.
". .ompile and lin' the -M& converter driver into a data set that is concatenated to the S!#*&IB in the IMS
.onnect startup D.& $3ob control language%.
Important;
!his IMS*BBCD.cbl converter driver is part of the sample that is included ith IMS .onnect. !herefore, no action
is needed here. You can proceed directly to tas' /2 Deploy WSD& and configure properties ith IMS S()*
+ateay.
1@ of 23
&as" /+ Enable the IMS application as a Web service
!he deployment step helps you set up properties and create runtime code that ill be used by the IMS S()*
+ateay to ma'e your IMS application accessible through a Web service.
IMS S()* +ateay provides a deployment utility that can help you perform the folloing tas's2
Deploying easily end8to8end
Setting up and modifying connection and correlation information $hostname, port number, trancode,
and timeout, for e6ample%
+enerating the runtime code from the WSD& that ill be used by IMS S()* +ateay to enable the IMS
application as a Web service
!he deployment utility can ta'e you through these tas's, or you can perform each tas' individually, either
through the interactive mode or command8line interface
)ey points;
In the IMS S()* +ateay deployment utility2
=. *rovide the WSD& file that is generated by Rational Developer for System z.
". Set the connection information to connect to IMS.
). Set the IMS .onnect host name and port number.
B. Set the IMS data store name $IMS ID%.
/. *rovide the correlator file path.
$eploy the generate! artiacts
=. .opy the WSD& file and the correlator file that ere generated by Rational Developer for System z from
the previous section into the appropriate directories. 0or this tutorial $see 0igure ">%2
o !he Rational Developer for System z or'space is this directory2.2EWor'spaces9.4ES)5DB(-
o !he WSD& file for the IMS*honeBoo' pro3ect is located in
.2EWor'spaces9.4ES)5DB(-EIMS*honeBoo'E+enerationE!argets
o !he IMS S()* +ateay installation directory is .2E*rogram 0ilesEIBMEIMS S()* +ateay F=>.=
$the default%
). .opy the I/S%=:).wsdl file from the Rational Developer for System z or'space into the
IMS S()* +ateay WSD& directory at installation_directoryEserverEebappsEimssoapEsdl. 0or this
tutorial, copy the WSD& file into .2E*rogram 0ilesEIBMEIMS S()* +ateay
F=>.=EserverEebappsEimssoapEsdl
B. .opy the correlator file $I/S%=:).-ml% from the Rational Developer for System z or'space
into the IMS S()* +ateay -M& directory at installation_directoryEserverEebappsEimssoapE6ml.
0or this tutorial, copy it into .2E*rogram 0ilesEIBMEIMS S()* +ateay
F=>.=EserverEebappsEimssoapE6ml
1= of 23
Figure 2?. The generated files in indows '-plorer view

". Start the IMS S()* +ateay. 0rom the Windos Start menu, select %rograms # I:/ I/S S$0%
"ateway Bersion 1?.1 # Start Server. You ill see a message from the console2 ?IMS S()* +ateay
server is no up and running.?
/. Start the deployment utility in the interactive mode. 0rom the Windos Start menu, select %rograms #
I:/ I/S S$0% "ateway Bersion 1?.1 # Deployment Ctility. !he deployment utility interactive
mode starts and displays the main menu shon in 0igure "=.
Figure 21. I/S S$0% "ateway Deployment Ctility
!he main menu lists the tas's that you can perform ith the deployment utility.
1A of 23
<( !ype 1 $one% and press 'nter to select !as' =2 #nable your IMS application as a Web service from start
to finish.
4. !he deployment utility then guides you through the folloing steps to complete the deployment tas'2
o Specify hich WSD& file to use for the deployment
o Specify the connection and security information for the Web service to create a connection
bundle
o Specify the interaction properties of the Web service to create a correlator file
o Deploy the Web service to IMS S()* +ateay
o .reate the Dava client pro6y code
7. #nter the values that are in code type $.ourier 5e% in the steps that follo hen you are prompted.
A( *rovide the WSD& file for deployment. *rovide the name and location of the WSD& file $for
e6ample c2EMyWSD&0ile.sdl%2 IMSPHBK.wsdl
.ote; You need to specify only the file name here, because the WSD& file as copied into the
IMS S()* +ateayGs WSD& directory. (therise, you ould need to specify the full path.
B. *rovide connection properties for connecting to IMS2
Do you ant to vie all e6isting connection bundlesH IY@5J2 n
Do you ant to create a connection bundleH IY@5J2 y
*rovide the name of the connection bundle. For this sample4 enter I/S%:2on
*rovide IMS host name or I* address. For this sample4 enter
DS'RB'R$S.DF.I:/.2$/
*rovide IMS port number$default2 <<<<%. For this sample4 enter >>>>
*rovide IMS datastore name. For this sample4 enter I/S2
*rovide IMS userid $optional%. For this sample4 press 'nter.
*rovide IMS passord $optional%. For this sample4 press 'nter.
*rovide IMS group name $optional%. For this sample4 press 'nter.
Do you ant to set SS& propertiesH IY@5J2 For this sample4 enter .
!he connection bundle, IMSPBCon, has been created.
.. *rovide interaction $correlator% properties for Web services
.ote; If you use the IBM8provided Rational Developer for zSeries solution, the correlator file is
generated for you as part of that process. If you use your on solution, you must create the
correlator file.
Do you ant to use an e6isting .orrelator fileH IY@5J2 y
*rovide the name and full path to the .orrelator file2 IMSPHBK.xml
.ote;
Eou need to spe!ify only the file name here4 be!ause the !orrelator file was
!opied into I/S S$0% "atewayFs
GinstallationHdire!tory#<server<webapps<imssoap<-ml dire!tory4 and we
have applied I/S S$0% "ateway B1? iFi- 1. $therwise4 you need to spe!ify
the full path.
Do you ant to vie the correlator fileH IY@5J2 y
.ote;
The !orrelator file is displayed. hen you are finished reviewing4 press 'nter
to !ontinue.
D. Deploy the WSD& to IMS S()* +ateay. !his step deploys the WSD& file and ma'es your IMS
application accessible as a Web service. .ote; #nsure that the IMS S()* gateay is already
started.
Do you ant to deploy the WSD& file to IMS S()* gateayH $y@n%2 y
You ill then see2
*rocessing file .2E*rogram 0ilesEIBMEIMS S()* +ateay
F=>.=EserverEebappsEimssoapEtempEserverEdeploy.sdd
WSD& as successfully deployed.
#. $(ptional% +enerate the Dava client code. !his step generates pro6y code that you can use to
build a Dava application to invo'e the Web service.
Do you ant to generate 3ava client code $optional%H IY@5J2 y
*lease enter the location to output client files Kdefault2 .2E*rogram 0ilesEIBMEIMS
S()* +ateay F=>.=EserverEebappsEimssoapEtempEclientL. %ress 'nter to use the
default.
You ill then see2 .lient code generation in directory Kthe S()* +ateay install path
entered aboveL is complete.
1B of 23
The Iava !lient pro-y !ode
!he client pro6y code is usually generated by a tool or utility and performs the folloing tas's2
=. .reates a connection to send and receive S()* messages
". Wraps the transaction data in a S()* message
!he IMS S()* +ateay Deployment Atility can generate this client pro6y code for you.
hat you have done so far
+enerated the correlator file, the WSD& file, and the -M& converter driver using Rational Developer for
System z
Deployed the -M& converter driver to IMS .onnect
Deployed the phoneboo' application using the IMS S()* +ateay Deployment Atility by specifying the
correlator file, the WSD& file, connection information for IMS, IMS .onnect host name and port number,
and IMS data store name
!he IMS phoneboo' application is no enabled as a Web service.
6eriy the !eployment o the IMS Phone)oo" Web service
Your IMS applications are ready to be accessed by a client as a Web Service. !o verify that the deployment has
completed successfully, do the folloing2
9. Start the IMS S()* +ateay Server .onsole by selecting, from the Start menu2 %rograms # I:/ I/S
S$0% "ateway B1?.1 # 0dministrative 2onsole. ) Web broser opens and displays the console.
:. .lic' the Biew deployed eb Servi!es lin'. You should see IMS*BBC*ort listed in the page, hich
indicates that the IMS phoneboo' application is successfully deployed as a Web service.
,as/ <( )eplo" a client application to access t#e Web service
)fter the IMS application is successfully deployed in the IMS S()* +ateay, you need to test hether you can
access the Web service from a client application, such as a Dava or Microsoft .5#! application. !he IMS S()*
+ateay deployment utility can help you generate the Dava pro6y code that you can use in your Dava application
$Step # in the previous section2 +enerate the Dava client code in the IMS S()* +ateay deployment utility%.
0or this e6ercise, an e6isting Dava application is provided.
$eploy the 1ava application into IMS SOAP Gateway7s webapps !irectory
=. .opy the phoneboo' directory from .2EIMS *honeBoo'.
". *aste the phoneboo' directory into the ebapps file2
.2E*rogram 0ilesEIBMEIMS S()* +ateay F=>.=EserverEebapps
5o you should have a directory that loo's li'e this2
.2E*rogram 0ilesEIBMEIMS S()* +ateay F=>.=EserverEebappsEphoneboo'
/. Stop IMS S()* +ateay. 0rom the Windos Start menu, select %rograms # I:/ I/S S$0%
"ateway B1?.1 # Stop Server.
2: of 23
,as/ >( Invo/e t#e -ava application
=. Start IMS S()* +ateay2 0rom WindosG Start menu, select *rograms L IBM IMS S()* +ateay F=>.=
L Start Server.
". &aunch Internet #6plorer.
3( +o to the folloing AR&2 http2@@localhost2:>:>@phoneboo'
!he Dava application displays the screen that 0igure "" shos.
Figure 22. Invo(ing the sample Iava appli!ation

<( #nter Smith as your in;uiry and clic' 9oo( up $see 0igure "/%.
Figure 2@. Spe!ifying a value to Auery the I/S phoneboo( appli!ation
21 of 23
!he resulting display loo's li'e 0igure "1.
Figure 2&. Juery result from the I/S phoneboo( appli!ation
Summary o complete! tas"s
You have successfully completed the folloing tas's for this tutorial $illustrated in 0igure "4%2
=. +enerated the WSD& file, correlator file, and converter driver for the IMS phoneboo' application by
using Rational Developer for System z
". Deployed the converter driver to IMS .onnect $hich as already done for you%
/. #nabled the IMS phoneboo' application as a Web service by deploying the generated WSD& and
correlator files and using IMS S()* +ateay deployment utility
Figure 2*. The overall pro!ess to enable an I/S appli!ation as a eb servi!e
1. You then deployed a provided Dava application that accessed the IMS phoneboo' application and
invo'ed the IMS phoneboo' application from the Dava application.
Eou have su!!essfully !ompleted this tutorialK
22 of 23
#esources
9earn
Fisit the Rational softare area on developerWor's for technical resources and best practices for
Rational Softare Delivery *latform products.
#6plore Rational computer8based, Web8based, and instructor8led online courses. Bone your s'ills and
learn more about Rational tools ith these courses, hich range from introductory to advanced. !he
courses on this catalog are available for purchase through computer8based training or Web8based
training. )dditionally, some ?+etting Started? courses are available free of charge.
Subscribe to the Rational #dge e8zine for articles on the concepts behind effective softare
development.
Fisit the IMS S()* +ateay product Web page.
.hec' out the Information Management IMS zone on developerWor's.
Subscribe to the IBM developerWor's nesletter, a ee'ly update on the best of developerWor's
tutorials, articles, donloads, community activities, ebcasts and events.
Brose the technology boo'store for boo's on these and other technical topics.
"et produ!ts and te!hnologies
Donload trial versions of IBM Rational softare.
Donload a trial version of IBM Rational Developer for system z.
Donload IMS S()* +ateay and to complimentary, unarrented copies of Rational Developer for
System z for IMS Fersion => customers.
Dis!uss
*articipate in the discussion forum .
.hec' out developerWor's blogs and get involved in the developerWor's community.
About the authors
7#ao$8in 8iu is a Soft!are )eveloper at I&M(
Cee$3ong 8ai is an Information )eveloper at I&M(
S#a#in Mo#ammadi$3as#edi is an IMS SOA )emonstration ,eam 8ead at I&M
23 of 23