Save info   Get password
Home Submit your blog Edit Account Rules RSS-Archive Contact


Facets XSD Editor Developing Message Interfaces
2008-05-19 09:02:45
Use Facets enable you to restrict the value range of a data type in XML schema to a particular subset. This enables you to determine exactly which value is expected in a special case for a simple data type, an element, or an attribute. For example: · A telephone number (using a pattern on a string) · A selection of permitted values, for example to classify the different classes
Read more: Editor , Message , Interfaces

Developing Business Logic
2008-07-09 23:10:36
Purpose You first define a collaborative process independent of a particular system landscape and create design objects in the Integration Builder. The proxy programming specifies how you implement proxies so that applications can communicate with the Integration Server. Process Flow .. 1. For descriptions of the design objects integration scenario, integration process, interfac
Read more: Business , Logic

Developing Business Logic Design
2008-07-09 23:10:12
Purpose The development of a collaborative process begins with its design (see: Design Time). The Integration Builder provides you with an environment with which you can describe integration scenarios, integration processes, interfaces, and mappings independently of a system landscape. These objects are stored in the Integration Repository and are associated with software component versions that
Read more: Business , Logic

Designing Integration Scenarios Developing Business Logic
2008-07-09 23:09:45
Purpose You use an integration scenario to define the message exchange and message flow for collaborative processes. Normally, these are processes between different business partners that are generally coupled by the exchange of messages. The integration scenario provides you with a central point of access for all objects that you require for semantic and technical integration, for example inter
Read more: Business , Logic , Designing , Scenarios

Designing Integration Scenarios Integration Scenario
2008-07-09 23:08:58
Definition An integration scenario completely models the exchange of messages for a collaborative process and provides an overview of the process flow. Structure An integration scenario is a design object of the Integration Builder, is uniquely identified by a name and a namespace, and is subject to versioning. To model the exchange of messages and the process flow, the integration scenario co
Read more: Designing , Scenarios

Designing Integration Scenarios Application Component
2008-07-09 23:08:23
Definition An application component is a modeling construct within an integration scenario. From a logical point of view, it represents a participant of an integration scenario. This contains the business tasks and concerns that this participant represents within the integration scenario. An application component can stand for a business partner or a component of a business partner. At runtime i
Read more: Application , Designing , Scenarios , Component

Designing Integration Scenarios Action
2008-07-09 23:07:58
Definition An action represents a function within an application component that is not subdivided further. Action s subdivide the process flow of an integration scenario. Actions are shown as white triangles in the integration scenario editor. The vertical progression of actions from top to bottom corresponds to the logical process flow. An action is an independent design object of the Integr
Read more: Designing , Scenarios

Designing Integration Scenarios Connection
2008-07-09 23:07:32
Definition A connection is a link between two actions within an integration scenario. The following connection types exist: · Sequence Sequence represents the sequence of two actions within the same application component. A sequence is required for portraying the integration scenario process; however it contains no additional information. · Cross-Component Connection A cross
Read more: Designing , Scenarios

Integration Scenario Design Environment
2008-07-09 23:07:09
Purpose In the integration scenario design environment of the Integration Builder, you can display and edit integration scenarios. Integration This section contains information about the object editors for the objects Integration Scenario and Action, including all functions and procedures associated with them. Features The integration scenario design environment contains two editors: ·
Read more: Environment

Quick Start: Designing an Integration Scenario
2008-07-09 23:06:40
Use This section provides you with a step-by-step guide to defining a simple integration scenario. In the process, you will learn about the graphical modeling options available, how to insert application components, how to create actions, and how to define synchronous and asynchronous connections. Prerequisites · Software component version Select a software component version in the n
Read more: Designing , Quick , Start

Integration Scenario Design Environment Action Editor
2008-07-09 23:05:49
Use You use the action editor to display and edit actions. Furthermore, you can assign one or more outbound or inbound interfaces to an action. You do not define actions for specific integration scenarios and can therefore reuse them in different integration scenarios. Prerequisites You have created a new action or have opened an existing one. For more information about creating objects in
Read more: Action , Environment , Editor

Integration Scenario Design Environment Assigning Interfaces
2008-07-09 23:05:09
Use You can assign one or more outbound or inbound interfaces to an action. These can be message interfaces, RFCs, or IDocs. For more information about the different interface object types, see Introduction to Interface Development. Note the following restrictions when assigning interfaces: · The software component version of the interface must be the same software component version as
Read more: Environment , Interfaces

Deassigning Interfaces Integration Scenario Design Environment
2008-07-09 23:04:40
Use You can remove the assignment of an interface to a particular action. Procedure To deassign an interface, select the table line for the interface concerned and choose Delete Selected Lines ( ). Ensure that the interface is not part of a connection in an integration scenario before removing the assignment. Otherwise, this will lead to inconsistencies in the integration scenario. For mor
Read more: Environment , Interfaces

