IMS Mobile Solution Getting Started

Transcription

1 IMS Mobile Solution Getting Started

2 Outline A graphic view of the IMS mobile solution and the components involved Installation options: Option 1. You already have WAS/z Liberty Profile V or later Option 2. You do not have WAS/z Liberty Profile Two security configuration scenarios: Scenario 1. Basic authentication for a quick installation verification Scenario 2. RACF security Installation walkthroughs with the following scenarios: Scenario 1. You already have WAS/z Liberty Profile 1a. You want to use basic authentication for a quick installation verification 1b. You want to use RACF security. Scenario 2. You do not have WAS/z Liberty Profile 2a. You want to use basic authentication for a quick installation verification 2b. You want to use RACF security. 2

3 IMS Mobile Solution: A graphical view Mobile applications Web browser / REST client JSON HTTP WebSphere Application Server for z/os Liberty Profile z/os Connect IMS Mobile Feature Pack TCP/IP IMS Connect O T M A IMS Transaction Manager IMS IMS IMS application IMS DB DB2 WebSphere Application Server for z/os Liberty Profile (WAS/z Liberty): The application server z/os Connect: A feature for WAS/z Liberty that serves as the gateway for discovering and invoking applications and data on z/os from mobile, cloud, and web applications. In the context of IMS mobile solution, this is the IMS gateway. IMS Mobile Feature Pack: A service provider for WAS/z Liberty that handles: Data transformation (XML <-> byte array) Interaction with IMS Connect Service management through IMS Explorer for Development, which provides the user interface for service creation, testing, and management 3

4 IMS Mobile Solution: Tooling for IMS mobile service creation, testing, and management Mobile applications Web browser / REST client JSON HTTP WebSphere Liberty Profile z/os Connect IMS Mobile Feature Pack TCP/IP IMS Connect O T M A IMS Transaction Manager IMS IMS IMS application IMS DB DB2 IMSEnterpriseSuiteExplorer for Development (IMS Explorer) Eclipse-based tool on Windows for IMS mobile service creation, testing, and management A component in IMS Enterprise Suite V3.1 that you can download 4

5 Mobile service creation, testing, and deployment tool-- IMS Explorer for Development installation IMS Explorer Do you already have IBM Installation Manager installed? Yes Download IMS Explorer (a.zip file) from the IMS Enterprise Suite download website. Launch IBM Installation Manager. Add a repository to point to where the IMS Explorer.zip file is stored No Download IBM Explorer for z/os and IBM Installation Manager from the IBM Explorer for z/os website. Extract and run the Launchpad.exe file to install both IBM Installation Manager and IBM Explorer for z/os. Click Check for Other Versions, Fixes, and Extension. 4. Click Install in the main window. 4. Select IMS Explorer from the Install Packages window. For installation information, see: 5

6 IMS Explorer: Getting started task launcher for IMS Mobile Click Start > All Programs > IBM Explorer for z/os > IMS Enterprise Suite Explorer for Development to launch IMS Explorer Getting started tasks are provided in the Task Launcher 6

7 Server runtime component installation options Installation option 1: You already have WAS/z Liberty Profile V or later Download from the WAS/z Liberty Profile repository the following required feature: IMS Mobile Feature Pack Repository location: Installation instructions are provided on the repository page. Installation option 2: You do not have WAS/z Liberty Profile Order IMS Enterprise Suite V3.1.1 (5655-TDA) from Shopz at ibm.com/software/shopzseries/ShopzSeries_public.wss. The IMS Mobile Feature Pack in IMS Enterprise Suite contains WAS/z Liberty Profile and z/os Connect as a supporting program. For WAS/z Liberty Profile usage restrictions in this context, see the license information included in IMS Enterprise Suite for z/os V

8 Installation option 1: You already have WAS/z Liberty Profile V or later 8

9 Installation option 1: You already have WAS/z Liberty Profile V or later Go to WAS/z Liberty Profile repository at Search for the IMS Mobile Feature Pack feature. Follow the instructions on the screen to install. WAS/z Liberty Profile z/os Connect IMS Mobile Feature Pack 3. Configure IMS Mobile Feature Pack. (more detail ) server.xml: See installation roadmap at: 9

