Avolve has investigated the .DWX file format and have found this format type to be produced exclusively by a 3^rd party company called CADLock, Inc. (www.cadlock.com). To create a .DWX file, AutoCAD users are required to purchase CADLock’s CADVault Digital Rights Management (only available for the Microsoft Windows operating system) add-on to AutoCAD. The .DWX format that is created “…utilize a proprietary system of adding internal security capabilities…” to the file or group of files. This process is much like putting a password on a .PDF file. If the receiver of these .DWX files do not have a CADVault Runtime license, they are not allowed/unable to open the .DWX file. Because the .DWX is a proprietary file format and the CADVault Runtime application is required to open it, Avolve’s ProjectDox Electronic Plan Review system cannot support this .DWX file format. Avolve also reviewed this with our Brava viewing engine vendor, and they have no future plans to support the .DWX file format.

•  How to find the information for a ticket for HTML Publishing in BESS (internal troubleshooting)

 The info for the ticket is found in data.txt in the dlcache for that file.

•  Subject: 8.4 docs Notes from IGC meeting apache and JP

Apache

The most useful Apache log is: C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\logs\catalina.2014-11-14.log the catalina logs.

Stopping and starting the Apache service clears the cache.

Job Processor

There is no localhost:7070 log for BESS

Avolve converts to XDL 2 times, once to store in UserFilesPublish and once to create a viewable HTML5 file.

For a single page jpg, as an example, if you watch the jpconsole, there are approximately 7 files spawned.

Description

Description

Understanding driver versioning for the ProjectDox Job Processor requires some high level understanding of the lower level component architecture.  The Job Processors are bundled with a component product called CDL (Common Display List).  CDL is a shared component that the Job Processor treats it like its own component.  In addition to the CDL there are several other component level drivers; DGN2DL.DLL, DWG2DL.DLL, LT2DL.DLL and PDF2DL.DLL.  Each component level driver is responsible for publishing different types of files that may be uploaded by ProjectDox users.

Version numbers are structured as "major release"."minor release"."iterative release"."build number." For drivers, that major.minor part is always locked to the lowest version of CDL that is compatible with that driver.

The major.minor version number of the driver can never be higher than the major.minor version of CDL.  It can be equal, but never higher.  For example, in the 7.1.0.11 version of Brava Desktop, CDL version 4.1.0.11 is included. You know that PDF2DL 2.5.16.6 will work with this version of Brava Desktop because 2.5 < 4.1 (PDF version < CDL version).

A CDL's major.minor version would never be upgraded mid-product release, but you might see a big jump in driver major.minor numbers between releases if needed to depend on code within CDL for some driver functionality.

As the CDL major.minor version increases it will always support previous version of the drivers as long as the driver major.minor is never higher.

Solution

To determine CDL's version, check the version of DLConverter.dll on the ProjectDox Job Processor server located in the \Program Files (x86)\Avolve\Job Processor\Job Processor\ root folder or in the \Program Files (x86)\IGC\Brava!\Job Processor\ folder.  In Brava Enterprise 7.1 and older you will find the file in the Job Processor directory. Starting with Brava Enterprise 7.2, check the properties of the file Igc.Cdl.DLConverter.dll instead.

Revised 02-26-2015

Description

Batch Stamps are not published with a Watermark by default when using the Batch Stamp feature of ProjectDox.  In order to get the watermark to show up on the Batch Stamped files, follow the steps described below. 

Solution 

1. On the Job Processor server, in the root of the Job Processor server install folder find the security.xml file and open it with Notepad.

2. Modify the section named <ISOBanners> according to your needs.  In the example below, I’ve highlighted the values that I modified for the City of Boca Raton.  NOTE:  The color setting is in RGB color and you can use tokens in the values.

    

     <IsoBanners>

   <!-- IsoBannerColor only applies to PDF output, not CSF output -->

        <!-- 255,0,0 is a red banner -->

        <IsoBannerColor string="211,211,211" />

    

           <WaterMark string="City Of Boca Raton - %DATE"/>

           <ScreenWaterMark string="City Of Boca Raton - %DATE"/>

           <ScreenBanner string="City Of Boca Raton - %DATE"/>

           <TopLeft string=""/>

           <TopCenter string=""/>

           <TopRight string=""/>

           <LeftTop string=""/>

           <LeftCenter string=""/>

           <LeftBottom string=""/>

           <RightTop string=""/>

           <RightCenter string=""/>

           <RightBottom string=""/>

           <BottomLeft string=""/>

           <BottomCenter string=""/>

           <BottomRight string=""/>

       </IsoBanners>

    

