Dashboard Installations & Troubleshooting Guide

Transcription

1 Dashboard Installations & Troubleshooting Guide Last Revision Date: October 29, 2009 Last Revision Date: October 29, 2009

2 Table of Contents Table of Contents...2 How to install Dashboard & Dashboard Purge Service (OpenVMS)...3 CONNX Installation Instructions:...5 Details of the CONNX Installation...6 How to install Dashboard (OpenVMS)...20 How to install the Dashboard Purge Service (OpenVMS)...22 How to install Dashboard & Dashboard Purge Service (Oracle)...24 How to install Dashboard (Oracle)...24 How to install the Dashboard Purge Service (Oracle)...26 How to install a Dashboard Patch...29 Installation s for loading a Dashboard Patch...29 Dashboard Troubleshooting Tips...32 Problem: The Dashboard Banner comes up on the screen, but nothing else. How do I turn on logging?...32 Problem: License looks good but it doesn t seem licensed Problem: How to change how often the purge process runs DB-2

3 How to install Dashboard & Dashboard Purge Service (OpenVMS) Overview Before installing Dashboard and the Dashboard Purge Service, you must install CONNX. Then the two programs need to be installed and configured: 1. Dashboard 2. Dashboard Purge Service There are three directories on the CD involved in installing these programs: ConnxCDD This directory holds the data dictionary used to map the CONNX database bridge to RMS files sitting on a VMS machine. This is necessary when installing the CONNX gateway on to a Window Server. DashboardInstaller This directory holds the setup program for installing the Dashboard program on a client machine. It also currently holds a canned dashboard.properties file (configuration file). This file needs to be reconfigured with the correct IP address of the CONNX gateway, username, password, and so on. An instruction on the specific editing that needs to be done is provided in the tables below. DashboardPurge This directory holds the background purge program that is installed on some Window Servers to periodically clean out stale data. Procedures The following steps describe the order of installation for Dashboard. 1 Install CONNX with CONNX Installation Instructions (see below). Note: The license service is a bit tricky. CNXLIC.DAT is the license for a multi-user customer. TPS Dashboard.CDD is the CONNX dictionary for Dashboard RMS. 2 How To Install Dashboard describes how to install the graphic user interface for Dashboard. 3 How to Install Dashboard Purge describes how to install the GUI for the Dashboard Purge. DB-3

4 4 The Dashboard Training document is end-user documentation. 5 The installation kit for just the Dashboard can be found here: \\tpsint2\temptps\dashboard\kit. DB-4

5 CONNX Installation Instructions: Thank you for using CONNX. Enclosed is your download password for CONNX Please note that before downloading CONNX 10.5, a license server will need to be installed. In order to perform this installation, please follow the instructions found at the link listed below as Installing CONNX License Server Technology. Also included are a few other links that may be of assistance. Please visit the CONNX website at for the latest CONNX news, recent updates, and future products. Password: Download Page: DataSync Download: Installing CONNX License Server Technology: CONNX 10.5 Manuals and Release Notes: CONNX User Reference and Installation Guides: Sportster These guides can also be found on the CONNX CD-ROM and in the CONNX software applications. DB-5

6 Details of the CONNX Installation CONNX Installation screen: 1 From the connx install, accept the user agreement, then press the Yes> button to continue, the CONNX Location screen (below) will display. DB-6

7 CONNX Location screen: 2 On the CONNX Location screen, type in the correct path for installation. Note the amount of disk space available on your Windows Server before proceding. Then press the Next> button. DB-7

8 Database Modules screen: 3 On the Database Modules screen, select the following: RMS Install License Source (on local Window server) Install CONNX License server on local computer Then press the Next> button. DB-8

9 Select Components screen: 4 From the Select Components screen, select the following options: CONNX Client Driver CONNX Help and Samples CONNX JDBC Server OpenVMS Server Components Then press the Next> button to continue. DB-9

10 CONNX NT/2000 Service screen: 5 For your Window server, CONNX License Manager, use a privileged username/password. 6 Check the License Service to make sure it started. CONNX Server Component Installation screen: DB-10

