Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

Starting the Server and Running a Process

Starting the Server and Running a Process

After you deploy a process, described in Creating and Deploying a Business Process Archive Contribution, you can run the process by starting the server and sending the appropriate message to instantiate the process.
The Process Server that comes with Process Developer consists of the Process Server engine running under Apache Tomcat. Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies.
You must start the embedded engine before deploying your processes. When it starts, it scans for new, updated, and deleted
.bpr
files.
  1. If you have not already done so, set up the server, as described in Setting Up the Embedded Process Server.
  2. Select the Servers view in the lower right of the workspace.
  3. Select the
    Start the Server
    button, as shown in the example.
As the server starts up, you see start-up tasks scroll in the Console. Several files are deployed to the embedded server each time you start it. When the server is started, the State indicates this, as shown above.
You can use the Process Console to manage deployed and active processes. To display the Console, select the
Process Console
toolbar button and notice that the following URL appears in the browser address field:
http://localhost:8080/activevos
Change the port number if port 8080 is already in use on your computer.
For more information, select
Help
in the Console.

0 COMMENTS

We’d like to hear from you!