10 Installation steps for option 1: You already have WAS/z Liberty Profile V or later 3. Configure IMS Mobile Feature Pack. In server.xml, add the following entries: Registry home: Location for the IMS gateway server registry. Technical ID: The technical ID is passed to the IMS Mobile feature on the gateway server if authentication is turned off, or the authenticated user ID is greater than 8 bytes. Technical group: An 8-byte SAF group name for IMS transactions. WAS/z Liberty Profile z/os Connect IMS Mobile Feature Pack server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user"/> See IMS Mobile Feature Pack security process flow at: See installation roadmap at: 10

11 Installation option 1: You already have WAS/z Liberty Profile V or later 3. Configure IMS Mobile Feature Pack. 4. Configure IMS Mobile Feature Pack for security. Security scenario 1. Basic authentication (for initial installation verification) In server.xml: a. Configure a basic registry with z/os Connect access roles in server.xml. b. If RACF is enabled in IMS Connect, specify the IMS technical password. Security scenario 2. SAF security a. Edit the BBGZANGL procedure as a started task to start the angel process. b. Start the angel process by issuing: START BBGZANGL c. If RACF is enabled in IMS Connect, specify the IMS technical password. WAS/z Liberty Profile z/os Connect IMS Mobile Feature Pack server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user"/> (more detail on next slide) (go to slide #16) See installation roadmap at: 11

12 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 1: Basic authentication 4. Configure IMS Mobile Feature Pack with basic authentication. a. Configure a basic registry with z/os Connect access roles in server.xml. Certification Configuration Basic Registry Configuration User Authorization Configuration server.xml: <keystore id= keystore_id" password= encrypted_pwd"/> <basicregistry id="basic1" realm="zosconnect"> <user name= your_username" password= your_pwd" /> </basicregistry> <authorization-roles id="zos.connect.access.roles"> <security-role name="zosconnectaccess"> <user name= user1"/> <user name= user2"/> </security-role> </authorization-roles> See installation WebSphere Liberty security configuration topics at:

13 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 1: Basic authentication 4. Configure IMS Mobile Feature Pack with basic authentication. a. Configure a basic registry with z/os Connect access roles in server.xml. b. If RACF is enabled in IMS Connect, specify the IMS technical password. This password is used for RACF authentication. Only one IMS technical password can be specified per IMS gateway server instance. This password must be set up in RACF for the user ID or IDs that are associated with the mobile service requests. server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user imstechnicalpassword="{xor}pjmzbiw7kje=" /> 13

14 Technical ID and technical password Technical ID: If SAF authentication turned off on WAS/z Liberty Profile, or if the authenticated user ID from the mobile client is greater than 8 bytes, this technical ID is passed to IMS Connect as the user ID. If the technical ID is left blank, the IMS Mobile feature uses the z/os Connect started job user ID Technical password: The password is used for RACF authentication if RACF is turned on in IMS Connect. Only one IMS technical password can be specified per IMS gateway server instance. This password must be set up in RACF for the user IDs (or the technical ID) that are associated with the mobile service requests. server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user imstechnicalpassword="{xor}pjmzbiw7kje=" /> 14

15 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 1: Basic authentication 4. Configure IMS Mobile Feature Pack with basic authentication. a. b. Configure a basic registry with z/os Connect access roles in server.xml. If RACF is enabled in IMS Connect, specify the IMS technical password. WAS/z Liberty Profile 5. Start the server by issuing: START BBGZSRV z/os Connect IMS Mobile Feature Pack GMOIG7777I: The IMS Mobile feature initialized successfully. (build_number): CWWKF0011I: The server imsmobile is ready to run a smarter planet. CWWKT0016I: Web application available (default_host): 15

16 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 2: SAF authentication and authorization 4. Configure IMS Mobile Feature Pack with SAF security. a. Edit the server.xml file to configure for SAF security if this is not yet configured. SAF Registry Configuration Certification Configuration server.xml: <safregistry id= saf_reg_id" realm="zosconnect"></safregistry> <safauthorization id= saf_id /> <safcredentials profileprefix= saf_cred_prefix"/> <keystore id= keystore_id" password= keystore_pwd"/>... See IMS Mobile Feature Pack security process flow at: For more information about security configuration for z/os Connect, see: 16