11 7 The CONNX Server Component Installation screen shows the connection info used for FTP of the Alpha server listener side of the installation. 8 Click the Install button. 9 If the FTP worked correctly, you will get an Installation Successful message (below). Installation Successful pop-up screen: 10 On the Installation Successful pop-up screen, click the OK button. 11 Log into the Alpha server, if previous was successful. 12 If a new installation of 10.5 and never had a previous version of CONNX installed, type in the following: Live Force> Creat/dir/prot=(wred) SYS$COMMON:[CONNX] Live Force> Create SYS$COMMON:[CONNX]test.test (then ctrl z) Live_Force> dir cn* Directory SYS$SYSDEVICE:[CULLITY] CNXCLEAN.COM;1 2/4 28-MAR :20:29.63 CNXDBMA0.COM;1 6/8 28-MAR :20:29.83 CNXHOTA0.OLB;1 319/ MAR :20:36.57 CNXIMAGE.COM;1 3/4 28-MAR :20:30.01 CNXINST.COM;1 1/4 28-MAR :20:42.19 CNXLOGIC.COM;1 1/4 28-MAR :20:30.22 CNXRDBA0.COM;1 6/8 28-MAR :20:30.44 CNXRMSA0.COM;1 6/8 28-MAR :20:30.63 CNXRMSA0.OLB;1 3445/ MAR :20:37.46-COM-D0-01/10/92 CNXRUNA0.OLB;1 1206/ MAR :20:35.04 CNXSETUP.COM;1 23/24 28-MAR :20:30.82 CNXSVR.COM;1 9/12 28-MAR :20:31.04 DB-11

12 Total of 12 files, 5027/5052 blocks. $ SET NOON $ if f$search("cnxsetup.log").nes. "" then del CNXSETUP.LOG;* $ DEFINE CNX$SCR _FORCE$RTA2: /nolog $ OPEN /WRITE /SHARE CNX$SCREEN CNX$SCR $ DEFINE SYS$OUTPUT CNXSETUP.LOG /nolog Installing CONNX for RMS Creating CONNX Directory in SYS$COMMON:[CONNX] Defining CONNX Logicals Setting protections on SYS$COMMON:[CONNX] components Copying CONNX common server files %LINK-W-MULDEF, symbol DECC$ NW XUI multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXRUNA0.OLB;1 %LINK-W-MULDEF, symbol DECC$ DL XPV multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXRUNA0.OLB;1 %LINK-W-WRNERS, compilation warnings in module CNETTCP file SYS$SYSDEVICE:[CULLITY]CNXRUNA0.OLB;1 %LINK-W-NUDFSYMS, 1 undefined symbol: %LINK-I-UDFSYM, WRITEHEXOUT 6HEXTRCXPVIPVIIII %LINK-W-MULDEF, symbol DECC$ NW XUI multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXHOTA0.OLB;1 %LINK-W-MULDEF, symbol DECC$ DL XPV multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXHOTA0.OLB;1 %LINK-W-NUDFSYMS, 19 undefined symbols: %LINK-I-UDFSYM, CNXRLECOMPRESS XPKCPCLNLL %LINK-I-UDFSYM, CNXRLEDECOMPRESS XPKCPCLNLL %LINK-I-UDFSYM, CONNX_ISSPACE_ARRAY %LINK-I-UDFSYM, HASH_BJ XPUCUI %LINK-I-UDFSYM, HASH_DJB64 XPUCUI %LINK-I-UDFSYM, HASH_FNV XPUCUI %LINK-I-UDFSYM, HASH_FUNCTION %LINK-I-UDFSYM, HASH_NOTHING XPUCUI %LINK-I-UDFSYM, HASH_OY64 XPUCUI %LINK-I-UDFSYM, HASH_OY_DJB_NEW XPUCUI %LINK-I-UDFSYM, HASH_OY_DJB XPUCUI %LINK-I-UDFSYM, HASH_UMAC64 XPUCUI %LINK-I-UDFSYM, MID K11CFASTSTRINGXII %LINK-I-UDFSYM, PSZEMPTY 11CFASTSTRING %LINK-I-UDFSYM, UMAC_DELETE %LINK-I-UDFSYM, UMAC_FINAL %LINK-I-UDFSYM, UMAC_NEW %LINK-I-UDFSYM, UMAC_RESET %LINK-I-UDFSYM, UMAC_UPDATE %LINK-W-USEUNDEF, undefined symbol PSZEMPTY 11CFASTSTRING referenced in psect $LINK$ offset %X in module CNXHOT file SYS$SYSDEVICE:[CULLITY]CNXHOTA0.OLB;1 %LINK-W-USEUNDEF, undefined symbol PSZEMPTY 11CFASTSTRING referenced in psect $LINK$ offset %X000001E0 in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXHOTA0.OLB;1 %LINK-W-USEUNDEF, undefined symbol PSZEMPTY 11CFASTSTRING referenced in psect $LINK$ offset %X in module DEBUG file SYS$SYSDEVICE:[CULLITY]CNXHOTA0.OLB;1 Copying CONNX RMS server files %LINK-W-MULDEF, symbol DECC$ NW XUI multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXRMSA0.OLB;1 %LINK-W-MULDEF, symbol DECC$ DL XPV multiply defined in module NONDEBUG file SYS$SYSDEVICE:[CULLITY]CNXRMSA0.OLB;1 %LINK-W-WRNERS, compilation warnings in module CNETTCP file SYS$SYSDEVICE:[CULLITY]CNXRMSA0.OLB;1 Creating RMS sample data files %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]EQUIPMNT.FDL;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]EQUIPMNT.SEQ;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]PRODGRP.FDL;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]PRODGRP.SEQ;1 created DB-12

