HP TRIM. Software Version: 7.2x. HP TRIM IDOL Configuration

Transcription

1 HP TRIM Software Version: 7.2x HP TRIM IDOL Configuration Document Release Date: August 2012

2 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notices Copyright Hewlett-Packard Development Company, L.P. Trademark Notices Adobe is a trademark of Adobe Systems Incorporated. Microsoft, Windows, Windows XP and Windows Vista are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle and/or its affiliates.

3 Documentation Updates The title page of this document contains the following identifying information: Software Version number, which indicates the software version. Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software. To check for recent updates or to verify that you are using the most recent edition of a document, go to: This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to: Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

4 Support Visit the HP Software Support web site at: This Web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: To find more information about access levels, go to:

5 Contents HP TRIM IDOL Configuration Basics... 6 Sizing and Requirements... 9 HP TRIM IDOL Sizing Considerations... 9 Small Sites... 9 Medium Sites... 9 Large Sites... 9 Physical Requirements TRIM IDOL Sizing Questionnaire Users General Information HP TRIM Document Management System Advanced Configuration Creating additional content engines IDOL Options Threads DistributeByReference DCI Round Robin MaxResults StopwordIndex Paths Database Read-only Default Operator Troubleshooting IDOL Logging in HP TRIM Logs relevant to each content engine Logs relevant to the TRIM IDOL services including DIH and DIH logs Changing the log file locations Removing an IDOL database DREDELDBASE Restarting Document Content Indexing Insufficient Disk Space TRIM IDOL database set to read only Compacting an IDOL Database Options for Improving Initial Indexing of Document Stores... 20

6 HP TRIM IDOL Configuration Basics By default, the HP TRIM IDOL service and TRIM IDOL content services are installed by selecting IDOL Services in the HP TRIM installation under the Server / Workgroup branch. The IDOL components are part of the HP TRIM Workgroup Server installation. The IDOL installation on the selected IDOL Server will also have HP TRIM installed. However, the HP TRIM Workgroup Server is not necessary for the operation of IDOL content indexing, and so the HP TRIM services do not need to be running on the IDOL Server. If the Workgroup service is not going to be run on the IDOL Server, the server should not be registered in HP TRIM Enterprise Studio (TES) as a Workgroup Server to avoid errors in other Workgroup Server logs about being unable to communicate with the non-active Workgroup Server. The HP TRIM installation provides two distributed IDOL content engines for the storage of indexed document content. By default, the HP TRIM IDOL Distributed Index Handler (DIH) and Distributed Action Handler (DAH) engines are installed into the HP TRIM application directory. The path to the IDOL content engines is determined by the location of the TRIM ServerData directory, unless specifically mapped to an alternative directory in the IDOL configuration file. The DIH working folders are also located in the HP TRIM application directory, but can be changed by including the [Paths] section of the TRIM IDOL Service.cfg file. See the Distributed Index Handler (DIH) 7.3 Administration Guide for more information. Each content engine is an OEM licensed version of IDOL. This provides for the indexing of up to 10 million documents per content engine, although the recommended size is only 5 million documents. Additional content engines can be created either for the purposes of: Handling greater document volumes Increased performance Failover and mirroring options None of these are handled by the TRIM installation and need to be set up manually. How to achieve this is discussed later in this document.

7 Create an IDOL index through the TRIM Enterprise Studio, using the dataset s content index context right-click command Content Index Create IDOL. The Create Content Index dialog appears: Query Server Name should be the fully qualified name for the TRIM IDOL Server. The ports should remain with their default values unless you have specifically modified the TRIM IDOL configuration file located in the IDOL directory under the HP TRIM applications directory. Server Instance name can only be changed by manually editing the TRIMConfig.tcfg file. This is the content index database name within IDOL itself. If it is modified in TRIMConfig.tcfg for any reason, the content index database name must also be modified in the IDOL service configuration file to match. When configuring IDOL, the Miscellaneous section within TES enables you to set the maximum size of a file and a compressed file that will be processed by the content indexer. The maximum size of each is 2048MB. Files larger than the Maximum size are ignored by the document indexing process.