17 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 2: SAF authentication and authorization 4. Configure IMS Mobile Feature Pack with SAF security. RACF registrations for angel process a. Edit the server.xml file to configure for SAF security if this is not yet configured. b. Set up the angel process. An angel process grants the Liberty profile server access to z/os authorized services for System Authorization Facility (SAF) authorization, Workload Manager (WLM), resource recovery services (RRS), and SVCDUMP. RDEF SERVER BBG.ANGEL UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM.SAFCRED UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM.ZOSWLM UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM.TXRRS UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM.ZOSDUMP UACC(NONE) RACF registrations for SAF authorization RDEFINE SERVER BBG.SECPFX.BBGZDFLT UACC(READ) RDEFINE APPL BBGZDFLT UACC(NONE) PERMIT BBGZDFLT ID(SGEN3) ACCESS(READ) CLASS(APPL) c. In the STARTED profile for the angel process and SERVER profile, create an authenticated user; add an unauthenticated user for READ access. RDEFINE EJBROLE BBGZDFLT.zos.connect.access.roles.zosConnectAccess UACC(NONE) PERMIT BBGZDFLT.zos.connect.access.roles.zosConnectAccess CLASS(EJBROLE) ID(SGEN3) ACCESS(READ) See the Liberty profile on z/os server administration topic at: For more information about authorizing access to administrative roles, see: 17

18 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 2: SAF authentication and authorization 4. Configure IMS Mobile Feature Pack with SAF security. a. b. c. Edit the server.xml file to configure for SAF security if this is not yet configured. Set up the angel process. In the STARTED profile for the angel process and SERVER profile, create with an authenticated user; add an unauthenticated user for READ access. d. START the angel process: a. Edit the BBGZANGL procedure to start the angel process if you have not done so already. b. Start the angel process by issuing: START BBGZANGL See the Liberty profile on z/os server administration topic at: 18

19 Installation option 1: You already have WAS/z Liberty Profile V or later Security scenario 2: SAF authentication and authorization 4. Configure IMS Mobile Feature Pack with SAF security. 5. Start the IMS gateway server by issuing: START BBGZSRV GMOIG7777I: The IMS Mobile feature initialized successfully. (build_number): CWWKF0011I: The server imsmobile is ready to run a smarter planet. CWWKT0016I: Web application available (default_host): 19

20 Installation option 2: You do not have WAS/z Liberty Profile 20

21 Installation option 2: You do not have WAS/z Liberty Profile Prerequisites: 1. Order IMS Enterprise Suite V3.1 (5655-TDA) from Shopz. You will receive the following FMIDs that you need for the IMS mobile solution: Base Services (FMID HAHF310) IMS Mobile Feature Pack (FMID JAHF31A) IBM Installation Manager for z/os (FMID HGIN140) 2. Install IBM Installation Manager for z/os by following the steps in Program Directory for IBM Installation Manager for z/os. SMP/E process the FMID HGIN140. Check for and apply the latest PTFs for Installation Manager for z/os to upgrade to V1.5.3 or later. Follow the Activating IBM Installation Manager for z/os section in the IBM Installation Manager Program Directory and the instructions in the installation JCL jobs to complete the installation. 21

22 Installation option 2: You do not have WAS/z Liberty Profile 1. Follow the installation instructions in the Program Directory (GI ) to install IMS Mobile Feature Pack. a. b. Use SMP/E process to put all code onto the target system. Edit GMOIMCFS to create and mount the file system. Edit and submit GMORECV#, GMOALLOC, GMOZFS, GMODDEF4. GMOAPPLY, GMOACCEP. Create and mount the file system for installing the run-time code for IMS Mobile Feature Pack. 22

23 Installation option 2: You do not have WAS/z Liberty Profile 1. Follow the installation instructions in the Program Directory (GI ). a. b. c. Use SMP/E process to put all code onto the target system. Edit GMOIMCFS to create and mount the file system. Edit GMOIMINS to install IMS Mobile Feature Pack using IBM Installation Manager for z/os. Specify the installation directory and repository location for use by IBM Installation Manager. Specify registry home, technical ID, and technical group for use by the IMS mobile solution. Submit the job to install. GMOIMINS Registry home: Location for the IMS gateway server registry. Technical ID: The technical ID is passed to the IMS Mobile feature on the gateway server if the authenticated user ID is greater than 8 bytes. Technical group: An 8-byte SAF group name for IMS transactions. server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user"/> See installation roadmap at: 23