13 %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]PRODUCT.FDL;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]PRODUCT.SEQ;1 created %DELETE-I-FILDEL, SYS$SYSDEVICE:[CULLITY]PRODUCT.FDL;1 deleted (4 blocks) %DELETE-I-FILDEL, SYS$SYSDEVICE:[CULLITY]PRODUCT.SEQ;1 deleted (16 blocks) %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]ORDER.FDL;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]ORDER.SEQ;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]CUSTOMER.FDL;1 created %CREATE-I-CREATED, SYS$SYSDEVICE:[CULLITY]CUSTOMER.SEQ;1 created Setting protections on SYS$COMMON:[CONNX] components ******************************************** CONNX for RMS has installed successfully! ******************************************** %DCL-I-SUPERSEDE, previous value of CNXLOCALIP has been superseded Setup Complete Setup Complete Live_Force> 13 If successful, note that you will see the messages (CONNX for RMS has installed successfully!) on the screen (see example above). 14 Next, take the CNXLIC.DAT, call it CNXRMS.DAT and FTP it into the CNXDIR folder on your VMS server. 15 Also on every CONNX install, using EDIT add the following lines to SYS$MANAGER:SYSTARTUP_VMS.COM, near the end. $! Commands needed for CONNX ODBC Driver $ DEFINE/SYSTEM CNXSVR SYS$COMMON:[CONNX]CNXSVR.COM $ DEFINE/SYSTEM CNXDIR SYS$COMMON:[CONNX] $ DEFINE/SYSTEM CNXRMS SYS$COMMON:[CONNX]CNXRMS.COM $ DEFINE/SYSTEM CNXRMSA0 SYS$COMMON:[CONNX]CNXRMSA0.COM START 16 Click START, CONNX, CONNX License Manager and check the license (CONNX License Administrator screen below). Note: Make sure the CONNX license service has started before going to the CONNX License Administrator screen. Also make sure the CONNX JDBC Service is running, too. DB-13

14 CONNX License Administrator screen: 17 On the CONNX License Administrator screen, make sure the license appears. Note: You might need to use the Install or update from license file option button to the right. CONNX Data Source Setup screen: DB-14

