Overview

To reduce the load on the ProjectWise Application Server machine, a process has been developed to allow the Document Processors to be off-loaded to a second machine. These two machines would then coordinate through the Bentley Orchestration Framework and the Orchestration Framework database.

1. Assuming a pre-existing ProjectWise 8.5.0.80 Application Server with all Document Processors installed.
2. Following the instructions in the ProjectWise Implementation Guide, on a second machine, install ProjectWise Application Server and all prerequisites, including MSMQ, Microsoft Index Server, MicroStation 8.5, Bentley Orchestration Framework.
   • When installing the Bentley Orchestration Framework, be sure to use the same Windows account to run the Shepard service as is being used by the Shepard service on the original ProjectWise Application Server
   • When installing the Bentley Orchestration Framework you will be asked for the database to be used. Select the same database that is being used by the original ProjectWise Application Server. It is also possible at this time to designate a new Orchestration Framework database on the second machine and reconfigure the Orchestration Framework on the original ProjectWise Application server so that it points to this new Orchestration Framework database.
3. On the second machine in which you just installed ProjectWise Application Server edit the dmskrnl.cfg file and add the line FullTextIndexSrv=1 to the [TeamMate] section, so that this machine will not require a ProjectWise App Server license. This will prevent this instance of ProjectWise Application Server from performing any of the real ProjectWise Application Server functionality.
4. Install the ProjectWise Automation Services Administrator client on the original ProjectWise Application Server. Launch it and connect the Orchestration Framework Browser to the database instance used by both machines. You should notice that there are now dispatchers and processors running on both machines. Looking at the monitor for one of the document processor instances you will notice that there are now two parallel sets of dispatchers and processors for that instance that are not connected. Close the ProjectWise Automation Administrator client. Our next step is to connect those parallel paths.
5. On the original ProjectWise Application Server, open a command prompt, navigate to the \ProjectWise\bin\ folder and then type:

   Dmsafpengine.exe -makeHead   
   
   This entry is case-sensitive so be sure to use an uppercase "H".

6. On the second machine, open a DOS prompt and navigate to the \ProjectWise\bin\ folder and then type:

   Dmsafpengine.exe -makeTail   
   
   This entry is case-sensitive so be sure to use an uppercase "T".

7. Reopen the ProjectWise Automation Server Administrator and reconnect to the Orchestration Framework Browser. Select monitor on one of the instances. You should notice that the parallel paths are now connected, the processors have been removed from the original ProjectWise Application Server and the dispatcher from the original ProjectWise Application Server is connected to processors running on the second machine.
8. Using the ProjectWise Administrator client, select Registered Full Text Index Servers and ensure that the second machine shows up in the list. If not, use the New > Index Server to add it. Log in to each datasource and select Document Processors > Full Text Indexing > Properties and make sure that the Index Server field shows the name of the second machine, if not select it from the pick list and click Register Server.
9. Using the ProjectWise Administrator client, select one of the document processors and select a folder for reprocessing and force processing now. Using the ProjectWise Automation Server Administrator validate that the queues of the processors on the second machine are populated with documents for processing.

See Also