8 Before starting a document content index, you should think about the types of files that you may want to exclude from a content index. This can be handled by specifically excluding documents of a particular Record Type by using the Suppress Content Indexing option in the Record Type s properties Electronic tab, or for file types through TRIM Enterprise Studio General - File Types: The TRIM IDOL Service.cfg file is used to configure the HP TRIM IDOL installation. Here, you can make changes to various IDOL options including ports, number of content engines, mirroring, max results, threading, failed indexing and log paths. Specifics are covered later in this document. The directories TRIM Content Service 1 and TRIM Content Service 2 store the configuration details for the IDOL content engines. Here, you can access the configuration files for each of the content engines and modify ports to match the settings in the TRIM IDOL Service.cfg file. You can also use it to change the physical path for the IDOL content engine.

9 Sizing and Requirements HP TRIM IDOL Sizing Considerations How HP TRIM and IDOL is implemented depends on the TRIM environment it needs to support. Document content indexing could be a simple case of installing the default configuration. Alternatively, for medium or enterprise installation of HP TRIM, the server platform hardware requirements and configuration can vary greatly. Small Sites Sites that have fewer than 5 million documents are considered small from a TRIM IDOL perspective. The two content engines can be installed either on a separate server or a designated Workgroup Server. Medium Sites Sites with more than 5 million and fewer than 20 million documents are considered medium from a TRIM IDOL perspective. The TRIM IDOL defaults will handle the size of the data store indexes, however it is worth taking into consideration the likely growth of the data stores and making allowances in the initial configuration of the IDOL content engines. Consideration should also be given to the physical location of the content engines and it is recommended that these engines be placed on separate physical disks to optimise performance. See below section on physical requirements. One or more additional content engines should be created before the initial ingestion to spread the load and allow for growth of Indexes. If mirroring or failover is required, it may be necessary to add additional content engines. Below are some generic hardware requirements for HP TRIM IDOL Servers to help you determine whether your current infrastructure is sufficient to meet your needs. Large Sites For larger/enterprise class sites it is recommended that you consult your HP TRIM support team, business partner or consulting team for specifics on scaling your IDOL solution. A questionnaire has also been prepared that will enable you to source advice on sizing requirements (see below). The following section discusses some of the physical hardware considerations. It is important to note that physical disk I/O plays a significant part in a successful HP TRIM IDOL implementation, as well as the free space on each disk. Virtualisation technologies such as VMware greatly impact on disk I/O so physical servers are strongly recommended.

10 Physical Requirements Note Windows Server 2008 R2 64-bit A minimum of two cores per content engine (default of 4) 4 GB of RAM / content engines Minimum of one 200 GB HDD (TRIM IDOL). This is not for the content engines. 1 IDOL Server content engine per 5 million documents with a minimum of 240 GB minimum space each. Each logical disk requires a minimum RPM with simultaneous bandwidth of 120MB/s and IOPS, with bandwidth being the more important metric. Each content engine should be located on a separate logical disk unless the shared disk can ensure the above specification. If using SAN for storage, each content engine requires a dedicated LUN. HP does not recommend that this server be virtualized. IDOL index disk specifications indicated in this sizing recommendation are for optimal performance. Substandard write speeds may impact the performance of initial index creation and synchronization of new content. Substandard read speeds may impact search performance. HP recommends no RAID, RAID 0, 1 or 10 depending upon the customer's hardware redundancy level of support requirements. For full redundancy and failover of the system, all of the above systems may be replicated on identical hardware. For IDOL Server, the recommended number of servers should be mirrored and the Distributed Index Handler (DIH) should be used for index mirroring. Note that the mirrored systems can also be used to increase performance. DIH mirroring is configured through the TRIM IDOL Service configuration file. The number of content engine servers and the need for a dedicated IDOL ingestion server depends on the TRIM environment. A dedicated IDOL ingestion server represents an enterprise server dedicated to the handling of all incoming text converted data from the Workgroup and event servers and distributes them to separate servers handling the content engines. The following section provides a series of questions that help determine your server platform hardware requirements

