The System page enables you to manage session timeout settings, global process concurrency settings, recurring schedule items, message queues, the frequency for generating new periods, and monitor the health of your application server clusters.

The following image shows the System page.

The System page is divided into the following areas:

• The Session Administration area enables you to define the period of time after which persisted session information is removed from storage.
• The Global Process Queue Concurrency area enables you to specify the maximum number of processes that can be running concurrently.
• The Recurring Meeting Generating Horizon area enables you configure recurring schedule items.
• The Channel Administration area enables you to administer message queues.
• The Period Generation Horizon area enables you to configure how often and for how many years new schedule periods are generated.
• The Diagnostics area enables you to monitor the health of application server clusters.

Setting session timeout preferences

You can set persisted session timeout preferences in the Session Administration section of the System page. The persisted session timeout setting defines the period of time after which persisted session information is removed from storage.

The amount of time after which session information is persisted is specified in the server or environment file, defined by the Session Timeout property in the Clustering/Session subtab in the environment file editor. See NexJ CRM deployment for more information.

To set session timeout preferences:

1. In the Session Administration section of the System page, click the Edit button . The Edit Session Administration dialog opens.
2. Enter a new value in the Persistent Session Timeout (minutes) field. By default, this field is set to 60 minutes.
3. Click OK. The Edit Session Administration dialog closes.

The session timeout value is updated.

Managing message queues

You can set up throttling or turn on and off your message queues by editing the maximum receivers for each channel.

To manage message queues:

1. In the Channel area of the System page, select a channel.
2. Click the Edit button . The Edit dialog opens.
3. Enter a value in the Max Receivers field.
4. Click OK. The Edit dialog closes.

The maximum number of receivers is defined for the selected channel.

Setting global process queue concurrency preferences

The global process queue concurrency setting specifies the maximum number of processes that can be running at the same time. The setting also specifies the maximum number of processes that you can define for an individual process queue in the Process Queue page.

Consider modifying this value when you need to increase the concurrency for the system or on a specific process queue. Ensure that you test in a non-production environment and consider making incremental changes to the value to avoid encountering performance issues in your production environment. By default, global concurrency is set to 4.

To modify the global process queue concurrency value:

1. In the Global Process Queue Concurrency area of the System page, click the Edit button . The Edit Global Process Queue Concurrency dialog opens.
2. Enter a new value in the Global Concurrency field, and click OK. The Edit Global Process Queue Concurrency dialog closes.

The global process queue concurrency value is updated.

Setting the recurring meeting generating horizon

You can configure how far ahead recurring schedule items will be created and how often they will be recreated.

To set the recurring meeting generation horizon:

1. In the Recurring Meeting Generating Horizon area of the System page, click the Edit button . The Edit Recurring Meeting Generating Horizon dialog opens.
2. In the Name field, specify a name for the recurrence batch job.
3. In the Start Time drop-down fields, specify a date and time for the recurrence batch job to begin.
4. In the Time Period (mins) field, specify how often you want the batch job to run and recreate your recurring instances. For example, the default value, 1440, causes the batch job to run once a day.
5. In the Generation Horizon (days) field, specify a limit of how many days into the future occurrences should be generated. All schedule items that fall before the horizon will be created, and all those that are after the horizon will not.
6. Click OK. The Edit Recurring Meeting Generating Horizon dialog closes.
7. To run the batch job manually, click the Run batch job now button .

The application will automatically generate the recurrence instances to the end of the generating horizon, and continue to regenerate according to the set time period.

Setting the period generation horizon

You can configure how often and for how many years new periods are generated.

To set a new period generation horizon: 

1. In the Period Generation Horizon area of the System page, click the Edit button . The Edit Period Generation Horizon dialog opens.
2. In the Timer Period (days) field, specify how often you want to generate new periods.
3. In the Generation Horizon (years) field, specify how many years to keep generating new periods.
4. Click OK. The Edit Period Generation Horizon dialog closes.
5. To run the batch job manually, click the Run batch job now button .

The application will automatically generate the different periods from the current year to the end of the number of years specified.

Related links

Creating process queues