Configuring the server messaging services capacity - HxGN EAM - 12.0 - Mobile - Hexagon

HxGN EAM Mobile User Quarter VGA

Language
English
Product
HxGN EAM
Search by Category
Mobile
HxGN EAM Version
12

The HxGN EAM installation sets the messaging service capability with a default setting. This setting may not be optimal depending on the balance between the number of users and the available bandwidth for each user. Change the default setting depending on your company's specific situation.

When downloading data to HxGN EAM Mobile, the load on the HxGN EAM server can be significant, especially for initial downloads, where all data is extracted, formatted, and downloaded through HxGN EAM Mobile data downloading web services. If multiple HxGN EAM Mobile users perform frequent, large downloads, configure the messaging services capacity on the EAM server to balance the need to download data and continue serving other users, including non-HxGN EAM Mobile users.

  1. Change parameters in the databridge_properties_advanced.xml configuration file. This file can be found in the depconfig subfolder of the HxGN EAM home folder.

    A Databridge license is not required to perform this task.

  2. Run the deployment process. See the HxGN EAM Enterprise Edition Installation Guide.

Example databridge_properties_advanced.xml

<?xml version="1.0" encoding="UTF-8"?>

<DeployOption>

<WSLogConfigFile>$DEFAULTFOLDER$/WSLog.xml</WSLogConfigFile>

<!--

<ArchivePeriod>99</ArchivePeriod>

<PurgePeriod>367</PurgePeriod>

-->

<DefaultJMSQueue>

<MaxThreads>5</MaxThreads>

</DefaultJMSQueue>

<AdditionalJMSQueues>

<Queue>

<Name>WS_REQUESTQUEUE_1</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

<Queue>

<Name>WS_REQUESTQUEUE_2</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

<Queue>

<Name>WS_REQUESTQUEUE_3</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

</AdditionalJMSQueues>

</DeployOption>

By default there are three queues configured (WS_REQUESTQUEUE_1, WS_REQUESTQUEUE_2, and WS_RE QUESTQUEUE_3). Each queue has a maximum of two threads, as shown in the <AdditionalJMSQueues> element. It is important to decide on a total maximum number of threads the HxGN EAM Mobile users can use concurrently for downloads. If this number is too high, the system may not have enough resources (CPU capacity, memory, and database connections) to support the desired configuration.

Consider the database connection pool size for the HxGN EAM server when deciding the total maximum number of threads.

See the HxGN EAM Enterprise Edition Installation Guide.

When an EAM server serves both HxGN EAM Mobile and non-HxGN EAM Mobile users, the following setting is recommended as the typical setting for the database connection pool size when you frequently have multiple concurrent users running initial data downloading:

  • <min-size> = 40

  • <max-size>=60

The total maximum number of threads for messaging services follows this guideline:

<Total maximum number of threads> x 3 x 2 should be smaller than <max-size>

After you decide on the total maximum number of threads, the sum of <MaxThreads> of each queue must be equal to or less than the total maximum number of threads. To balance the number of concurrent users experiencing a good response time, the speed performance for each user, and system resources, adjust the number of queues and the <MaxThreads> each queue has, without exceeding the total maximum number of threads.

You can add an additional queue by adding a <Queue> element. In the following example, a queue with the name MOBILE_QUEUE_A is added.

<AdditionalJMSQueues>

<Queue>

<Name>WS_REQUESTQUEUE_1</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

<Queue>

<Name>WS_REQUESTQUEUE_2</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

<Queue>

<Name>WS_REQUESTQUEUE_3</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

<Queue>

<Name>MOBILE_QUEUE_A</Name>

<MaxThreads>2</MaxThreads>

<Group>*</Group>

</Queue>

</AdditionalJMSQueues>

Each queue in the AdditionalJMSQueues list must have a unique name.

You can change the maximum threads each queue can use (the <MaxThreads> element value in each <Queue> element). A higher number of <MaxThreads> for the queue increases the speed performance of data downloading for a download process dispatched to this queue.