15 18 You ll need to add an ODBC system DSN on the CONNX Data Source Setup screen. 19 It will look like the ODBC Data Source Administrator screen below once it is complete. ODBC Data Source Administrator screen: DB-15

16 InfoNaut The CONNX Query Tool screen: 20 Use InfoNaut to test the connection to the RMS database. The! (exclamation point icon in the toolbar) executes the command string. Note: You may need to add a connection from the Connection tab (top of screen). 21 The successful query should look like the screen below. InfoNaut The CONNX Query Tool screen -- Example of Successful Query: DB-16

17 CONNX Data Dictionary Manager screen: 22 Be sure to set within the CONNX Data Dictionary Manager "read only" if you are using CONNX with the Import dictionary (and not the Dashboard dictionary). Set this way you can insure that no one will write back to the RMS files on the Alpha server. Also the IP address for the Alpha server resides within the CONNX Data Dictionary Manager: DB-17

18 Alliance User Profile Maintenance screen: 23 Add CONNX to the Alliance User Profile Maintenance, if it doesn t already exist. Make sure you enter the Password 5D68d832 (which is password encrypted). DB-18

19 CONNX Data Source Name Registry screen: 24 Add the Connx DSN Source Name Registry. DB-19

20 How to install Dashboard (OpenVMS) Procedures The following steps describe how to install Dashboard. 1 Run the Dashboard Setup program from the CD: Dashboard-setup.exe 2 Accept the default installation. C:\Program Files\Dashboard Note: If customer does not want software installed onc: or in Program Files, enter the alternate installation location. (For example:g:\dashboard ) 3 Browse to the following location (if you accepted the default location): C:\Program Files\Dashboard\conf If an alternate location was used in step 2 above, enter the alternate location followed by \conf. (For example: G:\Dashboard\conf ) 4 Within that directory, edit the following file: dashboard.properties 5 Set Dashboard to be the actual CONNX DSN that was previously set up. 6 Set to be the actual IP address of the Windows box where Dashboard is installed. 7 Specify a username. Note: This is the username on the customer s OpenVMS. This account will be used by Connx to connect Dashboard to the Alliance database. 8 Specify a password. Note: This is the password on the customer s OpenVMS. This account will be used by Connx to connect Dashboard to the Alliance database. DB-20

21 9 Additionally, make sure the following settings are set as below: db.acquireincrement=1 db.initialpoolsize=1 db.maxidletime=3600 db.maxpoolsize=1 db.minpoolsize=1 db.numhelperthreads=1 db.sql.show=false db.sql.format=true 10 Next, you must install the Dashboard Purge service. [Procedures can be found below.] DB-21

22 How to install the Dashboard Purge Service (OpenVMS) Installation Procedures There is no installer for the Dashboard Purge service. Instead, on the Windows Server, follow the steps below. Note: Make certain that any file that you need to edit in the steps below must be able to be written to (e.g., no write protection). 1 Create a directory. C:\Program Files\DashboardPurge 2 From the CD, copy the five directories under the CD s DashboardPurge directory to 3 Browse to C:\Program Files\DashboardPurge C:\Program Files\DashboardPurge\conf 4 EditdashboardPurge\conf\wrapper.conf And edit the following line to point to the java.exe (wherever the java runtime is installed on that box): wrapper.java.command=c:/program Files/Java/jre1.5.0_10/bin/java.exe Note: If there is no java runtime on the box, you can install it from the kit: DashboardPurge\JRE 5 Edit the following file: hibernate.cfg.xml 6 Change the Dashboard DSN name to be the configured CONNX DSN. 7 Change the IP address to be the IP address of where the CONNX JDBC service resides. 8 Specify a username. Note: This is the username on the customer s OpenVMS. This account will be used by Connx to connect Dashboard to the Alliance database. DB-22

23 9 Specify a password. 10 Browse to Note: This is the password on the customer s OpenVMS. This account will be used by Connx to connect Dashboard to the Alliance database. C:\Program Files\Dashboard\bin 11 Run the following batch file (which installs the Dashboard Purge as a Windows service): InstallGlobalPointAdapter-NT.bat 12 Go to the Windows Service applet under the Windows Control Panel. 13 Look for Dashboard Purge in the list. 14 Set the service to be Automatic. 15 Start the service. DB-23

