Creating an orchestration
There are three steps to creating a completed orchestration:
Create the new orchestration, rename the orchestration, and build
the orchestration.
Renaming an orchestration
Orchestrations are given default names when they are created.
You can rename it from the Project tab.
Building an orchestration
Studio provides visual cues in the workspace so that it
is easier to see and control the placement of activities in an orchestration.
When you drag-and-drop activities from the Studio Toolbox to the workspace,
a green circle icon displays the target location in the orchestration
where the activity is to be placed. When adding activities to the
branches of logic activities, Studio highlights the target branch.
Verifying orchestrations
Studio can simulate the CIOS runtime so that you can to test orchestrations within a
project and resolve any issues before deploying the project to the Integration
Appliance.
Using SSL in Studio
The Secure Sockets Layer (SSL) is the standard security
technology for establishing an encrypted link between a server and
a client. The encrypted link ensures that all data passed between
the server and clients remain private and unchanged. To create an
SSL connection a server requires an SSL certificate. This section
provides an overview of using SSL in Studio, discusses Transport Layer
Security (TLS) and SSL security, discusses certificates and supplies
the procedures you need to properly import Certificate Authority (CA)
and end-entity certificates and private keys for use when verifying
SSL client authentication.
Importing an end-entity certificate
An end-entity certificate is a digitally-signed statement
issued by a Certificate Authority to a person or system. It binds
a public key to some identifying information and is used for encryption,
authentication, digital signatures and other purposes. The term “end-entity”
is used to distinguish it from a Certificate Authority certificate.
The signer of the statement is the issuer and the entity discussed
in the certificate is the subject.
Importing a Certification Authority (CA) Certificate
Abbreviated as CA, a Certification Authority is a trusted
third-party organization or company that issues certificates used
to create digital signatures and public-private key pairs. Because
they guarantee that the two parties exchanging information are really
who they claim to be, CA's are a critical component in data security
and electronic commerce. Although the relationship between CA's
is most commonly hierarchical, CA certificates can also be used to
establish trust relationships between CA's in two different public
key infrastructure (PKI) hierarchies. A PKI is the set of people,
policies, procedures, hardware, and software used in creating, distributing,
managing and using digital IDs. In all of these cases, the CA certificate
is critical to defining the certificate path and usage restrictions
for all end-entity certificates issued for use in the PKI.
SSL server authentication
SSL server authentication verifies that sites you communicate
with are who they claim to be. Authentication confirms a server's
identity through standard techniques of public-key cryptography to
ensure that a server's certificate and public ID are valid and have
been issued by a certificate authority listed in the client's list
of trusted CA's.
Testing an SSL server connection
After creating an endpoint for the server using SSL, you
are ready to test the SSL server connection.
SSL client authentication
Client authentication is similar to server authentication
except that the server requests a certificate from the client to verify
that the client is who it claims to be. The certificate must be an X.509 certificate
and signed by a certificate authority trusted by the server. You can
only use client authentication when a server requests a certificate
from a client. Not all servers support client authentication.
Using the Log Viewer
Orchestration monitoring data is displayed in the Log Viewer
in a table or text format.
Viewing an orchestration
You can use orchestration view icons on the workspace,
and View options from the Studio toolbar menu
to manipulate your orchestration view in the workspace.
Validating an orchestration
An orchestration must be valid (complete and correct) before
you can publish it to the Integration Appliance. Use the validation
feature in Studio to validate your orchestration.
Printing an orchestration
You can print an orchestration directly or view a print
preview of an orchestration.
Processing orchestration jobs sequentially
You can use the Process Orchestration Jobs Sequentially
option when an orchestration contains activities that can conflict
with each other when multiple instances of the orchestration are running.
An instance of an orchestration is also known as an orchestration
job.
Enabling persistence
The Orchestration pane contains an Enable Persistence check
box that by default is selected. The setting of the Enable Persistence
check box affects the way orchestration jobs are restarted after a
failure.
Adding a global exception handler to an orchestration
During run time if any of the activities of the orchestration
throws an exception, and a global exception handler has been enabled,
the global CatchAll branch is run.