The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Feeding iPhone applications with WebSphere Process Server V6.2 services

Chris Felix (chrisfel@ca.ibm.com), Software Engineer, IBM

Chris Felix is a Software Developer and Agile ScrumMaster in the IBM Software Services for WebSphere organization at the IBM Toronto Lab, Canada. He is experienced in developing Web 2.0 applications that leverage Web services provided through WebSphere Process Server. He was recently engaged in a project that required a mobile front end, allowing him to gain experience in iPhone development.

Summary: This tutorial shows you how to extend new and existing services in WebSphere® Integration Developer V6.2 to use the new JSON over HTTP binding export, so that you can expose services to Web 2.0 and mobile clients that consume JSON. You will create a simple Apple® iPhone® application that will consume such a service. Integration developers will learn how to expose services to an iPhone developer, while iPhone developers can learn how to create Objective-C clients to consume those services.

Date: 27 Jan 2010
Level: Intermediate
PDF: A4 and Letter (514 KB | 23 pages)Get Adobe® Reader®

Activity: 43847 views
Comments:

Before you start

The application will demonstrate an example of an Apple iPhone to WebSphere Process Server (hereafter called Process Server) interaction using the JSON over HTTP binding export available in Version 6.2. However, you can apply the same principles to connect another client to Process Server. Imagine that company ABC currently provides an internal service that allows applications to look up the contact information of employees. The service (OrganizationInterface) is hosted on WebSphere Process Server V6.2, and currently only has a Web service (XML over SOAP) export. Since many of ABC’s employees are mobile, the company has asked its development team to create an iPhone application to provide this service.

Objectives

Learn how to:

Extend existing WebSphere Integration Developer V6.2 services to include the new JSON over HTTP binding export.
Create an Objective-C service proxy for the JSON over HTTP binding export.

Prerequisites

The following tutorial targets two types of development resources:

A WebSphere Process Server integration developer.
An iPhone application developer.

Integration developer role

Familiar with using WebSphere Integration Developer V6.2 to create integration modules.
Imported the following workspace provided in the Incomplete_iPhoneServicesModule.zip file.

iPhone developer role

Familiar with Objective-C.
Installed Apple’s iPhone SDK 3.0 or higher.
Familiar with the iPhone application development.
Imported the following project into XCode provided in the Incomplete_iPhoneApp.zip file.

System requirements

For the integration developer:

A PC running Windows® XP
IBM® WebSphere Integration Developer V6.2

For the iPhone developer:

An Apple Mac® running OS X Version 10.5.8
Xcode Version 3.1 for iPhone development

Duration

For the integration developer tasks: 2 hours
For the iPhone developer tasks: 1 hour

Download files

This tutorial provides the following files that you can download:

Incomplete_iPhoneServicesModule.zip: This is the incomplete workspace that the integration developer will work with in the Integration developer tasks section.
Complete_iPhoneServicesModule.zip: This is the complete workspace if you wish to skip the Integration developer tasks section and just run the finished code.
Incomplete_iPhoneApp.zip: This contains the incomplete XCode iPhone applicaton that the iPhone developer will work with in the iPhone developer tasks section.
Complete_iPhoneApp.zip: This contains the completed iPhone application.