24 How to install Dashboard & Dashboard Purge Service (Oracle) Overview There are two programs that need to be installed and configured: 1. Dashboard 2. Dashboard Purge Service The two directories on the CD/kit that are involved in installing these programs: DashboardInstaller This directory holds the setup program for installing the Dashboard program on a client machine. It also currently holds a canned dashboard.properties file (configuration file). This file needs to be reconfigured with the correct IP address, username, password, and so on. An instruction on the specific editing that needs to be done is provided in the tables below. DashboardPurge This directory holds the background purge program that is installed on some Window Servers to periodically clean out stale data. Procedures The following steps describe how to install Dashboard. How to install Dashboard (Oracle) 1 Run the Dashboard Setup program from the CD: Dashboard-setup.exe 2 Accept the default installation. C:\Program Files\Dashboard Note: If customer does not want software installed onc: or in Program Files, enter the alternate installation location. (For example:g:\dashboard ) DB-24

25 3 Browse to the following location (if you accepted the default location): C:\Program Files\Dashboard\conf If an alternate location was used in step 2 above, enter the alternate location followed by \conf. (For example: G:\Dashboard\conf ) 4 Within that directory, edit dashboard.properties # TPS Deringer Oracle Database db.driver=oracle.jdbc.driver.oracledriver 5 Set the actual IP address of the Oracle box where the Oracle Database is installed. db.url=jdbc:oracle:thin:@oracle-ip:oracle-port:oracle- SID-OR-SERVICE-NAME Note:ORACLE-IP is the IP Address of the machine where Oracle is installed. ORACLE-PORT is the Oracle Port number. ORACLE-SID-OR-SERVICE-NAME is the Oracle database ID or name of service. 6 Specify a username. db.username=oracle-username Note: This is the Oracle connection username. 7 Specify a password. db.password=oracle-password Note: This is the Oracle connection password. 8 Additionally, set the following: db.dialect=com.kewill.base.db.oracledialect db.hbm.loc=oracle DB-25

26 9 Additionally, make sure the following settings are set as below: db.acquireincrement=1 db.initialpoolsize=1 db.maxidletime=3600 db.maxpoolsize=5 db.minpoolsize=1 db.numhelperthreads=2 db.sql.show=true db.sql.format=true cglib.use_reflection_optimizer=true 10 Next, you must install the Dashboard Purge service. [Procedures can be found below.] How to install the Dashboard Purge Service (Oracle) Installation Procedures There is no installer for the Dashboard Purge service. Instead, on the Windows Server, follow the steps below. Note: Make certain that any file that you need to edit in the steps below must be able to be written to (e.g., no write protection). 1 Create a directory. C:\Program Files\DashboardPurge 2 From the CD, copy the five directories under the CD s DashboardPurge directory to C:\Program Files\DashboardPurge 3 Browse to C:\Program Files\DashboardPurge\conf DB-26

27 4 Set the Hibernate Connection URL by editinghibernate.cfg.xml 5 Set the actual IP address of the Oracle box where the Oracle Database is installed. <property name="hibernate.connection.url">jdbc:oracle:thin:@oracle -IP:ORACLE-PORT:ORACLE-SID-OR-SERVICE-NAME</property> Note:ORACLE-IP is the IP Address of the machine where Oracle is installed. ORACLE-PORT is the Oracle Port number. ORACLE-SID-OR-SERVICE-NAME is the Oracle database ID or name of service. 6 Next, set the following: 7 Specify a username. <property name="hibernate.connection.driver_class"> oracle.jdbc.driver.oracledriver</property> <property name="hibernate.connection.username">oracle- USERNAME</property> Note: This is the Oracle connection username. 8 Edit the Adapter.xml Change connx to oracle for database type 9 Specify a password. <param key='databasetype' value='connx' /> <param key='databasetype' value='oracle /> <property name="hibernate.connection.password">oracle- PASSWORD</property> Note: This is the Oracle connection password. 10 Additionally, set the following: <property name="hibernate.connection.pool_size">10</property> <property name="hibernate.connection.provider_class"> com.tps.adapter.pool.oracleconnectionpool</property> <property name="hibernate.connection.fixed_string">true </property> 11 Edit wrapper properties. # Wrapper Properties #************************************************************* ******* # Java must be included in the path or include a fully DB-27