24 Installation option 2: You do not have WAS/z Liberty Profile 1. Follow the installation instructions in the Program Directory (GI ). a. Use SMP/E process to put all code onto the target system. IMS Mobile Feature Pack b. c. Edit GMOIMCFS to create and mount the file system. Edit GMOIMINS to install IMS Mobile Feature Pack using IBM Installation Manager for z/os. Specify the installation directory and repository location for use by IBM Installation Manager. Specify registry home, technical ID, and technical group for use by the IMS mobile solution. Submit the job to install. GMOIMINS WAS/z Liberty Profile z/os Connect server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry 2. Modify server.xml to specify the server host name and port numbers. imstechnicalgroup="ims_group" imstechnicalid="ims_user"/> <httpendpoint host="*" httpport="10443" httpsport="9443" id="defaulthttpendpoint"/> See installation roadmap at: 24

25 Installation option 2: You do not have WAS/z Liberty Profile Modify server.xml to specify the server host name and port numbers. Edit the server.xml file to configure for security. IMS Mobile Feature Pack WAS/z Liberty Profile Security scenario 1. Basic authentication (for initial installation verification) In server.xml: a. Configure a basic registry with z/os Connect access roles in server.xml. b. If RACF is enabled in IMS Connect, specify the IMS technical password. Security scenario 2. SAF security a. In server.xml, configure SAF registry. b. Set up the angel process by editing and running: GMOEXTAT job GMOZANGL procedure c. Configure SAF for the IMS gateway server. z/os Connect server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user"/> <httpendpoint host= my.host.com" httpport="10443" httpsport="9443" id="defaulthttpendpoint"/> (more detail on next slide) (go to slide #30) See installation roadmap at: 25

26 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 1: Basic authentication 3. Edit the server.xml file to configure for basic authentication. a. Configure a basic registry with z/os Connect access roles. Certification Configuration Basic Registry Configuration User Authorization Configuration server.xml: <keystore id= keystore_id" password= encrypted_pwd"/> <basicregistry id="basic1" realm="zosconnect"> <user name= your_username" password= your_pwd" /> </basicregistry> <authorization-roles id="zos.connect.access.roles"> <security-role name="zosconnectaccess"> <user name= user1"/> <user name= user2"/> </security-role> </authorization-roles> See installation WebSphere Liberty security configuration topics at:

27 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 1: Basic authentication 3. Edit the server.xml file to configure for basic authentication. a. Configure a basic registry with z/os Connect access roles. b. If RACF security is enabled in IMS Connect, configure the IMS technical password. This password is used for RACF authentication. Only one IMS technical password can be specified per IMS gateway server instance. This password must be set up in RACF for the user ID or IDs that are associated with the mobile service requests. server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user imstechnicalpassword="{xor}pjmzbiw7kje=" /> See IMS Mobile Feature Pack security process flow at: See installation roadmap at: 27

28 Technical ID and technical password Technical ID: If SAF authentication is turned off on the IMS gateway server, or if the authenticated user ID is greater than 8 bytes, the technical ID is passed to IMS Connect as the user ID. If the technical ID is left blank, the user ID that started the IMS gateway server is used. Technical password: The password is used for RACF authentication if RACF is turned on in IMS Connect. Only one IMS technical password can be specified per IMS gateway server instance. This password must be set up in RACF for the user IDs (or the technical ID) that are associated with the mobile service requests. server.xml: <imsmobile_imsservicemanager imsregistryhome="./registry imstechnicalgroup="ims_group" imstechnicalid="ims_user imstechnicalpassword="{xor}pjmzbiw7kje=" /> 28

29 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 1: Basic authentication 3. Edit the server.xml file to configure for basic authentication. 4. Start the IMS gateway server by issuing: START GMOZSRV SYSLOG NC TESTMVS :18:40.31 SGEN S GMOZSRV N TESTMVS :18:40.35 STC $HASP100 GMOZSRV ON STCINRDR N TESTMVS :18:40.39 STC IEF695I START GMOZSRV WITH JOBNAME GMOZSRV IS ASSIGNED TO USER STC S, GROUP SYSPROC N TESTMVS :18:40.39 STC $HASP373 GMOZSRV STARTED N TESTMVS :18:40.39 STC IEF403I GMOZSRV - STARTED - TIME= N TESTMVS :19:12.02 STC GMOIG7777I: The IMS Mobile feature initialized successfully. (build_numb S er): N TESTMVS :19:13.28 STC CWWKF0011I: The server imsmobile is ready to run a smarter planet. JOBLOG (STDOUT) Launching imsmobile (WebSphere Application Server , WAS FOR Z/OS /wlp cl ) on IBM J9 VM, version Launching pmz6470sr6fp _01 (SR6 FP1) (en_us) [AUDIT ] CWWKE0001I: The server imsmobile has been launched. [AUDIT ] CWWKG0028A: Processing included configuration resource: See installation roadmap at: /usr/lpp/ims/imses/v3r1/rest_gw/imsmobile/usr/servers/imsmobile/ims-services.xml [AUDIT ] CWWKZ0058I: Monitoring dropins for applications. [AUDIT ] GMOIG7777I: The IMS Mobile feature initialized successfully. (build_number): [AUDIT ] CWWKF0015I: The server has the following interim fixes installed: PI16677,PI18279,PI [AUDIT ] CWWKF0011I: The server imsmobile is ready to run a smarter planet. [AUDIT ] CWWKT0016I: Web application available (default_host): 29

30 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization 3. Edit the server.xml file to configure for SAF security. SAF Registry Configuration Certification Configuration server.xml: <safregistry id= saf_reg_id" realm="zosconnect"></safregistry> <safauthorization id= saf_id /> <safcredentials profileprefix= saf_cred_prefix"/> <keystore id= keystore_id" password= keystore_pwd"/>... For more information about security configuration for z/os Connect, see: 30

31 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization 3. Edit the server.xml file to configure for SAF security. 4. Set up an angel process. An angel process grants the Liberty profile server access to z/os authorized services for System Authorization Facility (SAF) authorization, Workload Manager (WLM), resource recovery services (RRS), and SVCDUMP. a. Create the STARTED profile for the angel process and SERVER profile with an authenticated user; add an unauthenticated user for READ access. RACF registrations for angel process RDEF SERVER BBG.ANGEL UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM UACC(NONE) RDEF SERVER BBG.AUTHMOD.BBGZSAFM.SAFCRED UACC(NONE) RACF registrations for SAF authorization RDEFINE SERVER BBG.SECPFX.GMOZDFLT UACC(READ) RDEFINE APPL GMOZDFLT UACC(NONE) PERMIT GMOZDFLT ID(SGEN3) ACCESS(READ) CLASS(APPL) RDEFINE EJBROLE GMOZDFLT.zos.connect.access.roles.zosConnectAccess UACC(NONE) PERMIT GMOZDFLT.zos.connect.access.roles.zosConnectAccess CLASS(EJBROLE) ID(SGEN3) ACCESS(READ) For a sample JCL to create the STARTED and SERVER profiles with an authenticated user for the angel process, see: For more background information about authorizing access to administrative roles, see: 31

32 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization 3. Edit the server.xml file to configure for SAF security. 4. Set up an angel process. a. b. Create the STARTED profile for the angel process and SERVER profile with an authenticated user; add an unauthenticated user for READ access. Edit and run the GMOEXTAT job to add the extended attribute (p) for files before starting the angel process. //**************************************************************/ //* PROC NAME: GMOEXTAT */ //* GMOZSRV VERSION: */ //* */ //* DESCRIPTION: THIS SAMPLE JCL ADDS THE ATTRIBUTE P TO */ //* FILES AS A REQUIREMENT TO BRING UP ANGLE */ //* SERVER */ //* */ //* NOTES: */ //* 1) CHANGE THE JOB CARD TO MEET YOUR SYSTEM'S REQUIREMENTS. */ //* 2) CHANGE -PathPrefix1- TO THE LOCATION WHERE IMS MOBILE */ //* IS INSTALLED(IT ENDS WITH rest_gw) */ //* 3) CHANGE -PathPrefix2- TO THE LOCATION WHERE JAVA IS */ //* INSTALLED(IT ENDS WITH SR7) */ //* 4) USER MUST HAVE AT LEAST READ ACCESS TO THE FOLLOWING */ //* CLASS FACILITY: */ //* BPX.FILEATTR.APF */ //* BPX.FILEATTR.PROGCTL */ //* 5) USER MUST HAVE WRITE PERMISSION TO THE DIRECTORY WHERE */ //* OUTPUT IS WRITTEN(IT IS /tmp IN THIS CASE) */ //* */ //**************************************************************/ For more information about SAF configuration for IMS mobile solution, see: For more information about extended attributes, see: 32

33 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization Edit the server.xml file to configure for SAF security. Set up an angel process. a. b. c. //**************************************************************/ //* */ //* PROC NAME: GMOZANGL */ //* GMOZSRV VERSION: */ //* */ Create the STARTED profile for the angel process and //* DESCRIPTION: THIS PROC STARTS THE LIBERTY ANGLE PROCESS */ SERVER profile with an authenticated user; add an //* */ //* NOTE: */ unauthenticated user for READ access. //* */ //* CHANGE ROOT TO THE WLP DIRECTORY THAT IS LOCATED IN */ Edit and run the GMOEXTAT job to add the extended //* THE IMS MOBILE INSTALLATION DIRECTORY */ attribute (p) for files before starting the angel process. Edit the GMOZANGL procedure for the angel process. //* */ //* YOU NEED TO RUN THE SAMPLE JCL GMOEXTAT BEFORE STARTING */ //* THIS PROC */ //* */ //**************************************************************/ //GMOZANGL PROC PARMS='',COLD=N //* // SET ROOT='/usr/lpp/ims/imses/V3R1/rest_gw/wlp' //* //* Start the Liberty angel process //* //STEP1 EXEC PGM=BPXBATA2,REGION=0M, // PARM='PGM &ROOT./lib/native/zos/s390x/bbgzangl COLD=&COLD &PARMS' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //* ================================================================ */ For more information about enabling z/os authorized services on Liberty profile on z/os, see: 33

34 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization Edit the server.xml file to configure for SAF security. Set up an angel process. a. b. c. Create the STARTED profile for the angel process and SERVER profile with an authenticated user; add an unauthenticated user for READ access. Edit and run the GMOEXTAT job to add the extended attribute (p) for files before starting the angel process. Edit the GMOZANGL procedure for the angel process. d. Start the angel process by issuing: START GMOZANGL For more information about enabling z/os authorized services on Liberty profile on z/os, see: For more background information about WAS/z security, see: 34

35 Installation option 2: You do not have WAS/z Liberty Profile Security scenario 2: SAF authentication and authorization Edit the server.xml file to configure for SAF security. Set up an angel process. a. b. Create the STARTED profile for the angel process and SERVER profile with an authenticated user; add an unauthenticated user for READ access. Edit and run the GMOEXTAT job to add the extended attribute (p) for files before starting the angel process. 5. c. d. Edit the GMOZANGL procedure for the angel process. Start the angel process by issuing: START GMOZANGL Start the IMS gateway server by issuing: START GMOZSRV GMOIG7777I: The IMS Mobile feature initialized successfully. (build_number): CWWKF0011I: The server imsmobile is ready to run a smarter planet. CWWKT0016I: Web application available (default_host): For more information about SAF configuration for the IMS mobile solution, see: 35

36 Verifying installation Use the HTTP PUT method to invoke the IMSPingService service: invoke { message: "The ping request for the IMS gateway server was successful." } 36

37 Communicating to IMS To test the communication with IMS: 1. Turn off IMS Connect RACF security (RACF=N). IMS Mobile is considered a trusted client to IMS Connect because authentication and authorization are handled by WAS/z Liberty Profile and z/os Connect. 2. Use the HTTP PUT method to invoke the IMSPingService service and specify the host name, port number, and the IMS data store name: invoke&hostname=my.ims.host.com&port=9999&datastore=ims1 { message: "The ping request for the IMS gateway server was successful." pingtestresults: "Ping request for HOSTNAME: my.ims.host.com, PORT: 9999, DATASTORE: IMS1 was successful" } 37

38 What s next? Creating, testing, and publishing IMS mobile services Use IMS Explorer for Development Accessing and managing services Use the supported HTTP actions to: Start, stop, and invoke a service Obtain service status, statistics, JSON schema, and configuration information Check for available services Obtain IMS mobile service provider statistics For an end-to-end tutorial that turns the IMS phonebook application into a Contacts mobile application, see IMS Exchange: 38

39