|
| |
| |
| |
|
|
|
| Free SAP XI Books,Projects And Interview Questions |
| ABAP Proxy Generation,Application-to-Application,Developing Business Logic,Integration Scenario Editor,Interfaces and Proxy,Java Proxy Generation,Process Integration,XI Connectivity,XI TCodes,XSD Editor |
| Language: English |
| RSS Feeds for this Blog |
|
Statistics |
| Unique Visitors: 0 |
| Total Unique Visitors: 28471 |
| Visitors Out: 680 |
| Total Visitors Out: 680 |
|
|
|
| |
|
|
| |
|
| XI Process Integration (XI) Basics |
| 2008-09-12 02:45:38 |
Design, Configuration, and Runtime The implementation of a collaborative process is split into three phases: · During the design phase, you document the entire collaborative process and determine which interfaces are required. You can either define new system-independent interfaces to implement at a later point in time (outside-in development) or work with functions that already exist in the systems (inside-out development). In this phase you design the logical collaborative process by describing in a specific role the message exchange between the application components. This description is still not specific to any particular installed system (see also: Design Time). · During the configuration phase, you configure your collaborative process for a specific system landsca...
|
| |
|
| XI Process Integration (XI) Design Time |
| 2008-09-12 02:45:05 |
Communication in SAP Exchange Infrastructure is interface-based. That is, messages are generally created by calling an interface. SAP Exchange Infrastructure supports two approaches for implementing a cross-system process: · Outside-In: You create the relevant interfaces for the cross-system process in the Integration Builder. These message interfaces are a programming language-independent description in XML. You use these message interfaces to generate callable interfaces (proxies) in target systems. · Inside-Out: The functions that are to be called using SAP Exchange Infrastructure already exist in the application systems. To be able to use an interface description of these functions in the design process, you import specific interface descriptions to the Integration Re...
|
| |
|
| XI Process Integration (XI) Configuration Time |
| 2008-09-12 02:44:24 |
At configuration time you configure the cross-system processes for an existing system landscape. The configuration describes how the Integration Server is to process inbound messages and to which receiver or receivers messages must be sent. Various engines are involved in message processing on the Integration Server: The Integration Engine is the central runtime component; the Adapter Engine is the runtime component for adapter communication; the Business Process Engine is the runtime component for the execution of integration processes on the Integration Server. The Integration Server provides the following different services: · The Adapter Engine and the Integration Engine both have inbound and outbound processing. For example, when a message is received, a check is performed to...
|
| |
|
| XI Process Integration (XI) Implementing Collaborative Processes |
| 2008-09-12 02:43:46 |
Every type of business software is based on a real integration process, which is automated to accelerate integration processes and reduce costs. SAP XI concentrates on processes involving the exchange of messages between different systems. Examples of such processes and tasks are: Order processing involving different systems Providing products on internet marketplaces Implementing B2B processes with a business partner by using the internet Setting up a new software system that needs to exchange data with existing systems Processes of this kind that have not yet been automated are referred to in this documentation as collaborative or cross-system processes. SAP XI enables both top-down and bottom-up implementation of such processes. Inte...
|
| |
|
| XI Process Integration (XI) Interface-Based Message Processing |
| 2008-09-12 02:43:09 |
SAP Exchange Infrastructure messages are based on XML. How can an application send a message of this type to a receiver? The idea is similar to a Remote Function Call (RFC): Communication with another system is encapsulated in an interface; the parameters of this interface are converted into a message. However, the significant difference between SAP XI and RFCs is that former always requires two interfaces for communication: One on the sender side and one on the receiver side. This has the advantage that the sender and receiver interfaces do not need to match exactly (loose coupling). The following graphic illustrates schematically how a message is sent to a receiver using a sender interface: Multiple receivers can exist, the principle remains the same. The graphic illustrates...
|
| |
|
| XI Process Integration (XI) Messages |
| 2008-09-12 02:42:20 |
The SAP Exchange Infrastructure message format is based on XML. Since a message in SAP XI can also have binary attachments, this documentation refers predominantly to messages in general and not specifically to XML messages. XML Properties XML (eXtensible Markup Language) enables you to describe data in a highly intelligible form. An XML schema definition specifies which elements can be used, which attributes these elements have, and how they are structured. More than one instance (a document that matches an XML schema definition) can exist for each schema. The following example of an instance illustrates that the elements in a schema are ordered hierarchically: Rodney Washington 200 S Wacker Drive Chicago IL 60606 Bass Guitar No.14 Confirmed These elements (for example, ) are als...
|
| |
|
| XI Process Integration (XI) Integration Server Engines |
| 2008-09-12 02:41:35 |
The Integration Server is the SAP Exchange Infrastructure runtime component for receiving messages and controlling how these messages are forwarded. During configuration of the XI system landscape, an SAP Web AS client is assigned the role of Integration Server. The following two engines work together in this client to control the message flow: · The Integration Engine is responsible for central Integration Server services, for example, routing and mapping. · The Business Process Engine is responsible for executing and persisting integration processes. Furthermore, the majority of the adapters run on the central Adapter Engine, which is installed on the J2EE Engine of the SAP Web AS, and which can take over inbound and outbound processing on the Integration Server from t...
|
| |
|
| Multi-Mappings in SAP XI |
| 2008-08-22 08:45:20 |
Use A multi-mapping is a mapping program that is not restricted to the transformation of one source message to one target message. You have the following options: You can use a multi-mapping in a transformation step in a integration process. In this case, the mapping runtime supports 1:n-, n:1, and n:m transformations. You can map any number of source messages to any number of target messages. You can use a multi-mapping to map a message to multiple different (and generally smaller) messages during logical routing. Only a 1:n transformation is possible in this case. Integration As is the case for all mapping programs, to be able to configure the mapping programs for source and target interfaces, you need to assign a multi-mapping program to an interface mapping that you will use late...
|
| |
|
| Developing Multi-Mappings for Integration Processes in SAP XI |
| 2008-08-22 08:44:36 |
Purpose This section describes how to develop a multi-mapping for a transformation step in an integration process. In this case, the mapping runtime supports 1:n, n:1, and n:m transformations. Prerequisites The procedure described below requires that the message schemas for the messages to be mapped already exist in the Integration Repository (see also Features in Multi-Mappings) and that they are assigned to asynchronous, abstract message interfaces. You can only use this interface type in integration processes. Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects f...
|
| |
|
| Developing Multi-Mappings for Message Splits in SAP XI |
| 2008-08-22 08:43:58 |
Purpose This section describes how to develop a multi-mapping for a message split (1:n transformation). You can specify the multi-mapping program by means of an interface mapping in logical routing. In this case, the interface mapping not only determines the mapping program, but also determines which target interface the target message is to be sent to in logical routing. Hence the term mapping-based message split. Prerequisites Multi-mappings require the interfaces involved to be asynchronous. There are no other restrictions on the outbound interface of the interface mapping. Messages that result from the split in a mapping-based message split are sent using one Adapter Engine. For this reason, only those adapters that run on the Adapter Engine are supported. The Java proxy runtime i...
|
| |
|
| Mapping Development with the ABAP Workbench in SAP |
| 2008-08-22 08:43:12 |
Purpose SAP XI customers can also develop mapping programs by using the ABAP Workbench. At runtime, these programs are executed on the ABAP Engine of the SAP Web AS on which the Integration Server is running. At present there is no mechanism for shipping mapping programs of the ABAP Engine with SAP applications and importing them on the Integration Server. Therefore, only customers that can create such mapping programs directly on the SAP Web AS of the Integration Server or can transport them there can use ABAP Engine mappings. Unlike XSLT and Java mappings, which run on the J2EE Engine, mapping programs of the ABAP Engine cannot be imported to the Integration Repository. Therefore, there are no mappings shipped by SAP that run on the ABAP Engine. You can implement the following mapp...
|
| |
|
| Message Mappings in SAP XI |
| 2008-08-09 01:44:44 |
Use A message mapping refers to a mapping of messages and is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures and connect to a value mapping. The mapping tool generates Java source code from the graphical mapping description, which is then compiled and packed in a JAR file that the Integration Engine executes at runtime. Features The mapping editor can load the following schemas into the structure overview: · A schema from the Integration Repository: (Fault) message types, IDocs, the request, response, or fault part of RFCs, and message structures from external definitions. The latter are message structures from WSDL, XSD, or DTD documents. · XML schema definitions (XSD) or XML files from a lo...
|
| |
|
| Structure Overview in SAP XI Message Mappings |
| 2008-08-09 01:43:46 |
Use The structure overview displays all fields (elements and attributes) in the source and target structures. In the structure overview, you can assign source and target fields to each other or include them in the data-flow editor (see: Assigning a Field). The structure overview also contains a variety of additional functions that are described below. Features Functions in the Header Area You use the structure overview on both the Definition and Test tab pages. Most of the buttons available in the structure overview are available on both tab pages. Structure Overview Buttons Button Use Tree View (only on Definition tab page) View that only displays nodes for fields (elements and attributes) and their names. Tabular Tree View When yo...
|
| |
|
| Assigning a Field in SAP XI Message Mappings |
| 2008-08-09 01:42:18 |
Use Using the structure overview and the data-flow editor you can map source fields of the source structure to a target field. Features You can: ● Use drag and drop to select a source field in the structure overview and map it to a target field, or the other way around. The mapping editor displays this simple assignment in the data-flow editor. ● Drag a target field and one or more source fields from the structure overview to the data-flow editor. The data-flow editor automatically assigns the first source/target field pair. If a target field has already been mapped, then the mapping is displayed in the data-flow editor. ● Select a source and target field from the structure view by double-clicking. Note that you always transfer source fields to the data-flow editor ...
|
| |
|
| Data-Flow Editor in SAP XI Message Mappings |
| 2008-08-09 01:41:47 |
Use You use the data-flow editor (at the bottom of the mapping editor) to describe the flow of data from one or more source fields to one target field. Since this mapping is only a part of the actual message mapping and refers to a particular target field, this type of mapping is known as a Target Field Mapping. Features The data-flow editor comprises the following: · An editor window in which you can insert functions and source and target fields as rectangles, and move them as required. These rectangles are known as data-flow objects because you use them to describe the data-flow between source fields and target fields. · A function chooser in the lower screen area of the data-flow editor that contains...
|
| |
|
| Example Message Mappings in SAP XI |
| 2008-08-09 01:41:13 |
When you map structures to each other, there are generally particular standard cases that reoccur. To help developers and consultants implement these standard cases, SAP ships message mappings with test data in the software component version SAP Basis. You can find these examples in the namespace http://sap.com/xi/XI/System/Patterns. General To understand the example message mappings, you need to be familiar with how queues and contexts are processed. See also: Structure Mapping by Setting the Context, Processing an Input Queue and Advanced User-Defined Functions. Message Types The following message types are used in the examples: · MapExampleFlatStructureMessageThe structure of the message type is kept simple. Message instances of this mess...
|
| |
|
| MapExampleFilterRecordsByQualifier in SAP XI |
| 2008-08-09 01:40:33 |
Problem In this example, two identical Person records are mapped to each other. Only those records that contain an Id that is less than ten are to be copied to the target message. To facilitate this, the example uses a filter. Solution The target field Person is a structure field that is only created if the condition /ns:MapExampleFlatStructureMessage/Person/Id is fulfilled. The target-field mapping for the Person field therefore uses the createIf function. /ns:MapExampleFlatStructureMessage/Person/Id is assigned to the context MapExampleFlatStructureMessage so that it can be read before the target field Person is created. A simple assignment copies all other fields.......
|
| |
|
| MapExampleFlatStructureToNestedTables in SAP XI |
| 2008-08-09 01:40:05 |
Problem In this example, different Person records are mapped to a nested structure. In the source structure, a single person can have multiple records that contain different telephone numbers. The target structure only has one record per person; the element Telephones contains all the telephone numbers for this one person. The example assumes that the Person records in the source structure are sorted by the field Id: Consequently, Person records with the same Id come one after the other in the source message. If this were not the case, you would have to use the sort function to sort the records by their ID. Solution In the description for the individual target-field mappings, [Root Context] stands for the context MapExampleFlatStructureMessage in the source structure. · Ta...
|
| |
|
| MapExampleNestedTablesToFlatStructure in SAP XI |
| 2008-08-09 01:39:36 |
Problem In this example, the Person record in the source structure contains several telephone numbers for the person. To map this structure to a target structure that contains the telephone numbers for the same person in different flat records for the person, the fields Id and Name from the source structure have to be replicated accordingly. Solution · The target message should contain the exact same number of person records as there are telephone numbers. Therefore, you assign the target field TelephoneNumber to the source field Person. · You then replicate the Id and Name fields of the source message as often as required by means of the standard function useOneAsMany. The target-field mapping for the target field Name looks as follows (the target-field mapping for ...
|
| |
|
| MapExampleTwoTablesToFlatStructure in SAP XI |
| 2008-08-09 01:39:07 |
Problem The source structure in this example contains two records: · A Person record that stores the Id and Name of a person in the source message · A Telephone record that stores one telephone number for a PersonId in the source message The name and telephone numbers for a person are therefore stored in separate records, and can be assigned to each other by comparing the Id in the Person record with the PersonId in the Telephone record. The target structure is flat and stores Id, Name, and TelephoneNumberin a Person record. The problem with this message mapping is that you also need to know the name and telephone number for an ID when you create the Id field in the target structure. Solution · First of all, you need to create the exact same number of Pers...
|
| |
|
| MapExampleTwoTablesToNestedTables in SAP XI |
| 2008-08-09 01:38:31 |
Problem This example is similar to the example MapExampleTwoTablesToFlatStructure: The source structure consists of two records, which contain the name and the telephone number for a person. This example is a little more complicated, since the target structure is not flat, and all the telephone numbers for a person are to be stored within a Person record. Solution · The target structure must have the same number of Person records as there are in the source structure. This following assignment is therefore valid:/ns:MapExampleNestedTablesMessage/Person = /ns:MapExampleTwoTablesMessage/Persons/Person. · You can use a simple assignment to copy the values for Id and Name to the target structure. · To copy the telephone numbers across, you need to have the corres...
|
| |
|
| Mapping Templates in SAP XI |
| 2008-08-09 01:37:43 |
Use Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements. The same applies to the mapping templates themselves: You can save parts of mapping templates as mapping templates and reuse them in mapping templates or message mappings. To simplify the documentation, the text below does not mention explicitly that the statements made for message mappings are equally valid for mapping templates. However, you can replace message mapping with mapping template anywhere in this section, and the respective statem...
|
| |
|
| XSLT Mappings (ABAP Engine) in SAP XI |
| 2008-08-09 01:37:03 |
Use Customers can develop an XSLT mapping by using the Transformation Editor of the ABAP Workbench. Such XSLT mappings are executed at runtime on the ABAP Engine of the Integration Server. To simplify matters, this section refers to XSLT mappings of the ABAP Engine as transformation programs to differentiate them from XSLT mappings from imported archives that are executed on the J2EE Engine. Prerequisites Note the prerequisites in the sections Purpose and Integration as well as the Restrictions in Mapping Development with the ABAP Workbench. Features Runtime Constants You can access the same constants in a transformation program as in an XSLT mapping, except for the constant $MappingTrace. You must declare the constants used as parameters with . F...
|
| |
|
| Mapping Lookups in SAP XI |
| 2008-08-09 01:36:35 |
Use Mapping programs (message, Java, and XSLT mappings) are executed on the Integration Server, where they can access the global value-mapping table (see Executing Value Mappings) and mapping runtime constants. In addition, calls to other application systems are sometimes necessary to meet the following requirements: ● To get read access to application system data in the mapping program ● To call existing mapping routines in the application system To fulfill these requirements, the mapping runtime provides an API for mapping lookups. The API can be executed by message, Java, and XSLT mappings on the Application Server Java. Integration When a mapping program is executed on the Integration Server, the lookup API calls the required application system by using the central Ad...
|
| |
|
| References Between Mapping Programs in SAP XI |
| 2008-08-09 01:35:51 |
Mapping programs can cross-reference and use each other provided that they are in the same, or an underlying software component version: · The Java classes in an archive can be used in the user-defined functions of a message mapping. · Java classes can use each other. · XSLT programs in different archives can include or import each other. It is also possible to call Java methods from an XSLT mapping (see: XSLT Mapping with Java Enhancement).......
|
| |
|
| Java Proxy Generation |
| 2008-08-09 01:35:05 |
Use Using the Java proxy generation function, you can generate Java classes or Java proxy objects from the interface description in the Integration Repository. Using these objects, you can then implement sender and receiver applications in Java; the proxy objects establish the connection to the Integration Server by using the Java proxy runtime. Features You can generate Java proxies for J2EE applications on the SAP Web AS. Proxy generation generates J2EE beans and proxy classes for this purpose. The generated beans satisfy the EJB 2.0 standard. Java proxy generation is part of the Integration Builder and has the following functions: · Create an archive (as a Jar or Zip file)...
|
| |
|
| Naming Java Proxy Objects |
| 2008-08-09 01:34:35 |
Use Compared to ABAP, Java has fewer restrictions regarding names for labels (for example, for classes or data types). This documentation deals with cases where proxy generation cannot copy names without making adjustments. Features The length of labels in Java is practically unlimited and they are case-sensitive. The technical names of the generated Java proxy classes are based on the JAX RPC specification: · Namespaces are mapped to packages. · Classes for interfaces have the suffix _PortType. · Classes for data types have the suffix _Type. The suffixes correspond to the element names from the imported WSDL document and help to avoid naming collisions. For this reason, naming conflicts are ...
|
| |
|
| Attachment: Mapping XSD to Java Proxy Generation |
| 2008-08-09 01:34:00 |
Built-In XSD Data Types and Their Exact Equivalent in ABAP XSD Java string java.lang.String boolean boolean float float double double int int short short long long byte byte date java.util.Calendar time java.util.Calendar No global types are generated for simple data types (tag ), because they only reference built-in data types. Tags Supported for Complex Data Types (in Alphabetical Order) XSD Java (local) Attributes of a class (including access methods) (global) Class (local) Inner class · Attributes of an (inner) class (including access methods) · Inner table class (local) Attribute of an (inner) class (including access methods) Only those ...
|
| |
|
| Designing Interfaces and Proxy Generation |
| 2008-08-06 00:49:01 |
Purpose Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant: · Interfaces designed for message exchange between application systems · Interfaces used by a cross-component integration process to receive or send messages, or both Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process. You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Excha...
|
| |
|
| Introduction to Interface Development |
| 2008-08-06 00:48:24 |
Interfaces are at the heart of every cross-component process. They are referenced almost constantly during design and configuration. For this reason, it is vital that an interface description can be accessed at a central point. The following are interface description types that you can save in the Integration Repository: · Platform-independent message interfaces · Imported interfaces for which an XML representation of a BAPI, RFC, or IDoc is generated in the Integration Repository · External WSDL, XSD, or DTD definitions containing message schemas that you can access in the Integration Builder For all three types, the Integration Repository only contains information about their structure (interface type, parameters used, and ...
|
| |
|
| Communication Parameters Introduction to Interface Development |
| 2008-08-06 00:47:56 |
When you create message interfaces you have to define a series of communication parameters, which are described below. These parameters determine how the message interface will be used and the mode of communication. The communication parameters for imported RFCs and IDocs are defined by their definition in the SAP system (or are defined implicitly; IDocs are always asynchronous). Outbound and Inbound Interfaces These characteristics determine the direction of an interface: · An outbound interface sends a request message that is only used to make a communication party aware of data sent, without waiting for a response message. In the case of the latter, we also refer to publishing interfaces. · ...
|
| |
|
| Interface and Message Types Introduction to Interface Development |
| 2008-08-06 00:47:23 |
In the example below, multiple receiver systems need to communicate with one sender system: · In this example, the receiver SAP system does not support proxy generation. Instead, an IDoc and an RFC are used on the inbound side. To be able to access the names (and schema description) of these interfaces later during logical routing and mapping, you must import an XML description into the Integration Repository. · However, you can generate an inbound proxy for the ABAP sender and the Java receiver. To do so, create two message interfaces in the Integration Repository. Therefore, an outbound message interface can be connected to different receiver interfaces and the other way around. To model or document which interfaces belong toge...
|
| |
|
| Communication Parties (Case Examples) Introduction to Interface Development |
| 2008-08-06 00:46:54 |
The separation of outbound and inbound interfaces separates the calling and the called application from one another. Theoretically, you can therefore combine any interface types. Some typical examples are described below, which illustrate the necessary steps in interface development. For information about the technical prerequisites, see the Prerequisites section in Introduction to Interface Development. General Assigning Interfaces The case examples focus on interface objects. The generate rule is that outbound interfaces are not assigned to the corresponding inbound interfaces until configuration time (see: Defining Interface Determinations). However, you can model this assignment in an integration scenario in...
|
| |
|
| Developing Message Interfaces |
| 2008-08-06 00:46:19 |
Purpose By using platform-independent message interfaces you can define the type of communication and the data to be exchanged before you actually implement your cross-system process. See also: Introduction to Interface Development. Overview The following graphic displays the class model for message interfaces in the Integration Builder: As with all repository objects, message interfaces are organized by using Repository namespaces, which are assigned to a software component version (see also: Organization of Shipment Contents). You can construct message interfaces in the following way: · Using message types and data types. This two-layer structure uses WSDL (Web Service Description Language) and is oriented towards maximum reusability. Customers can also use data type enh...
|
| |
|
| Message Interface |
| 2008-08-06 00:45:36 |
Use You use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure. Depending on the communication parameters defined for a message interface, it can either have the task of sending a request (outbound) or receiving a request (inbound). Assigning an outbound interface to an inbound interface enables multiple communication parties to exchange messages with each other (see also: Communication Parties (Case Examples)). The following connections are possible for message interfaces: · A message interface with another message interface · A message interface with an imported interface · ...
|
| |
|
| Message Type Developing Message Interfaces |
| 2008-08-06 00:45:04 |
Use A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type: · More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped. · When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface. For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstra...
|
| |
|
| Inserting Actions Integration Scenario Editor |
| 2008-08-02 03:24:56 |
Use You can assign an action to an integration scenario. Prerequisites In the action properties you have defined whether an action can be used as an internal or external action (see: Action Editor). Note the restrictions regarding the type of application component when using internal or external actions (see Action). Procedure ... 1. Position the cursor on the application component. 2. Choose Insert Action from the context menu. Select an action from the list displayed in the Select Action dialog. Only those actions permitted for the selected application component are displayed (see Prerequisites). 3. Select an action. 4. Choose Apply. You can...
|
| |
|
| Displaying/Editing Actions Integration Scenario Editor |
| 2008-08-02 03:24:08 |
Use You have the option of displaying or editing an action. To do so, use the action editor. Procedure For more information about opening objects, see Object Editors. You can also open an action used in an integration scenario as follows: Position the cursor on the action in the graphical area of the integration scenario editor and do either of the following: · Double-click · Choose Edit Action from the context menu......
|
| |
|
| Removing Actions Integration Scenario Editor |
| 2008-08-02 03:23:36 |
Use You have the option of removing one or more actions assigned to an integration scenario. Procedure ... 1. Select the action or actions in the graphical work area of the integration scenario editor and choose Remove Action from the context menu. If you select more than one action, choose the function Delete Actions from the context menu. For more information about selecting actions, see Functions of the Graphical Editor. Result The selected assignment or assignments between the integration scenario and an action or actions is removed and is no longer visible in the integration scenario graphical work area. All connections associated with the action or actions are deleted.......
|
| |
|
| Defining Start and End Actions Integration Scenario Editor |
| 2008-08-02 03:22:58 |
Use You have the option of defining an action as a start of end action or removing an assignment that you have already made. Procedure To define an action as a start action, select the action in question in the graphical work area of the integration scenario editor and choose Define Action as Start Action from the context menu. From the context menu, you also have the option of undoing the assignment of the selected action as the start action. To define an action as an end action, select the action in question in the graphical work area of the integration scenario editor and choose Define Action as End Action from the context menu. From the context menu, you also have the option of undoing the assignment...
|
| |
|
| |
 |