3. Save the file and then take note of the path to the file, i.e. D:\Program Files\Avolve\JobProcessor\, you will need the path to the security.xml file for the next step.

4. On the ProjectDox Web Server, in the \ProjectDox\Integration\Brava\ folder, find the _QueueStampTemplate.txt file and open it with Notepad.

5. Add the following line to the file, right above <AdditionalParams>, using the path noted in Step 3 above:

           Securityxmlfilename=D:\Program Files\Avolve\JobProcessor\Security.xml

6. Save the file.

7. Test by running the Batch Stamp process on some test files and when the publishing has completed, download the PDF and open on your local machine to ensure that the published file has the Watermark displayed as you configured it.

Revised 02-26-2015

Description

Job Processor logging may be turned on to diagnose any publishing problems that may be occurring with the Job Processor. Avolve may ask you to turn on logging for the Job Processor (temporarily) and to reproduce the problem.

It is advised to turn the logging off when the data has been collected (problem reproduced) as it can cause a minor decrease of performance with the Job Processor.

Solution

To enable logging you must go into the Job Processor directory, which is typically E:\Program Files (x86)\IGC\Brava!\Brava! Enterprise JobProcessor.
From within this directory, open the JobProcessor.config file in a text editor (Microsoft Word is not advised as it may add formatting to the text file that will cause issues with the Job Processor).

You will notice near the top of the file that by default:

     log=off

Please simply change "off" to "on," save the file, and then restart the JobProcessor Service. The "log.size=200" is the default maximum amount of jobs that will be reported in the file. Remember you need to restart the service again when you turn logging off (and save the file) after reproducing the problem.

Further down in the file you will notice this section:

     # Log file
     ProcessMonitorLogFile=%temp%\Informative Graphics Corp\IGCMonitorServiceLog.txt
     ProcessMonitorLogFileMaxSizeInMB=1

The ProcessMonitorLogFile= is the location of one of the log files.

**Please note that this is the location of the %temp% folder for the user that the JobProcessor is running as (should be an Administrator account). This means if you are remotely connected to the machine as a user that is not the JobProcessor service user then you will not see the logs in this location and instead need to navigate to the folder for the JobProcessor User.

Usually it is easiest to find this by going to C:\Users\[Job Processor USER]\AppData\Local\Temp\ and then performing a search for "IGCMonitorServiceLog.txt" without quotes. This is because there could be several folders under \Temp\ that the file could be located under.

Search for RIE_NIE under %appdata% for the Job Processor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt and any files in this RIE_NIE folder to Avolve.

The filesize of the log will not exceed 1MB by default unless you modify ProcessMonitorLogFileMaxSizeInMB= to a higher setting which is usually not necessary unless you change log.size= to more than 200 (jobs).

Revised 02-26-2015

Solution 

You can enable Logging on the Job Processor with the below steps:

1. Navigate to the "IGC\Brava! Enterprise .NET\JobProcessor" directory.

2. Open the "JobProcessor.config" in any text editor.

3. Change "log=off" to "log=on".

4. Restart the Brava! Enterprise .NET JobProcessor service.

When issues occur, please provide the following log files:

1. A copy of the "WebServer0.xml" logs (Generally located in the "C:\Windows\Temp\Informative Graphics Corp\BravaEnterprise.net\logs" directory)

2. A copy of the "rie_nie" logs (Generally located in the "C:\Users[Service_Account]\AppData\Local\Informative Graphics Corp" directory)

This will provide Avolve Support the information needed to see what the Brava Viewing Server and Job Processor are doing before, during, and after the issue occurs. 

Revised 02-26-2015

Description

This will explain how to resolve the issue where the Job Processor service will not start, but other Brava services will.

This occurs with the following:

     Brava Type: Brava Enterprise .NET 7.1 and earlier

If all Brava services are able to start except the Brava Job Processor, this is usually related to the service account that is being used to logon the service, typically named NetItSvc. This means that the user that installed Brava Enterprise .NET is different from the user being used as the service account.

Solution

In order to resolve this, you will need to either change the service account to the user that installed Brava Job Processor or reinstall Brava Enterprise .NET Job Processor application as the user that will be running as the service account, in a typical installation, the NetItSvc account. 

The NetItSvc and the PD_USR accounts should be created on the machine as a Local Administrators prior to the installation of the Job Processor application.

Revised 02-26-2015

To be able to retrieve the Job Processor Log files, each Job Processor must first have logging enabled.  To enable JobProcessor logging, follow the directions listed in the KB below

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=62322277&objAction=ArticleView

