INBOX
An integral part of the OpenText Process Suite platform is the inbox application that can be accessed by means of the My Inbox artifact included in the My Applications App palette. The inbox is the default mail box that is used to receive or forward any of the tasks and/or notifications originating from a business process model or case model (only tasks).
HIGH AVAILABILITY
The OpenText Process Suite platform web gateway
As described before, when installing and configuring the OTPS platform for high availability, you install the OTPS platform baseline to run in primary distributed mode. Each of the OTPS platform instances will be running its own web server and OTPS web gateway. Typically in these scenarios, you will use an IP (Internet Protocol) Load Balancer to distribute the workload across the multiple nodes of the cluster. Although both hardware and software based IP load balancers can be applied, it is recommended to use a hardware based for better performance and their built-in high availability features.
GUID
Globally Unique Identifier
In the OpenText Process Suite, this is a hexadecimal string consisting of 32 positions, e.g. 000c2990-6953-11e5-e141-1f639364d29b.
Every object or component, process and / or case instances is assigned a GUID to uniquely identify that object or instance of the object. With the process, this is called a Process Instance ID (PID).
File System
OTPS platform instance at file system
When installing the OTPS platform baseline (step 2 in the previous blog), the appropriate folder structure is created at the file system of the server, starting from the level you specified as the folder where to install the OTPS baseline. Refer to the above mentioned folder locations with Windows and Linux.
File System
When you are installing the OpenText Process Suite (OTPS) platform, you are guided through in a number of steps:
