Once you have designed a module, you can upload it to an LSPS server and run it. Note that only a module that is executable can be run or instantiated.
To upload modules from PDS, first connect PDS to a server with LSPS Application Once you have established the connection, you can upload a model to the server and execute it.
Note: You can use also command-line console as well as from the Management Console to deploy and instantiate your model. However, you need to export your Modeling as a deployable bundle first.
When you upload a module with a data model that contains shared Records, tables for the related data is created in the database. If you modify the shared Records and pertinent relationships and upload the module with the same name and version again, the already existing tables need to be adjusted.
Therefore, whenever you are uploading or running a module, you need to define, how to handle such a situation:
Important: The Database Schema Update Strategy setting does not impact LSPS runtime information, such as, data on uploaded models, model instances in the current execution status, persons details, etc. and the data remains unchanged regardless of the setting. Only tables based on module data models are subject to the strategy.
PDS connections to LSPS servers are set under Runtime Connections > Runtime Connection Settings. The connections to embedded servers are added automatically when the servers are generated (For the PDS Embedded Server, when first started and for the SDK Embedded Server, when the LSPS Application is generated). Other connections must be configured manually.
To connect PDS to a server with LSPS Application other than the PDS or SDK Embedded Server, do the following:
To use a proxy server to connect from PDS to an LSPS Server, do the following:
Manual: as defined in Proxy entries below
You can define in the Proxy bypass table, the hosts that should be excluded from the proxying.
The PDS Embedded Server is an application server with LSPS Server accessible on http://localhost:8080
.
To launch the PDS Embedded Server and connect the Process Design Suite to the server, do the following:
Alternatively, click the Start Embedded Server ( ) button on the main toolbar.
On start, if the server does not exist, it is created in the .LSPSEmbedded
directory of your workspace. To reinstall it, delete the directory and start the server again.
The content of the LSPS database includes the runtime information, such as uploaded models, model instances in the current execution status, persons details, etc. Before you reset the database consider exporting it so you can load it if necessary. When resetting the database, all data is lost.
To save, restore, or reset the LSPS Embedded Server database, do the following:
Important: If a database is restored, the current database goes lost.
Note: The database is stored in the current workspace in the .LSPSEmbedded folder.
When you upload a module, the module and all its imported modules are uploaded to the LSPS Server of the server to which PDS is connected. An uploaded module is identified by its name and version and if a module with the given name and version is already present on the LSPS Server, its is replaced.
You can upload your modules to your LSPS Server from the Modeling perspective or from the Management Perspective. The upload is performed based on the upload configuration: when you are uploading a module for the first time, PDS automatically creates an upload configuration, which is then used for upload.
To upload a module for the first time, do the following:Note: Ensure that the server with LSPS Server is running and your PDS is connected to it (Information on the current connection is in the line at the bottom of PDS).
This creates an upload and run configuration, which is used for the next upload and run of the module from the Modeling perspective: To adjust the configuration, do the following:
To upload a module to the LSPS Server to which your PDS is connected, do the following:Note: Ensure that the server with LSPS Server is running and your PDS is connected to it (Information on the current connection is in the line at the bottom of PDS).
You can check the list of uploaded Modules in the Module Management view.
Once you uploaded an executable module with its module imports to an LSPS Server, you can run it as a model instance. Typically, you will instantiate Models from the Management perspective, but PDS allows you to upload and instantiate a Model directly from your workspace.
On Model instantiation, the Execution Engine of the LSPS Server creates a runtime version of a model: a model instance. Since you can create multiple model instances of a model, each model instance is created with a unique ID.
In additional, a model instance may define specific properties in the form of key-value pairs. For more information on Model instance lifecycle, refer to the GO-BPMN Modeling Language User Guide.
To create a model instance of an uploaded Model from the Management perspective, do the following:
Note: If a Model instance remains in the status Created, check the Error Log for errors. Error Log may contain also error entries of the server if these were caused by a Process Design Suite feature, which appear primarily in the Console view.
To instantiate a model of a module for the first time, do the following:Note: Ensure that the server with LSPS Server is running and your PDS is connected to it (Information on the current connection is in the line at the bottom of PDS).
This creates an upload and run configuration, and instantiates the module. Next time you run the module from the Modeling perspective, the created configuration is used.
To adjust the configuration, do the following: