Activating the PATH tables


Starting with fix 2013.1.0.152 one is required to ensure that the standard PATH tables (e.g., SD_CATALOG_PATH) are automatically refreshed since the EasyVista graphical user interface now uses this data to enable the new tree lookup searches. This page aims to show you how to enable this feature.

Caution

  • Computing table paths can prove CPU intensive, potentially taking over an hour for especially large tables.

Contact

For any questions or concerns, do no hesitate to contact your project consultant or your local support whose number you will find in your copy of the EasyVista Support Guide. If you are unable to find your Support Guide, please contact:

Installation

Please ensure you have reviewed or addressed the following items:

  • You need only implement this feature on 1 APP server per EasyVista platform
  • You must login to Windows using an account with Administrator privileges
  • You need to know where the EasyVista folder is located
  • You will need the SQL password for the 50004 (and 50005, etc.) account(s)
  • You must have applied Fix 2013.1.0.152 (or a more recent fix) beforehand

Notes:

  • Implementing this feature should not require any downtime, however do note that downtime will be needed if you also have to apply an EasyVista fix as part of this change.
  • If a given platform has multiple APP servers we suggest you might like to implement this feature on the one that is running all the background SMO services. 

Extracting the "Script" files

Note: This step applies only if you are using Fix 2013.1.0.152 (or older).

1. On one of your application server (mainly you have only one), locate your Easyvista main directory (check your installation document or search for smo_server.ini file).

This document will use the following path as an example: C:\Program Files (x86)\Easyvista\tools\servers\MSSQL

2. Under this folder, create a new subfolder named Script

Creating the Script subfolder:


Open the Table_path.zip file and extract it to Script  
The result should look like this:

ScriptContaint.png

Create Windows Scheduling tasks

For each account you wish to implement this feature you will create a Windows Scheduled Task.

1. Launch The Task Scheduler MMC snap-in “task” using Start-Run:
Create à new folder > Create a new entry in the library:
         TaskCheduler.png

2. Import each task (for more information How to import a task, by Microsoft)

Note: If you intend on activating a job for the 40000 account as well, you will need to run the following SQL script using Microsoft SQL Studio, since PATH computations are not enabled by default for DEMO (see paragraph "Force table path computing"):

/* for demo DB */
UPDATE EVO_DATA40000."40000".AM_DEPARTMENT SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_DATA40000."40000".AM_SUPPLIER SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_DATA40000."40000".EP_ANALYTICAL_CHARGE SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_DATA40000."40000".AM_LOCATION SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_DATA40000."40000".SD_CATALOG SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_DATA40000."40000".SD_KNOWN_PROBLEMS SET PATH_TO_COMPUTE=1 WHERE LEVEL=1
UPDATE EVO_CONFIG40000.EVO_CONFIG40000.C_TASK_CLASSIFICATION SET PATH_TO_COMPUTE=1 WHERE LEVEL=1

3. Under theAction adjust two items:
 

  • Replace “YourPassword” with the correct SQL password for each account (Note: You may find this password inside the file named “smoServer.ini” if need be): your task is now registered  
  • Repeat this step for each account in turn (50004, 50005, etc.).
             ActionSettings.png

Force table path computing

The first time, to populate the entire table, runs 1 init_pass.sql :

1. Log on SQL server management studio as sysadmin group member (e.g. sa).

2. Open the init_pass.sql and execute it.

Troubleshooting

Check if all task run:

  • If you glance at the “Last Run Time” and “Last run” columns, these would normally say “yesterday” and “(0x0)”.
  • Each job instance generates its own logs inside the “Easyvista\Script\Table_Path\log” folder.
    • Open file to show errors and to help in troubleshooting. 
    • If the file should be found to contain no information, such as only a blank line, please refer to Microsoft TechNet to troubleshoot the task manager: http://technet.microsoft.com/en-us/library/cc721846.aspx (or: search for “windows 2008 task scheduler troubleshooting” via TechNet or on the internet)
Tags:
Last modified by Unknown User on 2015/11/12 17:57
Created by Administrator XWiki on 2015/04/10 11:32

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:

-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

How to Automate Integration
Add a Shortcut to an App
History
Quick Dashboard
Full text search - Stop Words

Powered by XWiki ©, EasyVista 2019