Verastream Process Designer (VPD) is an end-to-end Web service composition and orchestration product based on the BPEL standard, consisting of the Process Design Studio and the Process Server. After installing, you can use the Process Design Studio to quickly import Web services, apply logic constructs, test, and execute them as a BPEL process. The process is immediately ready for deployment as a Web service to the Process Server.
These requirements apply to both the Process Design Studio and the Process Server.
NOTE: In preparing system requirement guidelines, Micro Focus may rely on published claims (that it cannot independently confirm) regarding the capabilities of the non-Micro Focus products. Micro Focus therefore recommends that you contact your suppliers directly with questions or concerns regarding their products.For the Process Designer (including both the Design Studio and Process Server) you should allow approximately 1 GB of disk space. Additional space for data (such as models, projects, and logging) or if the Windows platform does not have .NET Framework or Microsoft Installer already installed may be required.
The Process Design Studio runs on the Windows platform. When User Account Control (UAC) is enabled, you must run setup as Administrator.
Operating system | Supported versions (64-bit) |
---|---|
Microsoft Windows |
|
The Design Studio contains tutorials that walk you through important workflows in the product. These tutorials are in Portable Document Format (PDF) and require Adobe Reader. You can download the reader at http://get.adobe.com/reader. To set browser preferences, open Acrobat Reader, go to Preferences, and click on the Internet settings. For example, you can choose to have the Reader always open PDFs in an external window instead of embedded within the browser: just clear the "Display PDF in browser" option.
Web Services Explorer is a browser-based tool for testing SOAP-based Web services that are generated by your project. It is installed with the Design Studio and requires Internet Explorer version 11, Chrome, or Firefox 12.0 or higher.
Although the Design Studio is a Windows-based component, the Process Server runs on multiple operating systems.
Operating system | Supported versions (64-bit) |
---|---|
Microsoft Windows |
|
Red Hat Enterprise Linux |
|
SUSE Linux Enterprise Server |
|
z/Linux |
|
Preventing tampering, information leakage, and other security vulnerabilities is important. For a list of possible vulnerable files, see the online help topic, How to Work Securely.
To install the Process Design Studio:
install_directory\processserver\bin\pscli.cmd
.
setup.exe/install/quiet
setup.exe/install/quiet INSTALLDIR= "C:\Program Files\Micro Focus\Verastream"
C:\Program Files\Micro Focus\Verastream\
. The install process creates two sub-folders: ProcessDesignStudio and ProcessServerFor zLinux users, you must have Java SE Version 8 installed before running an installation of Process Designer. During installation you will be prompted to specify the location of an existing JDK installation. You must specify the full path before you can continue with the installation.
To install the Process Server:
./vpd-r6.x-prod-linux or sh vpd-r6-prod-linux
for Linux systems./vpd-r6.x-prod-zlinux or sh vpd-r6-prod-zlinux
for zLinux systemsy+ENTER
. Enter 'y' to accept the license.After accepting the license, navigate the menu using the following commands:
Choose this option | To do this... |
---|---|
p) installation path: /opt/microfocus/verastream | choose another base installation path |
o) installation owner: (current owner:current group) | choose the owner and optional group for all files and directories under the base location where the product is being installed. Specify user or user:group. After installation by root is complete, you can directly log in as the specified user to manage the product. The default installation owner is root:system |
After you configure the options, enter i and press Enter to finish installing.
You may install the Process Server silently by specifying all necessary installation and configuration files in a separate file. Assuming this file is called install-input and you are installing on a Linux system, type this command on the command line: vpd-r6.x-prod-linux --licenseagreed --input install-input
.
Example
File install-input
(below) contains all previously described options and is a sample delivered with the installation.
If you are installing on zLinux, you need to add the location of a JDK 1.8.0 installation to your input file:
# Path to the Java SDK (version jdk1.8.0 or higher) javapath=full path name of the java installation
Sample install-input file:
# Package selection processserver=true # Installation location # basepath=/opt/microfocus/verastream/ # Owner of installation and startup id servers # owner=vpduser:vpdgroup
You can specify option -yes to answer all uninstall questons, thus setting up an unattended uninstall process.
The most recent versions (R5, R5 SP1 and R6 SP1 and 2) of Verastream Process Designer are 64-bit products. Previous versions were 32-bit products. If you are upgrading from a 32-bit product, read Technical Note 10145 before proceeding.
The Process Server supports SHA-256 security certificates with 2048 bits keys. All certificates coming from the server, such as the HTTPS Verastream Web services, use this protocol. SHA-256 security certificates are designed by the National Security Agency and meet the United States information processing standards.
When you upgrade from a previous version, existing certificates (installed with the previous version) are maintained.
In this version (R6 SP2) of Verastream Process Designer the install path has changed to .../Micro Focus/verastream
. If you had a previous version installed in .../attachmate/verastream
, it will upgrade there. New installs will be installed to .../Micro Focus/verastream
.
This version of Verastream Process Designer supports RESTful services. RESTful services require complex input and output types. If you want to expose your existing projects as RESTful services and you are using simple types for inputs and outputs, you must modify them to be complex. New projects use complex inputs and outputs by default. You can refer to those as an example.
If you had processes deployed with persistence enabled, each execution instance was saved in the database. After you upgrade, these instances will no longer be available.