Overview of targets

Targets provide additional flexibility by providing the capability of modifying processing by changing the target configured for a reference.

A component can call a component in another module thereby reusing existing logic to minimize the time and cost in building an application. WebSphere® Process Server provides additional flexibility through targets. Targets allow an installed application to benefit from advances in processing by allowing the application to change the endpoint of a cross-module invocation, using the administrative console, without rewriting or redeploying the application.

To take advantage of the flexibility provided, you must understand how the system names the targets. The link from the calling module must connect to the correct target.

Target names

Target names are derived from how the calling component invokes the target. The names have the following format:
Invocation type
Name format
Synchronous
A name that follows the Java™ Naming and Directory Interface (JNDI) format, for example:
folder/export/fullpath_to_target/target_component_name
Asynchronous
A name with the format
folder/calling_component_name/
full_path_to_target_component/target_component_name
Multiple destinations
This name is the same as an asynchronous invocation but the target actually sends a message to multiple destination components.
Related tasks
Changing targets

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)