Search

Administration Console

Administration Console

9.2.5
- 9.2.6
- 9.2.4.6

Back Next

Site Properties

Site Properties

You can configure the following properties for the site associated with this Process Console. Each Site Properties page must be configured on a Process Server in its own site.

Field	Explanation
Name	Type in a short name with no spaces. This name appears in the MultiSite page of each Process Console in all the sites. It also appears in the title area of the Process Console. If no name is provided, the host name defined in the Site Service URL is used.
Description	Optional. Type in a short description of the site. The description appears in the MultiSite page of each Process Console in all the sites.
Id	Id assigned to the site by Process Server; this is used in internal communication.
Process Console URL	Type in the address of the Process Console for this site. The URL is defined during configuration and deployment of the server. The URL is the address that other sites use for a link from within the Process Console.
Site Service URL	Define how the site should be contacted for multi-site communication. The address will most likely contain the address of the load balancer installed in front of the servers.
WS-Security Enabled	(Replicated). By default, WS-Security is not enabled. Be sure to configure WS-Security on each node in each site before you enable it for MultiSite. For details on configuring WS-Security, refer to Configuring Process Server for WS-Security . within the Process Server help. If your site environment has another security implementation, you can leave WS-Security disabled.
Allow Optimistic Deployment of User Contributions	(Replicated). If selected, site locking is not performed when BPR contributions are deployed. This means that you are assuming that the same BPR contribution is not deployed from two sites at exactly the same time, and each site does not need to be locked. Enabling this is useful in a multi-tenant environment because it allows for faster deployments. This option does not apply to system deployments. Sites are always locked for these deployments.
Heartbeat Interval	(Replicated). Set the frequency in seconds to poll the site for its availability. The default is 15.
Max Missed Heartbeats	(Replicated). Set the maximum number of missed heartbeats before assuming the site is unavailable. If a site does not respond, the site status changes to Unavailable, and database replication cannot occur. The default is four.
Expected Database Latency	(Replicated). Set the latency in seconds expected for database replication to occur. The default is five seconds. This value serves as a guideline for anticipated database replication. This setting is necessary for the coordination of site to site communications with database replication. Site to site communication is typically completed in milliseconds while database replication varies, depending on your hardware and other environmental factors. A database latency of five seconds attempts to synchronize messages sent via site communications with database replication every five seconds until synchronization is either successful or the until the database latency timeout is reached.
Database Latency Timeout	(Replicated). Set the latency timeout value in seconds. The default is 300. This setting indicates that changes made to one site’s database instance have not been replicated to another site within the latency period. If this value is reached, a critical storage error is written to the application Process Server. You can also configure a server property to monitor storage exceptions. For details, see Monitoring Thresholds, Properties, and Monitor Alert Service .

Multisite Configuration

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.