Directory
- Database connection Management Tools
- About MySQL Database
- Matters needing attention in the database use
- Export business Process model to XPDL format
- Export XPDL Format
- Preliminary analysis of XDPL format
- Process Model Simple Case
- Description of Activity link
- Message Mapping Description
Database connection Management Tools
Use the Manage database configurations component to manage the connection of the databases, as shown in.
You can use the features here, and delete database connections.
About MySQL Database
Note:
MySQL recognizes case, the database name here, when configuring the database connection, by case-sensitive to fill, for example, here northwind_dbo.
Matters needing attention in the database use
- MySQL data management identifies case, such as table name uppercase and lowercase, for two tables;
- The definition of an Oracle database table is case-insensitive, however, if the table name and column name are enclosed in double quotation marks when the table is being built, double quotes, such as "Doc" for the table name, and Doc in the administrative tool, are not valid when using the SQL statement, and are used in double quotation marks. If you are building a table with uppercase, there is no problem and the case is all the same.
Export business Process Model export XPDL format to XPDL format
In the workspace (Workspace Documents), open the Project (project), right-click the process model you want to export, select Export from the popup menu item, and the Export Wizard interface pops up as shown in.
Select the model type and export plug-in, and in the drop-down box choose "XPDL 2.0 Export" to perform the next step (next).
Note:
The model that needs to be exported needs to complete the publish Operation first (published to an organization).
On the next wizard page, do the following:
- In the model to export option, click to select the process model that needs to be exported;
- Specify the name of the exported file (export filename);
- Click the Export button to generate a ZIP file on the server, and then you can download (Download) to local.
XPDL (XML process definition Language) is a standardized specification presented by Workflow Management Coalition, which enables different workflow software to exchange business process definitions using XML files.
XPDL is a universal framework, which is also an important feature of XPDL, which can support the special use of developers, but the external representation is the same. The implementation of the developer and its external interface can be separated independently, because no matter how you implement, what the graphical description (state diagram, activity diagram, etc.), as long as the external interface conforms to the XPDL specification, then you can maintain the same representation. It is expected that in future releases of WFMC interface 1, the missing attributes in the current version will be included.
XPDL is designed to meet the business process definition of switching, both graphically and semantically, and is the best file format for describing BPMN diagrams. BPEL can also describe business processes. But XPDL not only contains the description of the process execution, but also includes the graphical information of the elements, which is more suitable for business process modeling.
XDPL format Preliminary analysis process Model simple case
The message map in the process model is defined as follows:
Message |
Element |
XForm |
Input |
Testmsg |
Elema |
Testbpmxform |
Input_name |
|
Elemb |
|
Input_count |
Description of Activity link
<activity id="O_1"Name="Start"> <Event> <startevent trigger="Message"> <TriggerResultMessage> <message id="M_o_1"> <ActualParameters> <actualparameter>bpm:testmsg</actualparam eter> </ActualParameters> </Message> </triggerresultmessage > </StartEvent> </Event> <NodeGraphicsInfos> <nodegraphicsinfo Tool Id="Cordys"> <coordinates xcoordinate=" the"Ycoordinate=" the"/> </NodeGraphicsInfo> </NodeGraphicsInfos> <Extensions> <DataObjectType/> <Color></Color> <ExtendedAttributes/> </Extensions></Activity>
Message Mapping Description
<messageMapping> <activity id="O_1"/> <activity id="O_2"> <mapping xmlns=""Sourceid="_testmsg_test_elma"Targetid=""isprocessvariable="false"iscasevariable="false"targetassign="Ns2:testbpmxform_testbpmxformdefaultdeliverymodel_ip/ns2:forminputdata/ns2:freeformcontrols/ns2:input_ Name "operation="Replace Content with"Operation2="SELECT"isnillable="false"Afterassignment="false"> <sourceassign>bpm:testmsg/bpm:test_elma/text () </sourceAssign> </mapping> & Lt;mapping xmlns=""Sourceid="_TESTMSG_TEST_ELMB"Targetid=""isprocessvariable="false"iscasevariable="false"targetassign="Ns2:testbpmxform_testbpmxformdefaultdeliverymodel_ip/ns2:forminputdata/ns2:freeformcontrols/ns2:input_ Count "operation="Replace Content with"Operation2="SELECT"isnillable="false"Afterassignment="false"> <sourceassign>bpm:testmsg/bpm:test_elmb/text () </sourceAssign> </mapping> </ Activity> <activity id="O_5"/> <activity id="O_8"/> <wsdl xmlns=""> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/"Xmlns:xsd="Http://www.w3.org/2001/XMLSchema"Name="Method"Targetnamespace="Http://schemas.cordys.com/default"xmlns:bpm0="Http://schemas.cordys.com/default"> <types> <xsd:schema xmlns:xsd="Http://www.w3.org/2001/XMLSchema"xmlns:tns="Http://schemas.cordys.com/default"xmlns=""elementformdefault="qualified"Targetnamespace="Http://schemas.cordys.com/default"> <element xmlns="Http://www.w3.org/2001/XMLSchema"Name="Test_elma"Type="Xsd:string"/> <element xmlns="Http://www.w3.org/2001/XMLSchema"Name="TEST_ELMB"Type="Xsd:string"/> </xsd:schema> </types> <message name="Testmsg"> <part name="Part_test_elma"Element="Bpm0:test_elma"></part> <part name="PART_TEST_ELMB"Element="BPM0:TEST_ELMB"></part> </message> </definitions> </wsdl></messageMapping>
Reference:
Baidu Encyclopedia. XPDL
Cordys BOP 4.3 Platform Use small experience-database connection management, export process model to XPDL