11 TRIM IDOL Sizing Questionnaire To determine the HP TRIM IDOL Server platform hardware requirements for HP TRIM 7.2.1, the following questions should be answered. Users What is the total number of users who will be using the system? How many users will be using the system simultaneously? What are the expected hours of usage per day? What is the expected length of time of a user s single visit? General Information What operating systems (i.e. Windows, Solaris, Linux) and versions are planned for the hardware that will support the system? What is the required query per second (QPS) performance for the system? What is the required average query response time (QRT) for the system? What are the availability and redundancy requirements (fail-over, redundancy)? HP TRIM Document Management System What is the average approximate file size (kbytes)? What is the format of the pages (e.g. html, pdf)? Total number of files? What is the expected growth per annum (in percent, GB, TB)?

12 Advanced Configuration Creating additional content engines By default, two content engines are created. For medium to large installations, it may be necessary to add an additional content engine. The following step-by-step guide shows how this can be achieved. It can be repeated as required. It is recommended that when creating additional content engine services, all existing IDOL services are stopped. This example creates a third TRIM Content Service. For each additional Content Service, replace the number 3 with the appropriate number and pick suitable unused port numbers. 1 Navigate to C:\Program Files\Hewlett-Packard\HP TRIM\IDOL and copy the entire TRIM Content Service 1 directory to a temporary folder 2 Rename the directory to TRIM Content Service 3 3 Open the directory TRIM Content Service 3 and rename the files TRIM Content Service 1.cfg and TRIM Content Service 1.exe to TRIM Content Service 3.cfg and TRIM Content Service 3.exe respectively 4 Edit the file TRIM Content Service 3.cfg and change the existing values to the following: // Service Settings // [Service] ServicePort=9302 ServiceStatusClients=*.*.*.* ServiceControlClients=*.*.*.* // Server Settings // [Server] Port=9300 IndexPort=9301 Note The Port, IndexPort and ServicePort numbers selected are variable the user can select any port value not already in use; however they must be reflected correctly in the TRIM IDOL configuration file.

13 // Path Settings // [Paths] BitFieldPath=D:\HPTRIM\IDOL\TRIM Content Service 3\bitfield DyntermPath=D:\HPTRIM\IDOL\TRIM Content Service 3\dynterm IndexQueuePath=D:\HPTRIM\IDOL\TRIM Content Service 3\indexqueue IndexTempPath=D:\HPTRIM\IDOL\TRIM Content Service 3\indextmp MainPath=D:\HPTRIM\IDOL\TRIM Content Service 3\main NodetablePath=D:\HPTRIM\IDOL\TRIM Content Service 3\nodetable NumericPath=D:\HPTRIM\IDOL\TRIM Content Service 3\numeric RefIndexPath=D:\HPTRIM\IDOL\TRIM Content Service 3\refindex SecIndexPath=D:\HPTRIM\IDOL\TRIM Content Service 3\secindex SortfieldPath=D:\HPTRIM\IDOL\TRIM Content Service 3\sortfield StatusPath=D:\HPTRIM\IDOL\TRIM Content Service 3\status StatePath=D:\HPTRIM\IDOL\TRIM Content Service 3\storedstate TagPath=D:\HPTRIM\IDOL\TRIM Content Service 3\tagindex LanguageDirectory=..\shared\langfiles // Logging Settings // [Logging] LogDirectory=D:\HPTRIM\IDOL\TRIM Content Service 3\logs Note In the above example, the store path for IDOL has been set in the original configuration to D:\HPTRIM\IDOL; however, this path can be placed in any location on any server. UNC paths can be used in this configuration file. It is referenced in the TRIM IDOL Service.cfg file (see below). 5 Save the configuration file 6 Copy the entire directory TRIM Content Service 3 to C:\Program Files\Hewlett-Packard\HP TRIM\IDOL 7 Navigate to the directory C:\Program Files\Hewlett-Packard\HP TRIM\IDOL\TRIM IDOL Service using a text editor (as administrator) and edit the file TRIM IDOL Service.cfg. 8 Edit the following: a b Set [DAHEngines] Number=3 Add [DAHEngine2] Host=servername Port=9300