To obtain the JobProcessor logs, search for RIE_NIE_logfile.xml under %appdata% for the JobProcessor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt (if the JobProcessor does not work at all) and any files in this folder. Typically, the folder that has the RIE_NIE_logfile.xml is:

 C:\Users\JOB_PROCESSOR_USER\AppData\Local\Informative Graphics Corp

The filesize of the log does not exceed 1MB by default unless you modify ProcessMonitorLogFileMaxSizeInMB= to a higher setting which is usually not necessary unless you change log.size= to more than 200 (jobs). You can safely set this up to 32MB.

NOTE: When saving at any time after the first save, each of the originally included files must be populated with at least one markup. Saving with any of the drawings empty of markups disables future saves.

Lately we have been seeing some “Invalid server license errors” when trying to view files in non-Internet Explorer browsers. Below is a list of recommendations in order to fix these problems.

•          Applicable to ProjectDox 8.3 and greater - Make sure there are no spaces in your license keys for both Brava Server and Brava Enterprise Client License, located in IGCKey.lic file on the web server. Move your cursor to the end of the key, click the right arrow button and if it does not go to the next line, then it means you have an extra space and it must be deleted (can be done by simply hitting backspace). The new Salesforce license system adds the extra space when copying so it is important to check this every time you copy a new license.
•          Applicable to ProjectDox 8.3 and greater - After modifying, editing, or replacing the license you must reboot the web server in order for the changes to take effect. First, stop the Job Processor services, then stop Brava service(s), delete DLCache, reboot the web server. Once the web server is up, start the Job Processor service and test viewing files in non-IE browsers again.

Job Processor Optimizing Number of Threads to Process

The recommended starting point when updating the threads for each Job Processor is as follows: As a rule of thumb starting point, the total number of threads below should be 2-3 times the number of logical cores on the JP machine.  For example, if the machine runs a quad-core processor and has hyperthreading or similar technology enabled, you might start with a total of 2-3 x (4 x 2) = 16-24 threads. If hyperthreading is unavailable or disabled, then you might start with a total of 2-3 x 4 = 8-12 threads.

This number is just a starting point, and will vary depending on number of different kinds of files, their sizes, file I/O bandwith and the variability of the load on the JP.

Doc can be set to a 2 and only on the Job Processor that has Office installed. If Office is installed on only one Job Processor, then the PRQ and DOC threads must be set to zero on the server without Office. PRQ is used for unidentified files and an Office file will be unidentified without Office present.

Description

Brava scalability touches many parts of the system, including the integration in which Brava runs.   This section covers scalability and fault tolerance of the Brava system itself. Integration scalability is covered in a separate section.

Solution

The attached white paper that was released by the makers of ProjectDox Publishing Engine, Informative Graphics, provides a very good understanding of the architecture used for the publishing paradigm in ProjectDox.

Revised 02-18-2015

Description

Certain configurations of Windows 2008 R2 may experience a memory leak in the "WinHTTP Web Proxy Auto-Discovery Service" (WinHttpAutoProxySvc) when the Job Processor is running. Microsoft is aware of this issue and Informative Graphics is working closely with Microsoft to provide a fix. However, at the time of release this fix is not yet available.

Solution

If you are experiencing memory growth in the WinHTTP Web Proxy Auto-Discovery Service on a 2008 R2 machine running a Job Processor, you can work around this issue in one of two ways:

1. Configure the WinHTTPAutoProxySvc to run in its own process. Open a command prompt and enter the following commands:

     sc stop "WinHTTPAutoProxySvc"
     sc config "WinHTTPAutoProxySvc" type= own
     sc start "WinHTTPAutoProxySvc"

2. Disable the WinHTTPAutoProxySvc. This will not affect the operation of the Job Processor, but may affect other components on the machine. To do this, open a command prompt and enter the following commands:

     sc stop "WinHTTPAutoProxySvc"
     sc config "WinHTTPAutoProxySvc" start= disabled

This will stop and disable the service.

In either case, If you've experienced memory growth, you'll have to reboot the machine to clear up the memory.

Revised 02-18-2015

• In BESS 7.2 BEN 71159 mydrv.ini this value MaximumPageDimension=1000000000,1000000000 only affects measurements and not the reflected page side. It no longer affects the scaling. That is why we did not see any difference when changing this to 80,300 which used to correct. If this value is changed it will throw off measurement.

• In BESS 7.3 mydrv.ini this value MaximumPageDimension=1000000000,1000000000 is not in the product.

Adam is not coding anything that retrieves page size. It is a black box in the JP concerning sheet size calculations, I checked with him. LB

cdl=true