28 qualified executable # of java.exe. #wrapper.java.command=../../program files/java/jre1.5_0_10/bin/java.exe wrapper.java.command=c:/program Files/Java/jre1.5.0_10/bin/java.exe #JDBC driver 12 Browse to wrapper.java.classpath.11=../lib/connxjdbc.jar #wrapper.java.classpath.11=../lib/ojdbc14.jar C:\Program Files\Dashboard\bin 13 Run the following batch file (which installs the Dashboard Purge as a Windows service): InstallGlobalPointAdapter-NT.bat 14 Go to the Windows Service applet under the Windows Control Panel. 15 Look for Dashboard Purge in the list. 16 Set the service to be Automatic. 17 Start the service. DB-28

29 How to install a Dashboard Patch Overview There are four (4) directories in the distribution: Directory ConnxCDD DashboardInstaller DashboardIndividualJars DashboardPurge Brief Description Holds the latest version of the CONNX data dictionary Holds the actual dashboard setup/installation program dashboard-setup.exe Holds the 4 main Dashboard related Jar files. These are already part of the installer above, but if the fixes are limited to these jar files only, it may be convenient to have these 4 jar files as_is in case you simply want to drop them into an existing installed version of the dashboard. This method eliminated the need to re-install again. For this patch, these files are identical to the ones in Dashboard Installer above and do not need to be used. Holds the directories, files, and batch scripts used to set up the dashboard purge windows service. Procedures The following steps describe how to install a Dashboard patch. Installation s for loading a Dashboard Patch 1 Please ensure that theexisting dashboard.properties file is backed up if you are doing a re-install of Dashboard (as opposed to simply just copying the updated JAR files into an existing instance of the Dashboard). The Dashboard installer does not detect an existing installation and will overwrite dashboard.properties. For example, to back it up copy Dashboard.properties toold_dashboard.properties in My Documents folder. dashboard.properites contains the settings on how/where to connect to CONNX. Once you re-run thedashboard-setup.exe from Dashboard installer (described in 11 below), copy the backed up DB-29

30 dashboard.properties back (In the example above, copy back the old_dashboard.properties file from the My Documents folder). Thedashboard.properties file is found in \WHERE_EVER_YOU_INSTALLED_DASHBOARD \dashboard\conf\dashboard.properties If the Dashboard Purge process was installed on the computer, as a precautionary measure, it should be updated with the GlobalPointAdaptor.jar that is found in the DashboardPurge portion of the cd (DashboardPurge\lib\GlobalPointAdapter.jar) using the steps 2 through 5 below. 2 You should first stop the Dashboard Purge windows service under the Control Panel/Administrative Tools/Services. Right click on Dashboard Purge Services and choose Stop. 3 Copy theglobalpointadaptor.jar to something like old_globalpointadaptor.jar (folder: \WHERE_EVER_YOU_INSTALLED_DASHBOARD_PURGE \dashboardpurge\lib) 4 Copy the new GlobalPointAdaptor.jar file to wherever it is installed: (For example, from the cd to \WHERE_EVER_YOU_INSTALLED_DASHBOARD_PURGE\dashboardpurge\li b.) 5 Then restart the DashboardPurge windows service under the Control Panel /Administrative Tools/Services. Right click on Dashboard Purge Services and choose Start. 6 The cd may include an updated CONNX data dictionary called Tps_Dashboard.cdd. If not, skip to step 11; other wise, to install this data dictionary, follow steps 6 through 10. First stop the CONNX JDBC Service from the Windows Control panel under the Control Panel/Administrative Tools/Services. Right click on CONNX JDBC Service and choose Stop. 7 Next, make a copy of the Tps_Dashboard.cdd file called old_tps_dashboard.cdd 8 Copy the new Tps_Dashboard.cdd file from the ConnxCDD folder from the cd. 9 Next you must use the CONNX Data Dictionary Tool to edit the Tps_Dashboard.cdd file and set the IP address of the VMS server that CONNX should point to by first checking the IP address of the old Tps_Dashboard.cdd. DB-30

