WPS: Custom code to call map

 // create a BOFactory instance to create BO instance

BOFactory boFactory = (BOFactory)ServiceManager.INSTANCE.locateService("com/ibm/websphere/bo/BOFactory");

// creating input BO

DataObject ldsJobInput = boFactory.create("<name space>","<BO Name>");

HashMap inputMap  = new HashMap();

//adding the inputs to the map

inputMap.put("<input BO Name>",<input BO reference>);

inputMap.put("<input BO Name>",<input BO reference>);

inputMap.put("<input BO Name>",<input BO reference>);//..... as per our submap

HashMap outputMap  = new HashMap();

//adding the out bo's to the map

outputMap.put("<Out BO name>",<out Bo reference>);

// creating the instance for map service

MapService service  = (MapService)new com.ibm.websphere.sca.ServiceManager().locateService("com/ibm/wbiserver/map/MapService");

// calling the map

service.transform("<map namespace>","<Map Name>",inputMap,outputMap,null);

//set the out BO reference to outreference

<output Reference>  =<out Bo reference>;

ex: ServiceMessageObject_1_body_createLDSJob_createLDSJobInput_Content  = ldsJobInput;

WPS: connection factory independent of the name specified by JMS client

$. Is the naming of connection factory independent of the name specified by JMS client?

Yes, the naming of connection factory is independent of the name specified by JMS client. This is made possible by WAS (Web sphere application server) with its resource references. It isolates the application from object names. This feature is important because it gives us the flexibility to change the administered object without changing the JMS client code.

WPS: Relationships

$ What is Relationships?

The Relationship is used to relate the Business Data between two integrated systems. The reference is established and maintained by using relationships.
The relationship service has two distinct relationship types: static and dynamic. Static relationships are used to map between non-primary key values, where the data does not change frequently (such as zip codes). Dynamic relationships are used to define correlations on the key attributes that uniquely identify the business objects.

static and dynamic relationships Reference:

http://www.ibm.com/developerworks/websphere/library/techarticles/1009_venn/1009_venn.html

WPS: Business Objects in WPS

$ What are Business Objects (BO)?

You can use Business Objects, extensions of Service Data Objects (SDO), to provide an abstraction layer for data access. While SDOs provide a universal means of describing disparate data, such as JDBC ResultSet, XML Schema described data, and so forth, Business Objects include some extensions that are very important for integration solutions; you can use them to further describe the data that is being exchanged between SCA services. This includes metadata-like change history or information on the context of the data, such as update, create, delete, and so on.

While the concepts of Service Component Architecture and Business Objects are new, the implementation is standards based. For example, interfaces to any SCA service component are described through Web Service Definition Language (WSDL) or Java interfaces and Business Objects are described through XML Schema (XSD).

WPS: Service Component Architecture

$ What is Service Component Architecture (SCA)?

SCA describes all integration artifacts as service components with well defined interfaces. SCA also introduces the concept of a module, which groups together service components and provides further specification and encapsulation of services. Integration developers can use the Assembly Editor in WebSphere Integration Developer to group service components into modules, and to specify which service interfaces you want exposed by the module to outside consumers.

You can use Services that include imported components, such as Java Beans or Web Services, along with service components that WebSphere Process Server provides. You can then connect the modules together to form complete integration solutions. SCA concepts let you encapsulate integration logic within modules. This means that you can make a change to a service component within a module without affecting any of the other modules in the overall solution as long as the interface of the module you changed stays the same. This concept applies throughout WebSphere Process Server. All integration artifacts in WebSphere Process Server -- processes, business rules, human tasks, and so forth -- are represented as SCA service components.

This creates a very flexible environment that you can use, for example, to replace an approval module that contains a human task with a module containing a business rule. As long as the interface to the module is identical, you can deploy the updated module, and it will be picked up automatically by all consuming modules without changes.

You can use SCA to invoke service components through both synchronous and asynchronous programming styles. This set of options lets you assemble the modules into overall solutions so that asynchronous channels between service components and modules can increase the overall throughput and flexibility of the system.

WPS: WebSphere Process Server capabilities

WebSphere Process Server WPS supports two capabilities required for an efficient Service Oriented Architecture SOA : 1. a universal invocation model as SCA, 2. a universal data representation as BOs.

WPS PLATFORM:

Service Components:

1. Business Process

2. Human Tasks

3. Business State Machines

4. Business Rules

Supporting Services:

1. Interface Maps

2. Business Object Maps

3. Relationships

4. Selectors

SOA Core:

1. Service Component Architecture

2. Business Objects

3. Common Event Infrastructure

WPS: WebSphere Process Server

$ What is WebSphere Process Server?

Service Oriented Architecture provides you with the ability to develop and modify integration applications dynamically. It also lets you integrate existing applications with newer applications, so that they work together transparently. You can use WebSphere Process Server to develop and execute standards-based, component-based business integration applications in a Service Oriented Architecture.

Reference : 

http://www.ibm.com/developerworks/websphere/library/techarticles/0509_kulhanek/0509_kulhanek.html

WPS: websphere integration developer

$. Explain about IBM websphere integration developer?

Web sphere integration developer provides an IDE to build applications based on service oriented architecture. Web sphere process server and web sphere ESB were built with WID. WID was built with RAD Eclipse based technology.