forcetojpg=true

jpgfidelity=75

MaxRasterDPI=600

embedtruetypefonts=false

ForceEmbedTruetypeFonts=false

MaximumPageDimension=1000000000,1000000000

NonConcurrentLoaders=dui2dl.dll;dwg2dl.dll

MaxPageCount=5000

If Apache does not start on the web server, it may be that Java was updated automatically, and changed the path.

1)     It is important to disable the Java Updates when you install. 

Please see attached image.

If you encounter the error "There was a failure downloading the Integration Dll! Please check the IntegrationUrl BravaXParam," there may be an issue with the User Account Access. For troubleshooting steps, see attached document.  

Description

Customers with anti-virus installed on the ProjectDox Servers must enable the following exclusion rules in any scanning utilities installed to prevent issues with the function of the software.  Avolve recommends that only the PdoxTemp folder be scanned in real-time.  All other ProjectDox application folders and supporting folders, including all sub-folders, should be excluded from anti-virus applications real-time scanning.  A nightly scan of the directories is acceptable.  It is not recommended to have anti-virus installed on the Job Processors.  Avolve cannot guarantee the operation of the Job Processors with anti-virus installed on the servers and, in the event issues occur with publishing, the first recommendation will be to remove the anti-virus application from the Job Processors and perform a full reboot.  Perform testing after the Job Processor has been rebooted to see if the issue is resolved.  

Solution

Avolve recommends setting up exclusion rules for the folders specified below on the ProjectDox servers indicated.  Assuming the Operating System is installed on the C:\ drive and the ProjectDox, related services and Brava applications are installed on the E:\ drive, you would want to exclude the following folders, including any sub-folders, on the ProjectDox servers.  A list of common Share Folder Names used by ProjectDox is provided below.

• UserFilesSource or UFS - Stores original files uploaded by users
• UserFilesPublish or UFP - Stores published ActiveX version of files uploaded by users
• DLCache - Stores published HTML version of files uploaded by users
• Queue - Stores Job Tickets created for publishing requests for the Job Processors
• PdoxLogs or Logs - Stores Archive PDFs if using ProjectDox Archive Feature
• PdoxExport or Export - Stores Exported Projects until retrieved by EDMS solution
• WFlowDLLCache - Stores ProjectFlow workflow instance DLLs for active workflows

• PdoxTemp - All uploaded files are stored in this folder first before being moved to the UserFilesSource folder.  This folder should not be excluded as it is the single point of entry for any new files uploaded to ProjectDox and should be scanned in real-time.

NOTE:  Some anti-virus applications may need an additional exclusion rule enabled for .rtf file types.  If you experience trouble with missing Markups or Changemarks within the workflow, then please try adding the exclusion rule for file types of .rtf and see if that resolves your issue.  Markups and Changemarks are saved to the PdoxTemp folder temporarily and some anti-virus applications will false alert and remove the .rtf file causing saved Markups and Changemarks to not show up in the workflow.

Job Processors

     C:\Windows\system32\spool\PRINTERS\  

     C:\Windows\Temp\  **  (see additional info below)

     C:\Users\NetItSvc\AppData\Local\Informative Graphics Corp\

     C:\Users\NetItSvc\AppData\Local\Temp\

     C:\Users\NetItSvc\AppData\Roaming\Informative Graphics Corp\

     C:\ProgramData\IGC\  (Brava 16.2 and 16.4)

     C:\ProgramData\OpenText\  (Brava 16.6 and up)

     E:\Program Files (x86)\IGC\   

     E:\Program Files (x86)\Avolve\    

     E:\Program Files\IGC\   

     E:\JPTemp\  **  (see additional info below)

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)


Web Server

     w3wp.exe Process

     E:\ProjectDox\     (Superion customers may see E:\EPR instead of E:\ProjectDox)

     E:\ProjectDox.Web.API

     E:\ProjectDox.Web.UI

     E:\Program Files (x86)\Avolve\   

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)


Application Server

     E:\Program Files (x86)\Avolve\

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)



NOTE *

ProjectDox file share folders may exist on any ProjectDox server, Network Storage Device or stand-alone File Server. 
The PdoxTemp folder is the single entry point of new files to the server and therefore it is recommended to scan this folder only in real-time.  A nightly scan can be performed of the folders if desired.
Exclude all share folders with the exception of PdoxTemp from real-time scanning. 

ADDITIONAL INFO **

     If you are unable to exclude C:\Windows\Temp on the Job Processors, you can update the system output path of the IGC Writer Print driver and use a different directory for example E:\JPTemp.

To do this:

