Top Blogs

Jumat, 26 Februari 2010

Import and export tips and tricks

This section contains tips that apply to importing and exporting.

Checking errors

If there were any errors or warnings while you were exporting from or importing into Business Integration Modeler, you can click a Details button to read them. This list cannot be printed, and cannot be viewed again once you close it. Ensure that you take a screenshot before you click OK.

Importing structured business items

You can use Microsoft® Excel spreadsheets to create business items (based on the structure used in Business Integration Modeler), export them to delimited text files, and import them into Business Integration Modeler. See Importing data from delimited text files.

Importing from WebSphere® Business Integration Workbench Version 4.2.4

If you import a project using the MQ user option, subprocesses that have been defined as a block are converted to local processes. (The non-MQ user option does not recognize the concept of a block, and so all subprocesses are converted to global processes.)

Mapping to BPEL and MQ Workflow FDL

For a detailed description of how models are mapped to BPEL, see WebSphere Business Integration Server Foundation export reference. For MQ Workflow FDL, see WebSphere MQ Workflow export reference.

Understanding warnings in BPEL and MQ Workflow FDL mode

Several warnings may appear when assigning resources to tasks (processes) in BPEL and MQ Workflow FDL mode. The warnings indicate the fact that the attributes will not be mapped to any BPEL or FDL constructs. For a detailed description of the restrictions for BPEL, see Modeling in BPEL mode. For FDL, see Modeling in MQ Workflow FDL mode. Also see Import and export in the release notes for a list of known limitations.

Specifying manual and automatic tasks

You cannot specify directly in Business Integration Modeler whether a task is manual or automatic.

If you are exporting to FDL, this is determined by a Staff assignment on a task. If a task has a resource requirement that is of type Person or Staff (or a subset of one of these), the generated FDL activity is set to manual and contains the staff assignment. Otherwise, it is set to automatic.

If you are exporting to BPEL, a task with resource requirement (of type Person/Staff) will be exported as a staff activity with a potential owner. The potential owner is generated with a different verb query (as per the WPC predefined verbs) based on how you assign the resources and roles to tasks. For example, when a role is assigned to a task and the type of the resource that executes the task is set to Staff or Person, the potential owner is set as a "Member of Role". If you specify an individual resource requirement with the resource type set to Staff or Person, you can then create a query "Criteria" mapped to a WPC verb. For a specific individual resource requirement, such as "Jane Doe" where Jane Doe is a Staff, a "User by userID" is generated. If you want to specify editor or reader instead of potential owner, you must manually update the generated BPEL file.

Exporting to BPEL

The BPEL generated from Business Integration Modeler uses the IBM® extensions to BPEL (for example, staff activity and Java™ snippets).

Exporting to MQ Workflow FDL

WebSphere MQ Workflow Buildtime does not have auto-layout, and Business Integration Modeler does not generate any visual layout information. You must arrange the visual elements manually after importing them into MQ Workflow Buildtime.

Exporting from Business Integration Modeler to FDL files will not produce the same files as importing those FDL files into WebSphere MQ Workflow Buildtime and exporting them as FDL.

Exporting text data to UML

When you export to UML, text data is mapped in the following ways:
  • The description of an element is mapped to the UML's class's comment. The comment appears in the Model Documentation pane in the IBM Rational® XDE™ when you select the class. Because of a bug in XDE, when you first import the XML file, nothing shows in the Model Documentation pane. Close the model and open the model file again.
  • The description of an attribute, and its rule if the attribute is of a predefined basic type, are mapped to the UML attribute's comment. The comments appear in the Model Documentation pane in the IBM Rational XDE when you select the attribute from the Model Explorer. If the attribute is a complex type, its rule is mapped to the UML association's constraint.

Recreating UML Activity Diagrams

Since diagram information is not part of the XMI 1.1 DTD, the exported XML file does not contain any diagram information. You must create diagrams using the imported model elements after importing the model file. See the detailed instructions in Importing into Rational XDE.


Ads By Google