PSA Tasks
General Tasks
•
To start PSA
View Modules Tasks
•
To select options for View Modules
Test Active Installation Tasks
•
To test your network
•
To test the MicroKernel (transactional) Engine
•
To test the Relational Engine
Log Files Tasks
•
To specify a different location for the PSA log file
•
To view the log file at the completion of PSQL System Analyzer
General Tasks
►
To start PSA
1
Access PSQL System Analyzer from the operating system Start menu or Apps screen or execute psawizrd.exe from a command prompt.
For default locations of PSQL files, see Where are the PSQL files installed? in Getting Started With PSQL.
View Modules Tasks
►
To select options for View Modules
1
Start PSA and click Next.
2
Click View Loaded PSQL Modules.
3
Click Next.
A dialog appears similar to the following.
Figure 27 View Modules Section of PSA
If In Memory is selected, PSA searches for all PSQL components loaded in memory, regardless of whether they are located in the PATH or other specified locations.
If you want to add components to the search list, do the following:
a.
Click Additional modules (if it is not already selected).
b.
Type the file name (without a drive letter or path) in the text box.
c.
Click Add Component .
d.
If the component you added is not in the path, add the path to the searched locations.
If you want to add more paths to the search locations, do the following:
a.
Click Additional locations.
b.
Click Add Location .
c.
Browse to the location using the directory selector and select the desired location.
d.
Click OK.
e.
If you also want all directories below the location to be searched, click Include subfolders.
4
Click Next.
5
View the grid that shows the components found.
If files of the same name are detected, the multiple occurrences are marked with an icon on the left side: .
If you see multiple occurrences of a component, you can adjust the list so that the occurrences sort together. To do this, click the Module column heading.
Multiple occurrences of a file does not necessarily represent a problem with your configuration. Their identification can help you troubleshoot issues with components depending on the situation. For example, if you see two PSQL components both marked with the same version, you may want to check which is loaded in memory and that the components are located where you expect.
6
Click Next.
7
Click Finish if you are finished using PSA, or click View Log File to view the log.
Test Active Installation Tasks
►
To test your network
1
Start PSA and click Next.
2
On the Options dialog, click Test active installation (if it is not already selected).
3
Click Test network communication (if it is not already selected).
4
Click Next.
5
For Target machine, type the machine name or TCP/IP address of the machine you wish to test. You may also type “localhost” for the local machine. The machine can be the machine where you are currently located or a remote machine.
6
If you want to control how the tests are run, click Advanced Settings and complete the following steps:
a.
By default, PSA uses the first available protocol. You can force PSA to use one or more protocols by clicking Use Only These Protocols.
b.
Select the protocol options that you want PSA to test. Note that the NetBIOS protocol is not supported on PSQL Server. The SPX protocol is not supported on PSQL Workgroup.
c.
Specify the number of stress test messages to send by typing a value for test messages. The default is 75. (After successfully connecting using any protocol, PSA sends stress test messages to ensure that the connectivity is functioning correctly. )
d.
Click OK to save the changes.
7
Click Next to start the test.
PSA runs a series of tests and displays the results.
If the test succeeds, PSA informs you that all test messages were successfully transmitted. If the test fails, PSA lists the issues along with tips on how to resolve them. The tips are also written to the PSA log file.
8
Click Next.
9
Click Finish if you are finished using PSA, or click View Log File to view the log.
►
To test the MicroKernel (transactional) Engine
1
Start PSA and click Next.
2
On the Options dialog, click Test active installation (if it is not already selected).
3
Click Test transactional engine (if it is not already selected).
This test runs a series of transactional operations to simulate your client requester interacting with the database engine.
4
Click Next.
5
Provide a path name to the samples directory on the machine running the database engine. The default path should be correct if the database engine is running on the local machine. You can type a path, or browse to one if you click .
6
Select the operations you want to perform for the MicroKernel Engine (by default, all are selected):
•
Create Data File (write access required)
•
Read Data File
•
Update Data (write access required)
•
Insert Data (write access required)
7
Click Next.
PSA performs the tests and displays the results. A check mark indicates a test succeeds and an "x" indicates a test fails.
If all of the tests succeed, your client requester can communicate with the database engine.
8
Click Next.
9
Click Finish if you are finished using PSA, or click View Log File to view the log.
►
To test the Relational Engine
1
Start PSA and click Next.
2
On the Options dialog, click Test active installation (if it is not already selected).
3
Click Test relational engine (if it is not already selected).
This test runs a series of SQL operations to simulate your client requester interacting with the database engine.
4
Click Next.
5
For Machine Name, type the name or IP address of the machine where the engine data source name (DSN) resides, or browse to the machine (click ).
The name “localhost” is valid if you are testing the local machine.
6
For Engine DSN, type the name of the DSN for the data source you want to test. The default, demodata, uses the DSN for the sample database installed with the database engine.
7
Select the operations you want to perform for the Relational Engine (by default, all are selected):
•
Create Table
•
Read Data
•
Update Data
•
Insert Data
8
Click Next.
PSA performs the tests and displays the results. A check mark indicates a test succeeds and an "x" indicates a test fails.
If all of the tests succeed, your PSQL Client can communicate with the Relational Engine.
9
Click Next.
10
Click Finish if you are finished using PSA, or click View Log File to view the log.
Log Files Tasks
►
To specify a different location for the PSA log file
1
Start PSA and click Next.
2
In the Log File field, type a path to the PSA log file, or browse to the desired location (click ).
If you want a log file that contains information only about the current PSA session, clear the Append to log file option.
You can also specify a different name for the log file, but the name applies only for that session of PSA. PSA defaults the name to PSALog.txt the next time you execute PSA.
►
To view the log file at the completion of PSQL System Analyzer
Click View Log File to display the PSA log file.
A summary of the tasks PSA completed is listed for you.