Differences

This shows you the differences between two versions of the page.

--- en:software:tim:deploy_processdefinition [2019/09/18 16:57]
wikiadmin [Error and Correction]
+++ en:software:tim:deploy_processdefinition [2019/09/24 15:19] (current)
wikiadmin [Error and Correction]
@@ Line 1: / Line 1: @@
+====== Deployment of a Process model from iGrafx ======
-====Deploying a Process Definition====
+In order for a process model to be successfully integrated into iPA and be ready to use, it first has to be deployed or uploaded.
-In order for a process definition to be successfully integrated into TIM and be ready to use, it first has to be deployed/uploaded. The Deploy-interface is used to issue a process definition in TIM. The interface can be called under:
+Once the process model has been validated, from the Automation menu the user has the choice of either: \\
+  ***Deploy Model**
+  ***Download Deployment File**
+----
+==== Direct Deployment of a Process model ====
+To Deploy without exporting beforehand, choose **Deploy Model**.  You will be prompted to enter: \\
+  ***Automation Deployment URL**
+  ***Username**
+  ***Password**
+For the **Automation Deployment URL** use the following URL:
+ 	<code>http://<server><:port>/loom-portal/Deploy.iGrafx</code>
+If the process should not be immediately activated, this may be designated by adding the suffix **?publish=false**.
+ 	<code>http://<server><:port>/loom-portal/Deploy.iGrafx?publish=false</code>
+----
+==== Download and Manual Deployment of a Process Model ====
+To Deploy manually, you must download the model definition to a .zip file.  To do this choose **Download Deployment File**.  You will be prompted to save a .zip file to a file location.
+Once the .zip file has been created, the Deploy-interface is used to deploy a process model in iPA. The interface can be called under:
 <code> http://<server>:<port>/loom-portal/deploy.htm </code>
 \\
-The Process definition itself must have either the appropriate [[en:software:tim:user_profile_properties|user]] or one of its [[en:software:tim:user_profile_properties|groups]] listed as the [[en:software:tim:roles|deployer]]. Additionally, this user or group must have the role of [[en:software:tim:roles|deployer]] in TIM. Lastly, the process definition has to be passed to TIM as either a .zip file or as a bpmn file.\\
+The Process definition itself must have either the appropriate [[en:software:tim:user_profile_properties|user]] or one of its [[en:software:tim:user_profile_properties|groups]] listed as the [[en:software:tim:roles|deployer]]. Additionally, this user or group must have the role of [[en:software:tim:roles|deployer]] in TIM. Also, the process definition has to be passed to TIM as either a .zip file or as a bpmn file.\\
-Also, the process definition has to be exported as a .zip file and released in TIM. \\
 <note tip>An SVG Graphic for a bpmn is optional. A zip-file already contains a graphic and therefore a graphic does not need to be added </note> \\
-{{:software:tim:deployment_default.png?400  |}}
+{{:en:software:tim::Deploy_with_Zip_file.jpg?400  |}}
-{{:software:tim:deployment_bpmn.png?400  |}}
+{{:en:software:tim::Deploy_with_XML_and_SVG_file.jpg?400  |}}
 ----
+\\
+Should the process still require configuring within the [[en:software:tim:processrepository|ProcessRepository]] before being deployed, then the check-box marked **Publish process automatically** can be deactivated.
+<note tip> If the option is deactivated, it will appear only in the final deployment.</note>
+----
+\\
 A confirmation message will be shown after the deployment procedure has been executed successfully (without any problems).
-{{:software:tim:deployment_sccess.png?600 |}}
+{{en:software:tim:Deploy_with_Zip_Success_Message.jpg?600 |}}
 ----
-==== Automatically Deploying the Process ====
-Should the process still require configuring within the [[en:software:tim:processrepository|ProcessRepository]] before being deployed, then the check-box marked **Publish process automatically** can be deactivated.
+==== Error and Correction ====
-<note tip> If the option is deactivated, it will appear only in the final deployment.</note>
------
+If an error occurs a message will be shown.  If the process definition can not be deployed, the following points should be addressed before contacting support for help: \\
- 	==== Direct deployment from the model ====
- If the process is to be deployed without being exported beforehand, this can be accomplished using the following URL
- 	<code>http://<server><:port>/loom-portal/Deploy.iGrafx</code>
- 	If the process should not be directly activated here, this may be designated by adding the suffix **?publish=false**.
- 	<code>http://<server><:port>/loom-portal/Deploy.iGrafx?publish=false</code>
- 	----
- 	==== Error and Correction ====
- 	If an error occurs and the process definition is not deployed thereafter, the following points should be addressed before contacting support for help: \\
   * Is the user correctly entered or is the [[en:software:tim:tim.properties#default-client|Client]] missing?
   * Is the password entered correctly of is the [[en:software:tim:userprofil_profile|LDAP Authentifcation]] on/off?
@@ Line 38: / Line 59: @@
   * Does the user have **deployer** [[roles| rights]]?
   * Are all of the groups correctly entered into the characteristics of the process model?
- 	{{  :software:tim:process_properties.png?600 |}}
-A message will also be shown if an error occurs.\\
-<note tip>If problems are still experienced, please contact TIM via e-mail at support@tim-solutions.de. Please send the file **server.log** as an attachment.</note>
+<note tip>If problems are still experienced, please contact https://www.igrafx.com/support/customer-support. Please send the file **server.log** as an attachment.</note>

iGrafx Automation Wiki

User Tools

Site Tools

Differences

Page Tools