BSOA Orchestra Designer's Guide
Table of Contents
Chapter 1. The
Purpose of This Guide
Chapter 2. Process
Console Description
2.2 Console Frames Description
Chapter 3. Designer
Process Console Guide
3.2 How To Add a New Process Model
3.3 How To Delete Process Models
List of Figures
Figure 2‑1. Process Administration Console Login Screen
Figure 2‑2. Description of Administration Console Frames
Figure 3‑1. Import Files Frame for Adding a New Process
Model
Preface
This guide describes which facilities the BSOA Console provides to users via the role of Designer.
This guide provides the
information necessary to be able to:
· Access Process Management in order to create or modify Process Models,
· Manage Orchestra Process Models: import BPEL files, etc.
To access the Process Administration Console, connect to
the following URL http://Your_Host:Your_HttpPort/jiapAdmin, and enter your
login and password.
Figure 2‑1. Process Administration Console Login Screen
After logging in, the Administration Console is available in the main frame of a browser. It is divided into four parts (five if the footer frame is configured), each with a specific profile:
Figure 2‑2. Description of Administration Console Frames
Navigational Tree
Use this frame to navigate between the different options the console offers, which are based on the user profile and the user-application context.
Click either on the /
signs, or on the desired labels to expand/retract a branch.
For a terminal node, the Core Frame then presents the corresponding information.
Header Frame
By default, this frame displays the title and icon of the Process Console. The console administrator may customize the content of this frame by displaying the content of a configured URL.
Utility Frame
This frame displays the name of the user logged in, a link
to set user preferences, a button to refresh the header, core and footer
frames, and a
button to exit the console. It also displays
the path corresponding to the information shown in the Core Frame.
Core Frame
This is the main frame of the console. A navigational path showing the tree structure of the information displayed along with the actual information is available. Different tabs may be accessed in this zone, and all information entered will be displayed within it.
Footer Frame
By default this frame is not displayed. The console administrator may configure this frame to display the content of a configured URL (see Customizing Header/Footer URLs below).
Customizing
Header/Footer URLs
To customize the header frame or display a customized footer frame, the properties $JONAS_BASE/conf/jiapadmin_custom.properties file must be edited. This can be done either within the navigational tree by navigating to the Edit Custom Frames link of the Administrator tree, or by manually editing the above properties file.
The following is an example of a configured footer frame,
while preserving the default header frame:
# Custom console fields
# bottom frame (footer) of the Admin Console.
footer=http://www.somewhere.com/acme.html
# top frame (header) of the Admin Console.
header=
It is the responsibility of the administrator to make sure the customized frame content fits within the dimensions of the frame.
Any user managing process models to view a given process model must have a designer profile. An Administrator user of the Process console sets this operator profile. See the BSOA Orchestra Administrator’s Guide to set operator profiles.
Select the following path in the Navigational Tree (Left Panel): Designer →
Process management → Import files.
Figure 3‑1. Import Files Frame for Adding a New Process Model
To specify a BPEL process the console must be given:
1) a BPEL file describing the process,
2) a WSDL file describing the interfaces of the process, and
3) a WSDL file (or a set thereof) for each Web Service called within the process.
· Use the “Browse” button to specify a BPEL and WSDL file as required.
· Use the “Browse” button to specify an external WSDL file. To import more than one external WSDL file, click the “Add” button to browse and import additional files. Once specified, these files are listed under the “External WSDL file” line (at the right of the “Add” button) and can be deleted as desired before clicking on the “Import” button.
· Click the “Import” button at the bottom of the form to import the BPEL process definition into the BPEL engine.
|
Note: At least one BPEL file and one WSDL file are required in order to import a process. |
Select the following path in the Navigational Tree (Left Panel): Designer → Process management → Process models.
The “Process models” list is displayed in the core panel with the following information:
· Name: the name of the imported process model.
· State: the state of the process model (DEPLOYED, TODEPLOY).
- The DEPLOYED state occurs after the Deploy action is taken, which is described under the Operator → Process Models menu choice in the BSOA Orchestra Operator's Guide.
- The TODEPLOY state occurs after an Import Files operation.
· Creator: the login name of the designer who imported the process files into the Orchestra engine.
· The last column of the table, named “Action”, contains a “Delete” link for each process in the list.
Click this “Delete” link to delete the process.
|
Note: This operation will be successful if no instance of this process is still in running state. To terminate a running BPEL process instance, refer to the BSOA Orchestra Operator's Guide which describes the Operator → Process Instance menu choice and the Terminate action. |