1. Create a folder on the E:\ drive named JPTemp
2. Grant Full Control under the Security Options for the folder, to the PD_USR and NetISvc accounts
3. In the Control Panel Printers and Faxes panel, right-click on the CSF Writer printer and select Properties
4. Select the Advanced tab
5. Click the Printing Defaults... button
6. Select the Filename Generation tab
7. Change the Output Directory path to the following:  E:\JPTemp
8. Click OK to save your settings.

Then add an exclusion rule for the E:\JPTemp folder on the Job Processors in place of the C:\Windows\Temp folder

SQL Server

Antivirus exclusion on SQL files:

When you configure antivirus software settings, make sure that you exclude the following files or directories on SQL Server machine from virus scanning. Doing this improves the performance of the files and helps make sure that the files are not locked when the SQL Server service must use them. However, if these files become infected, your antivirus software cannot detect the infection. 

Dynamic Stamp Tokens

Brava Stamp Tokens

%Date Inserts the date the print was spooled. If the tags are viewed on screen, the time at which the screen was last refreshed displays.

% SysDatePlusDays(x) Inserts a date the specified number of days past the system date. Replace "x" with the desired number of days. Negative numbers of days may be entered. Be sure to close the parenthesis when you add the number of days.

%Time Inserts the time the print was spooled based on a 12 hour clock (AM/PM). If the tags are viewed on screen, the date on which the screen was last refreshed displays.

% MilTime Inserts the time the print was spooled based on a 24 hour clock.

%Title Inserts the name of the document.

%Page Inserts the page number.

% TotalPages Inserts the total number of pages.

%batespgno(x) Bates Number - This tag is used to indicate the starting page number and the number of digits to use. For example, %batespgno(0002) would place 0002 on the first page, 0003 on the next page, etc.

%Login (or %User) - Specifies the user name of the person who issued the print.

%Hostname - Specifies the hostname of the machine that issued the print.

%IPAddress - Specifies the IP Address of the machine that issued the print.

%% - Inserts a single % character.

© - Inserts the copyright symbol.

® - Inserts the registered trademark symbol.

%prompt("Label_String") Used in a token expression when creating a stamp template. When set, a prompt dialog displays to the end-user prompting them to manually edit a markup stamp's text string during review process. When this token is used, the prompt dialog displays when a user initially inserts the markup stamp and at any time the stamp is double clicked. The dialog contains a text entry field value which can be updated at any time before the markup is finalized through publishing. Unlike %DBUpdateString, the %prompt tokens will NOT be sent to the integration database for resolution and may not be customized for integrations.

Note that a ":" character will be automatically added to the end of LABEL_STRING in %prompt(LABEL_STRING) when displaying the caption to the user. For example, %prompt(Enter amount) means that the user will see a prompt box with the caption "Enter amount:" and a text entry field to type in the requested information.

%DBString(x) This tag is used to resolve custom tags for products that integrate with Brava!. Replace "x" with any printable character except a right parenthesis, ")". See notes below.

%DBUpdateString(field label) Used when creating Stamp Templates to resolve custom integration values during the review process. This tag inserts a corresponding field label value (Priority, Status, etc.) from the integration's database tables when a user either inserts a markup stamp, or double clicks on a markup stamp containing a %DBUpdateString token in the markup text string. The method for resolving these tokens is determined by the integration's needs, and can include using a dialog or a non-interactive method. If %DBUpdateStrings are not resolved, they are given a default answer which is displayed with the resulting markup stamp.

Notes:

• Tag values are case insensitive. Also, all the tags except %% and %SysDatePlusDays(x) must be followed by a non-alphanumeric character (such as a space, a %, a comma, a slash) otherwise, they are interpreted as text strings.

• A Bates Number is considered to be both the prefix and the page number WITH leading zeros. To create a Bates ID, you can add text preceding the tag. For example, Smith vs. Jones%batespgno(00001) would result in Smith vs. Jones000001 being printed on the first page, Smith vs. Jones000002 printed on the second page, etc.

• Using the %DBString(x) macro allows you to incorporate database attributes into your ISO Banner and watermarks. For example, the following show the resulting printed string of various typed input:

Input: This document was created on %DBString(r_creation_date) by %DBString(owner_name).

Output: This document was created on 11/15/2011 by John Johnson.

Input: Document "%DBString(object_name)” was modified by %DBString(r_modifier) on %DBString(r_modify_date).

Output: Document "neo.doc” was modified by Pat McDonald on 1/12/2012.

Input: Reviewed and Approved, Version %DBString(r_version_label)

Output: Reviewed and Approved, Version 1.6