Utilities Descriptions

Utilities Descriptions

Contents Show

XMLCleaner

This utility provides a checklist to invoke all of the steps to export and import fact and metadata from a database to a new, proCube database, and clean the metadata in between. It cleans up invalid data that arises due to problems such as uncompleted processes or illogical imported data. Examples of such problems include empty alias names, duplicate cubes with identical names, or a user that owns a process but has been deleted from the system.

In the vast majority of cases, such data inconsistencies remain hidden and unknown, never visibly affecting the use of proCube, even if they might be somewhat degrading performance somewhat. But when a proCube function is repeatedly unable to complete, and the underlying data is suspect, you should consider cleaning the database. It can also be a good idea, in systems that continuously undergo extensive metadata updating, to periodically run this utility on a proactive basis to improve performance and eliminate inconsistencies before they become problems.

The steps can be performed all-at-once, or separately, as shown by the "Clean Database" and "Run Selected Tools" options on the upper left side of the following screen:

procubedatabasecleaner.png

Figure 1.    proCube Database Cleaner

As you select the options on the left side of the proCube Database Cleaner window, varying fields appear on the right for you to supply the corresponding, required information. Click Browse to enable the location of the appropriate information for each field. You can choose to automatically delete all of the files once they are imported by selecting Delete Files After Import.

Clean Database

This option runs the entire sequence of steps on a database. If a sequence fails at any step, a prompt will appear to describe the problem. After you address the problem, you can then select the remaining steps and continue from that point.

Run Selected Tools

This option enables you to run any or all of the processes individually. The processes are as follows:

Process

Description

Export XML Metadata

Exports the metadata into an XML file in the same folder as the OLP file.

Export Fact Data

Exports the cube fact data into a folder created below the folder of the OLP file.

Clean XML Metadata

Checks for some common, known invalidities in the XML document; fixes them (with the user’s permission); resaves the XML document.

Validate XML Database

Validates the XML file against the provided XSD schema. If the XML file is invalid, a list of the invalidities is displayed. For proCube XSD Path, youmust specify the database2.xsd file which, in a default installation is found in the C:\Program Files\proCube folder.

Create New Database

Creates a new database in the existing OLP folder. The existing OLP is renamed to .OLD.

Import XML Metadata

Imports the XML metadata into the given OLP.

Import Fact Data

Imports the files in the specified folder into the OLP.

To clean your database:

  1. Back up your database, preferably to removable media.

  2. Run XMLCleaner.

  3. On the left side of the proCube Database Cleaner window, select options. The window's right side will show fields for the information you need to supply.

  4. Complete the fields on the right. For proCube XSD Path, specify the database2.xsd file, which, in a default installation is found in the C:\Program Files\proCube folder.

  5. Click Go.

  • If the process runs without finding errors, a prompt appears: The program has completed successfully. Click OK and close the window.

  • If errors were found, fix the data and click Go again to complete the remaining steps. The specific procedure for fixing XML errors is beyond the scope of this document.

Example Errors

The Validation Errors window shows a sample error message from the validation process. These errors require manual resolution, by using the error's line number reported and making the required changes in the XML file.

validationerrors.png

Figure 2.    Validation Errors Window

CubesRebuild.exe

CubesRebuild.exe is a command-line utility equivalent to the proCube menu function, Data/Xchange/Rebuild Cube. It replaces the old pxrebuild utility, using the .NET platform to offer technical advantages by no longer requiring the full proCube Windows process to execute. If you run the command without any arguments, the required syntax is displayed, slightly reformatted here:

****************************************************************************
proCube Xchange Cube Rebuild Command Line Utility
CubesRebuild.exe
****************************************************************************

Setup Instructions:

So as to optimize the rebuilding of the cubes a space separated list of cubes can be passed in to the rebuild process. Use quotes to separate parameters that have spaces in them.

To run CubesRebuild.exe pass the required additional parameters about what server, database,  username, password, method and cubes to use.

Following is the list of parameters and the syntax required.  For more information on the function of each parameter, please consult the proCube Xchange Manual.

Syntax:

