The Project tab

The Project tab contains folders for each component

The following component folders can be accessed from the Project tab:
  • Orchestrations
  • Endpoints
  • Flat File Schemas
  • Stylesheets
  • Transformations
  • WSDLs
  • XML Schemas

When you create new instances of a Project tab component, these instances display within the appropriate component folder.

To create new instances of any of the components in the Project tab, right-click on the folder (e.g., Endpoint) to display a menu and select the create option. The component is then created and displays under the appropriate folder, and given a generic name: Orchestration, Orchestration1, and so on. You should rename all components to something meaningful in the context of your integration project.

You can create these components in any order. To ensure that all components are available, create Flat File Schemas, and upload XML Schemas, WSDLs, and Stylesheets before you start defining the orchestration.

Orchestrations
Orchestrations are the central component of any integration project. An orchestration contains a sequence of activities that perform a specific business process. For example, an orchestration could get a Flat File from a FTP Server, take the data from the Flat File, transform it, and then save the result into a database. An integration project must contain at least one orchestration.
Endpoints
Endpoint components display in the Endpoint folder of the Project tab and specify the connection information required to connect to the various external systems or endpoints. The Integration Appliance supports connecting to Endpoints of many types including Email (SMTP, POP), FTP, SFTP, HTTP, HTTPS, JDE, JMS, MQ, NetSuite, PeopleSoft, Salesforce.com, SAP, Siebel, Web Services, and many commercial database systems.
Each type of endpoint has an associated configuration pane where you specify endpoint connection information. For example for a database endpoint, you must provide a database name, server name, user account, and password. You may, however, want to specify a different set of configuration information when you move from a testing environment to the production environment. You can simplify the process of moving from one set of connection information to another (for example: from one database to another) by defining configuration properties (or name/ value pairs) in studio, to define the configuration information.
Flat File Schemas
A Flat File Schema defines the parsing rules, content, and structure of a Flat File. Flat Files are any non-XML text data, such as comma- and tab-delimited files and EDI or industry-specific textual formats, such as the Health Level 7 (HL7) format for the health care industry.
In addition to supporting variable-length Flat File formats that use delimiters to distinguish one record or field from another, studio also supports fixed-length records and fields such as the COBOL copy book format. In studio using the Flat File Schema Editor, you can create definitions for either type of text file and groups.
Stylesheets
An XSLT Stylesheet defines how to transform XML data from one format to another format. You can upload a XSLT Stylesheet into studio and add an Apply XSLT activity to your orchestration that uses the XSLT Stylesheet during run time.
Transformations
The Transformation folder contains standalone maps. A standalone map represents a set of one or more mappings between source and destination nodes.
For example, you can create a standalone map called myMap that contains a set of mappings between a source XML Schema called IncomingOrder and a destination XML Schema called ShippingOrder. A standalone map can be used to create any number of Map Variables activities in the same orchestration or in other orchestrations in the same project. You can create a Map Variables activity from a standalone map by dragging the standalone map from the Transformations folder to an empty node on the orchestration. A Map Variables activity based on the standalone map is created.
WSDLs
A WSDL (Web Services Description Language) is an XML document that describes a Web Service. It defines how to access a Web Service and the operations available for the Web Service.
XML Schemas
An XML Schema defines the content and structure of XML data. XML Schemas are typically stored in files that end with the .xsd extension. Once you upload an XML Schema into a project, you can use that XML Schema to create variables used in the activities of an orchestration.



Feedback | Notices


Timestamp icon Last updated: Thursday, December 17, 2015


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.gettingstarted.doc/getstart_theprojecttab.html