Integration Scenario Editor Enabling Application-to-Application Processes
2008-07-09 23:04:17
Use You use the integration scenario editor to display and edit integration scenarios. In the interactive graphical work area, you can visualize the integration scenario as a Component View. In a component view, you can display the process flow of an integration scenario and assign other objects, which define how messages are exchanged. You can define multiple component views for an integration
Read more: Application , Editor

Inserting an Application Component Integration Scenario Editor
2008-07-09 23:03:38
Use You can assign an integration scenario both an application component and a role. You must specify the implementing product version for the application component, including its extended name if applicable. Furthermore, you define the name of the WSCI interface for the application component. Prerequisites You have opened an integration scenario. Procedure ... 1. Position the c
Read more: Application , Component , Editor

Displaying/Editing Application Components Integration Scenario Editor
2008-07-09 23:03:03
Use You have the option of displaying or editing information about an application component. Prerequisites An integration scenario is open (integration scenario editor). This contains at least one application component. To call the Display/Edit Application Component editor, either · Double click the application component. · Position the cursor on the application component an
Read more: Editor , Components

Removing Application Components Integration Scenario Editor
2008-07-09 23:02:27
Use You have the option of deleting an application component from an integration scenario. Prerequisites The application component does not contain any actions. Procedure Position the cursor on the application component and choose Remove Application Component from the context menu. Result The application component is deleted from the integration scenario. The column belonging to the applica
Read more: Editor , Components

Designing Mappings in SAP XI
2008-07-09 23:01:27
Purpose In SAP Exchange Infrastructure, interface descriptions of function calls (interfaces) are saved in XML format. The parameters of these interfaces determine the contents of the messages that are exchanged between systems (see also: Interface-Based Message Processing). A mapping refers to the mapping of interfaces or messages to other interfaces or messages. You may need to use mappings of
Read more: Designing

Overview in SAP XI Designing Mappings
2008-07-09 23:00:42
You can define mappings for an interface pair (source and target interface) by using message interfaces and message types in the Integration Repository. You can also define the corresponding mappings when the source or target interface is an IDoc, an RFC, or another interface connected by an adapter. As illustrated in the graphic, in the standard case a request contains the data that is
Read more: Designing , Overview

Interface Mappings in SAP XI
2008-07-09 22:59:55
Use Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time (see: Defining Interface Determinations). The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response


Test Environment for Interface Mappings in SAP XI
2008-07-09 22:59:15
Use To check whether an interface mapping that you have defined functions at runtime, test the interface mapping on the Test tab page. Note the following restrictions: ● The Integration Builder cannot yet access the value-mapping table at the design stage. The results of accessing the value-mapping table are estimated as text output in the test results. ● The runtime constants of th
Read more: Environment , Interface

ABAP Mappings in SAP XI
2008-07-09 22:58:32
Use ABAP mappings are mapping programs in ABAP objects that customers can implement using the ABAP Workbench. Prerequisites Note the prerequisites in the sections Purpose and Integration as well as the Restrictions in Mapping Development with the ABAP Workbench. Features An ABAP mapping comprises an ABAP class that implements the interface IF_MAPPING in the package SAI_MAPPING. The interface


Enabling Application-to-Application Processes
2008-07-09 22:57:40
Purpose This documentation describes how to centrally design processes to integrate applications within a company as part of the enabling application-to-application processes IT scenario. The applications to be integrated can be SAP or non-SAP applications. Prerequisites The following table lists the prerequisites for this documentation: Prerequisites Description Technical usage type for
Read more: Application

Concepts of Process Integration (XI)
2008-07-09 22:57:15
This section is aimed at developers who want to get an overview of Process Integration (XI) and how it can be used. · Basics describes the main concepts and terms of Process Integration (XI). · The term XI content or Process Integration content refers to the integration knowledge required to define collaborative processes. · Connectivity provides an overview of the optio
Read more: Concepts

Enabling Application-to-Application Processes Go and Create
2008-07-09 22:56:50
This section contains information about the scenario as well as references to further information about the individual process steps. How to Familiarize Yourself The following procedure helps you to familiarize yourself with the topic: ... 1. Familiarize yourself with the scenario. See: Process Flow of Scenario 2. Work your way through the tutorial. See: Tutorial: D
Read more: Application

Scenario Process Flow Enabling Application-to-Application Processes
2008-07-09 22:56:23
The scenario comprises the following processes: Process Description Configuring the System Landscape Using this process, you: ● configure the involved application components and define system monitoring ● Configure the involved application systems and connect them to the Integration Server ● Model the products, software components, technical systems, and business syst
Read more: Application

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.
Read more: Message

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
Read more: Overview , Structure , Message

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 mor
Read more: Message , Field

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
Read more: Editor , Message

Page 1 of 3 « < 1 2 3 > »
eXTReMe Tracker