14 c d Repeat for the [DIHEngines] [DIHEngines] Number=3 Add [DIHEngine2] Host=servername Port=9300 Note Ensure the port number matches that used when editing the file TRIM Content Service 3.cfg 9 Save TRIM IDOL Service.cfg 10 Open a command prompt as administrator and navigate to the directory C:\Program Files\Hewlett-Packard\HP TRIM\IDOL\Trim Content Service 3 11 Run the command Trim Content Service 3.exe install This will install TRIM Content Service 3 as a service 12 Open Windows Services and restart the HP TRIM IDOL Service, HP TRIM IDOL Content Service 1, HP TRIM IDOL Content Service 2 and TRIM IDOL Content Service 3. You may choose to change the value for Log on as for the new service. Please note the name is not prefaced with HP for the new service. Navigate to the location set in the path for TRIM IDOL Content Service 3 and confirm that the IDOL database structure has been created IDOL Options There are a myriad of options that can be applied to a HP TRIM IDOL installation to optimize the IDOL implementation and to tailor the solution to meet your requirements. Here are some of the options to consider when building your IDOL environment. Threads The Threads option sets the maximum number of parallel actions that can be handled by an IDOL Server and the number of action commands that the server can process in parallel at any one time. You can calculate the optimum number of threads as follows: (1 x number of cores ) + 1 spare thread. This is applicable to the TRIM IDOL service and is found in the TRIM IDOL service configuration file under the [server] section (file location: C:\Program Files\Hewlett-Packard\HP TRIM\IDOL\TRIM IDOL Service\). Example: Threads=9 (default is 4)

15 DistributeByReference Plain non-mirror mode sends all commands to all engines and tells the child engines to determine which documents to index. With reference-based indexing, DIH performs these calculations, reducing network traffic and load on the child servers. In HP TRIM the transaction and command files are sent to all content engines. The size of these transaction files is determined by the value set for Number of transactions in an index update file during a reindex. In this example, the value is set to 250MB Note At times, the size may exceed this value, depending on documents being indexed. By adding DistributeByReference=true to the [server] section of IDOL Server configuration file, IDOL is configured to send each content service only part of the transaction file. DCI Round Robin An alternative to DistributeByReference is to use a Round Robin approach to the processing of transaction files in IDOL. Rather than breaking up the transaction file and distributing to the content engines, Round Robin will send the transaction file to one engine at a time and cycle through the available content engines. The advantage here is that the Distributed Index Handler (DIH) does not need to break up the transaction file or send the transaction file to all content engines. See the DIH 7.3 Administration Guide for more information. MaxResults In the TRIM IDOL configuration file, there is a MaxResults setting that limits how many results IDOL will return to TRIM before in a single search. This is included as a performance consideration. TRIM IDOL Service and the Distribution Settings contain the MaxResult option. Change the value in both sections. For example: MaxResults= By default, this value is set to

16 StopwordIndex By default, IDOL will not index or search on several operator words, such as AND, NOT, TO, DO, NEAR, MORE, etc. You can enable indexing of these operator words by editing the IDOL configuration files. Under section [LanguageTypes] in the TRIM IDOL Service configuration file and each of the IDOL Content Service configuration files, add: StopwordIndex=1 Note If you are changing this option after the index has already been created, you should perform a full HP TRIM document content reindex. Paths The default location for the content engines and log files is determined by the settings within the TRIM IDOL configuration file and the IDOL Content Service configuration file To redirect the HP TRIM IDOL log files to an alternative directory to the default C:\HPTRIM, insert the following [paths] statement into the file TRIM IDOL service.cfg: Example: [Paths] Incoming=D:\HPTRIM\IDOL\TRIM IDOL Service\incoming Archive=D:\HPTRIM\IDOL\TRIM IDOL Service\archive Failed=D:\HPTRIM\IDOL\TRIM IDOL Service\failedTasks This is particularly relevant for systems that have limited space on the C: drive. In the event of a problem, the failed directory receives all unprocessed transaction files and this may fill the drive. Database Read-only You can set a TRIM content engine to read-only by adding the following to the TRIM Content service configuration file in the respective Content service under the C:\Program Files\Hewlett-Packard\HP TRIM\IDOL directory. [TRIM_PM] DatabaseReadOnly=TRUE PM represents the database ID of the dataset.

