Working with projects
This page is the starting point for finding information about working with projects using
App Connect Studio.
- Studio basics
Studio provides an environment called a Workspace in which you can design and configure your integration projects. The Toolbox is the area next to the Workspace where multiple tabs contain components that you use to build an integration project; components such as endpoints, schemas, orchestrations, style sheets, transformation, WSDLs, activities, variables, and functions. - Creating a new project
Each time you create a project, a project properties file is also created with the project name. These property files are used when you export or publish projects. - Protecting a project with a password
In Studio, you can protect a project by assigning a password to it. - Opening a Project
When you first launch Studio, the Project last worked on is opened by default. There are several ways to open a different project. - Saving a Project
You can save a project using the Studio toolbar. - Renaming a Project
You can rename a project using the Studio toolbar. - Publishing a Project
When you publish a project, Studio connects to an Integration Appliance and directly updates the Integration Appliance with the documents that make up the project. Publish a project when the project is complete, has been validated, and has been tested in Studio. You cannot publish a project that has not been successfully validated. - Exporting a Project
Export saves all the orchestrations, endpoints, schemas, and other items associated with the project, into a single file that ends in the .par extension. - Configuring Project Settings
You can assign a unique version number to a project using the Project Settings dialog box. - Setting Preferences
You can specify Project, Orchestration, Flat File, SSL/Kerberos, Session Login, and XML Schema preferences from the Preferences dialog box. You can change preferences at any time. - Creating Configuration Properties
Create configuration properties or name/value pairs in a project. Use configuration properties to supply the default values for destination nodes of a map in the Mapping Editor. - Editing Configuration Properties
You can edit configuration properties in Studio and in the Web Management Console (WMC). - Creating Global Configuration Properties
When a global configuration property is created, you can import the global configuration property into a project as a project configuration property. - Searching for Template Integration Projects (TIPs)
Template Integration Projects (TIPs) are stored in the App Connect solutions repository. Through the Configuration Wizard, TIPs guide you through the configuration steps for an integration scenario. TIPs can be downloaded to your local machine. The login window is pre-populated with the User Name and Password to make it easier for you to download the TIPs, without registration. - Installing Module Provider Libraries
Both App Connect Studio and the Integration Appliance require library files (.jar and .dll) associated with instances of certain connector types to be imported. For example, the following connectors require additional libraries: Database Connector, JDE, JMS, MQ, PeopleSoft, and SAP. These files must be present in Studio to enable configuration of the endpoints and orchestrations that use any of those connectors. - Uploading Files into a Project
You can upload only specific types of files into a project. For example, if you plan on mapping a string to XML data (valid to a particular XML Schema), you must first upload the XML Schema file (ends in the .xsd extension) into the project before mapping the nodes in the XML Schema. - Uploading Included XML Schemas
An XML Schema or WSDL document can include other XML Schemas in the main document, using Schema Inclusion, Schema Inclusion with Redefinition, or Importing a Namespace. - Specifying the Location of a File to Upload
Files can be uploaded into a project from a web location (HTTP or FTP Server) or from the local file system. - Valid External File Types for a Project
When building orchestrations, you can upload XML Schemas or other files into your project to complete configuration tasks. External files are used in connection activities and orchestrations that use a message that Studio cannot generate an XML schema for automatically. You must supply an XML schema or DTD if the message must be transformed or if you need to define a job key for the message. - About Valid Names
To be valid, the names for projects, Endpoints, orchestrations, stylesheets, Flat File Schemas, XML Schemas, WSDLs, and transformations must not exceed 42 characters and must not contain any of the reserved characters or words. - Undo and Redo Operations
Studio stores up to the last 100 actions you make and you can undo and redo those actions. You can undo and redo an action that you take on the fields in the UI, orchestration views, Mapping Editor, project tree, configuration properties, and variable panel activities. - Updating a Changed XML Schema
If you created a project that uses an XML Schema and the XML Schema changes, you can attempt to update the existing XML Schema with the new XML Schema. - Using the Project Explorer
The Project Explorer dialog box list the set of entities of the current type, that have been already defined for the project. - Using the HTTP Post Utility
This utility provides a simple HTTP client interface that enables you to post messages/requests to HTTP servers, which is useful for orchestrations that have an HTTP Receive Request activity as the starter activity.