31 10 Make the IP Address of the newtps_dashboard.cdd file the same as the old. 11 Now you are ready to run the install. Double click on dashboard-setup.exe from the cd. Click on Next all the way to completion. Then click Finish. If you installed an updated CONNX data dictionary (steps 6 10), go on to step 12. If you did NOT install an updated CONNX data dictionary, you are done. 12 If you installed an updated CONNX data dictionary, restart the CONNX JDBC windows service under the Control Panel/Administrative Tools/Services. Right click on CONNX JDBC Service and choose Start. DB-31

32 Dashboard Troubleshooting Tips Contents of Troubleshooting Section The following troubleshooting tips are included in this section: The Dashboard Banner comes up on the screen, but nothing else. How do I turn on logging? License looks good but it doesn t seem licensed. How to change how often the purge process runs. Problem: The Dashboard Banner comes up on the screen, but nothing else. How do I turn on logging? Procedures The following steps describe how to turn on Dashboard logs. 1 Backup dashboard\conf\log4j.xml 2 Edit dashboard\conf\log4j.xml 3 Replace occurrences of <appender-ref ref="console" /> with <appender-ref ref="file" /> 4 Replace occurrences of <level value="warn" /> with <level value="debug " /> 5 Save and exit the log file. 6 Run Dashboard. 7 When it fails, look in the directory dashboard\logs/@dir@\ 8 If you don t under logs, then edit the log4j.xml again and modify the appender tag to have an appropriate log file name: <appender name="file" class="org.apache.log4j.rollingfileappender"> <param name="file" value="logs/dashboard.log" /> 9 Edit or Save or FTP or the log file back so we can review it. DB-32

33 Problem: License looks good but it doesn t seem licensed. Procedures The following steps describe what to do if the License looks good but doesn t seem licensed. 1 Take the CNXLIC.DAT, call it CNXRMS.DAT and FTP it into the CNXDIR folder on your VMS server. 2 Also on every CONNX install, using EDIT add the following lines to SYS$MANAGER:SYSTARTUP_VMS.COM, near the end. $! Commands needed for CONNX ODBC Driver $ DEFINE/SYSTEM CNXSVR SYS$COMMON:[CONNX]CNXSVR.COM $ DEFINE/SYSTEM CNXDIR SYS$COMMON:[CONNX] $ DEFINE/SYSTEM CNXRMS SYS$COMMON:[CONNX]CNXRMS.COM $ DEFINE/SYSTEM CNXRMSA0 SYS$COMMON:[CONNX]CNXRMSA0.COM START Problem: How to change how often the purge process runs. Procedures The following steps describe what to do to change how often the purge process runs. Note: You can review the log to check how often the purge process is running. 1 Edit the adapter.xml file. To do so find the following section in the xml: <handler>com.tps.adapter.handlers.dashboardpurgehandler</handler> <schedules>* * *</schedules> These lines control how often the process runs. The three stars (* * *) mean run all the time. <schedules>* * *</schedules> DB-33

34 2 You can modify it to run every hour or even once a day, by doing the following: Change the last star (* * *) to a number between 0 and 59 to indicate what minute of the hour the purge is to run. Example: To set it up to run every half hour, change the settings to the following: <schedules>* * 30</schedules> Change the middle star (* * *) to a number between 1 and 24 to indicate what hour of the day the purge is to run. Example: To indicate that it should run every day at 11:30 AM, change the settings to the following: <schedules>* 11 30</schedules> [Last revision date: 10/29/09] DB-34