17 Default Operator The default IDOL operator is not strictly an OR, but similar to an OR with calculations that affect relevancy sorting. To change this, in the [Server] section of the file TRIM IDOL service.cfg, add DefaultQueryOperator=<Operator> Example: [Server] DefaultQueryOperator=AND Troubleshooting IDOL Logging in HP TRIM Logs relevant to each content engine Logs relevant to the TRIM IDOL services including DIH and DIH logs Location of the transaction files and working directory for opening compressed files during text extraction: C:\Users\trimservices\AppData\Local\Hewlett-Packard\HP TRIM ServerLocalData on the Workgroup Servers will hold all relevant Workgroup Server, event server and document content indexing (DCI) logs: C:\HPTRIM\ServerLocalData\TRIM\Log

18 Changing the log file locations In the default configuration, the log files are located in C:\HPTRIM. This can be changed in the IDOL configuration files. In the TRIM Content Service configuration files in C:\Program Files\Hewlett Packard\HPTRIM\IDOL\TRIM Content service 1 and 2, the path to the log files is in the section [Logging]: // Logging Settings // [Logging] LogDirectory=C:\HPTRIM\IDOL\TRIM Content Service 1\logs LogTime=TRUE LogOutputLogLevel=TRUE LogLevel=Normal Change the directory to desired location. In the TRIM IDOL service configuration file at C:\Program Files\Hewlett Packard\HPTRIM\IDOL\TRIM IDOL Service.cfg, there is a similar path: // Logging // [Logging] LogDirectory=C:\HPTRIM\IDOL\TRIM IDOL Service\logs LogTime=TRUE Change this path, as well. Removing an IDOL database It is possible to delete an existing IDOL database. DREDELDBASE Enables you to delete all documents from an IDOL Server database. Run from your Internet browser. Example: This command uses port 9001 to delete all documents from IDOL Server's TRIM_45 database. DREDbName The database from which to delete the documents. Note the database is in the format TRIM_DBID. Localhost The name of the DCI server hosting IDOL Note Compact the database using Optimise through TRIM Enterprise Studio after deletion (see section below)

19 Known Issues Restarting Document Content Indexing In some circumstances, TRIM Enterprise Studio may fail during a document content reindex. There can be many reasons and checking the relevant document content indexing (DCI) log files may provide an answer. However, if TRIM Enterprise Studio has stopped responding, you should restart the process where it left off. The first step is to determine approximately how far the indexing process progressed. Examining the DCI logs should give enough information, which is why you should set IDOL to use Verbose Logging. The text of each record is put into a transaction file. Once a transaction file reaches the configured limit, it is transmitted to the IDOL Server (written to the DCI log as Transaction file xxx.txt processed ), and all the contained records will be available for document content searches. If a record is processed, but the reindex ended before the transaction file was processed, IDOL has not received the document, so the record will not be found using a document content search. By starting at the end of the most recent DCI log (located in \ServerLocalData\Log\), it should be possible to determine which was the earliest record that was processed into the last transaction file (the one that was interrupted before it could be transmitted). If the computer has multiple processors, then there will be multiple transaction files being built in parallel. This complicates the process, as you will have to identify the earliest record across all the transaction files. When you have identified the earliest unprocessed record, re-start TRIM Enterprise Studio. Open the Document Content Reindex dialog, and reselect the record URI range. It is advisable to set Start URI to a number around 250 times [the number of computer CPU cores] less then the earliest URI determined above. For example, on a 4-core computer where the last processed record URI was 25,600, start from 24,600. It is better to aim for an overlap in processing than risk missing a record. Insufficient Disk Space The TRIM IDOL content engine requires a minimum of 1024MB of free space for the operation of the content service. This can be changed in the IDOL configuration files. If there is insufficient space when starting the TRIM IDOL Content service, a message Error 1067: The process terminated unexpectedly will appear. During a reindex, a TRIM error DCI server is unreachable will appear. The dih_index.log may also report I/O errors. In normal day-to-day operations, document content indexing is handled through the event processor. If the document content service has insufficient space, the following appears in the event processor log file: 04:54: Error : 21 User: TRIMservices - DCI server TRIMIDOL1 is unreachable. The IDOL application log in the content service\log directory will report that there is insufficient space. To fix this, increase the available space and restart the process.