CubesRebuild.exe ServerName DataBaseName User Password RebuildType CubeName CubeName ...

  • ServerName [<[<proCube  Server name>]

  • DatabaseName (not the OLP filename but the name in proCube)

  • User [<[<proCube  server account>|<user name>] if none use empty quotes

  • Password [<[<proCube  server password>|<user password>] if none use empty quotes

  • RebuildType

  • F - Rebuilds Fact Data Only

  • M - Rebuilds Meta Data and Fact Data

  • U - Updates Meta Data and Fact Data

  • H - Updates Meta Data, Rebuilds Hierarchies and Fact Data

  • CubeName = Space-separated list of cubes to be rebuild

For a missing value, such as User or Password in a non-secured database, use empty quotes.

Example Using proCube Server:

CubesRebuild.exe  SEVER01 Sample AnyJoe SecPaswd M Finance

XMLValidator

This utility checks the integrity of an XML metadata file that you exported with the proCube menu function, Data/Export/Metadata to XML.

XMLValidator also includes a function to transform the metadata, enabling software developers to execute any capabilities that can be programmed into XSLT transformations. One example is generating reports on the XML data.

The Validator Dialog shows the status of the integrity check:

validator.png

Figure 3.    Validator Dialog

To run the validator utility:

  1. Run XMLValidator.exe. The program window opens.

  2. Click the browse button (…) to the right of XSD and specify the database2.xsd file., typically found at C:\Program Files\Satori\bin\database2.xsd.

  3. Click the browse button (…) to the right of XML and specify an XML file that you exported.

  4. (Optional; although operational, this functionality is for future use.) If you are performing a transformation on the file, click the browse button (…) to the right of XSL and specify an XSL file.

  5. Click Validate.

  • If there were errors, the message “Document is invalid” appears and the errors are reported in the pane at the bottom of the window. Click OK. Then click Notepad to open the XML text to examine the cause of the errors, and possibly fix them. The specific procedure for fixing XML errors is beyond the scope of this document.

  • If there were no errors, the message “Document is valid” appears. Click OK.

  1. If you are using the optional transform functionality, click Transform.

  2. After validating, particularly if you fixed invalid data, the next likely step is to import the metadata into a database.

Promo.exe

Promo.exe is an unsupported Windows program that monitors users and activities occurring on a server. It runs in two separate modes: Admin Mode and View Mode. Promo.exe, available in 32- or 64-bit versions, is automatically installed on the proCube server and located in the following locations:

  • 32-bit: C:\Program Files (x86)\Satori\proCube\bin\promo.exe

  • 64-bit: C:\Program Files\Satori\proCube\bin\promo-64.exe

Admin Mode

To run (promo.exe or promo-64.exe) in Admin Mode:

  1. Double-click the file to open the program dialog. The dialog is divided into three sections for server, running operation, and pending operation.

procubeserverprocessmonitor.png

Figure 4.    proCube Server Process Monitor Dialog (Admin Mode)

  1. From the Host Name drop-down, select one of the servers. Port Name displays for the selected server. Clicking Refresh manually updates the dialog information.

  2. Select one of the seven tabs at the bottom of the dialog:

  • View — Lets you view the number of users logged onto a proCube server instance and the running and pending operations.

  • Logging — Lets you enter (in seconds) how often a refresh of the dialog information will run and lets you turn on a Log to File for users and operations. The default log file is: /bin/promolog.log.

  • Debug Level Info — Allows you to set the debug info level. The available levels are: Info, Warning, Error, Fatal.

  • Sessions — Turns on Block Users and then disconnect all or selected users.

  • Calculations — Enables the cancellation of all or selected user calculations.

  • Messaging — Broadcasts messages (e.g., Server is rebooting) to a user or all users.

  • Dangerous — Sets the server to desperate mode in order to do a last resort destructive save.

Viewer Mode

From the command line, run promo.exe with the –v switch, to open it in Viewer Mode (proCube Process Viewer). Viewer Mode is similar to Admin Mode except that this version does not have the seven tabs. Viewer Mode allows you to view users logged into a proCube server instance and view running and pending operations.

Command line syntax

To perform:

Use this function

Run in Admin Mode (all tabs display)

Promo.exe

Run in Viewer Mode (no tabs display)

Promo.exe –v

Specify a default server

Promo.exe –machine/instance

Specify a default server in viewer mode

Promo.exe –v –machine/instance

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk