WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Development and deployment of applications on WebSphere ESB

Options for development and deployment of integrated applications on WebSphere® ESB include working in the WebSphere Integration Developer development environment, working with Service Component Architecture APIs, and enabling the applications in a test or production server environment.

Developing service applications

IBM® WebSphere Integration Developer is the separate development environment for WebSphere ESB. In addition to the WebSphere Integration Developer development environment, Service Component Architecture APIs are published for developers. You can also develop some service components using other application development tools then import them into WebSphere Integration Developer for modelling, editing, testing, and packaging for deployment into WebSphere ESB.

Within WebSphere Integration Developer, you can use an assembly editor to group services into modules and specify which services are exposed by the module to outside consumers. The modules are then connected to form complete integration solutions. You encapsulate integration logic within modules so that a change to services within a module will not affect any of the other modules in the solution if the interface of the changed module stays the same.

Modules, also called Service Component Architecture (SCA) modules when deployed to WebSphere ESB, determine what artifacts are packaged in enterprise archive (EAR) files that are deployed to the runtime environment.

For more information about developing modules for use with WebSphere ESB, see Developing for WebSphere ESB.

For more information about using WebSphere Integration Developer to develop integration applications, see the WebSphere Integration Developer documentation.

Deploying service applications

Deploying is the act of enabling your applications – your SCA modules – in either a test or a production environment. While the concept of deployment is the same for both environments, there are a few differences between the deployment task in each environment. Because it is best to test any changes to your SCA modules on a test server before committing them to the production environment, use WebSphere Integration Developer to deploy the modules into a test environment, and to package them as a standard enterprise application package, for deployment into WebSphere ESB.

Use WebSphere ESB to install and deploy the applications into a production environment. In WebSphere ESB, you can use the standard WebSphere administrative console to deploy and manage the components of service integration packages. For more information about deploying applications into WebSphere ESB, see Deploying modules.

If you need to deploy many application files, which means installing many SCA modules, you may want to use a batch file. For more information about batch files, see "Deploying applications using Apache Ant tasks".


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/covw_deploy.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).