20 TRIM IDOL database set to read only There may be circumstances where the IDOL services starts up without details of the current HP TRIM IDOL database configuration. In this case, the IDOL service would detect that a database existed that was not in the configuration file and would set the database to readonly (see option above). The read-only database setting is appended to the end of the Content Service configuration file To fix this issue, edit the HP TRIM Content Service configuration files and change the value to False. [TRIM_PM] DatabaseReadOnly=FALSE PM represents the database ID of the dataset. Compacting an IDOL Database When reindexing documents, the IDOL database will continue to grow, particularly the Nodetable files. This is due to the fact that the database is not compacted every time a record is added or reindexed. To force a compacting of the IDOL database, you will need to use the Optimise function within TRIM Enterprise Studio. Open TRIM Enterprise Studio, select the dataset to compact, right-click the dataset name and on the Content Index menu, click Optimise. Options for Improving Initial Indexing of Document Stores The longest process in any installation of HP TRIM IDOL is the initial indexing of the document stores. However, there are a number of ways to optimize performance of the initial indexing process. Ensure that the documents to be indexed do not include unwanted document file types. As indicated earlier, this can be configured in TRIM Enterprise Studio so that unwanted file types are bypassed when determining which records to include in the index. If there are specific record types that do not need to be included, ensure that you have suppressed document content indexing in the options for the Record Type. In TRIM Enterprise Studio, ensure that you have set the maximum size for compressed and standard files. Once you have determined what is to be indexed, you can then spread the indexing load across multiple Workgroup Servers. In previous versions of HP TRIM, it was not possible to process document content from more than one Workgroup Server and write to the same content database. This is not the case with HP TRIM and IDOL. Redundant Workgroup Servers can be configured to process chunks of data at the same time. The Workgroup Servers would be configured separately and not be part of the same deployment. The Workgroup Servers would be set up to be identical and configured to use the same IDOL Server. For the Workgroup Server, virtual machines could be used for this purpose, allowing enough space to handle the text extraction process and processing of any compressed files. The process uses minimal resources to access the database and document stores and should not have an undue impact on production performance.

21 Each Workgroup Server would run as many text extraction processes as it has CPU cores available. HP TRIM IDOL includes a deduplication function so it is not possible to create duplicates for the same document. However, using the Document content options it is possible to setup each Workgroup Server to process a unique set of records. This can be achieved either by using the Date fields to specify a range or by using a URI range. Below is an example Oracle script that could be used to divide the data up into three groups of URIs based on the size of the electronic document stores. This would ensure that they share the load evenly. This script could be modified for SQL Server or to break up the data into the number of groups required. Set serveroutput on; DECLARE CurrentValue NUMBER := 0; RunningSum NUMBER := 0; MaxLimit NUMBER := 0; MaxUri NUMBER := 0; LowerUri NUMBER := 0; UpperUri NUMBER := 0; CurrentUri NUMBER := 0; bset BOOLEAN; BEGIN SELECT Round(Sum(reBytes)/3) INTO MaxLimit FROM TSRECELEC; SELECT Max(uri) INTO MaxUri FROM TSRECELEC; FOR i IN 1..3 LOOP RunningSum := 0; bset := TRUE; LowerUri := 0; UpperUri := 0; LOOP SELECT uri, rebytes INTO UpperUri, CurrentValue FROM ( SELECT * FROM TSRECELEC WHERE uri > CurrentUri ORDER BY uri) WHERE ROWNUM <= 1; IF bset THEN LowerUri := UpperUri; bset := FALSE; END IF; RunningSum := RunningSum + CurrentValue; CurrentUri := UpperUri; IF CurrentUri = MaxUri THEN EXIT; ELSIF RunningSum < MaxLimit THEN CONTINUE; ELSE EXIT;

22 END IF; END LOOP; DBMS_OUTPUT.PUT_LINE ('WGS ' TO_CHAR(i) ' Min Uri = ' TO_CHAR(LowerUri)); DBMS_OUTPUT.PUT_LINE ('WGS ' TO_CHAR(i) ' Max Uri = ' TO_CHAR(UpperUri)); END; END LOOP; When employing this approach, it is important to ensure that the IDOL Server has been correctly sized as discussed earlier to handle the store content.