Administrator toolbox

Administrators have a tool available, the administrator toolbox, that provides regularly required information and facilitates recurring tasks.

The commands are available as buttons or in the function bar. Administrators can temporarily lock the system globally for non-administrators (normal users) for administration purposes. Only administrators can log in while the system is locked.

An administrator can send a message to all logged-in users about any required locking or other system conditions. This message appears in the client of the users who are logged in to the application.

Administrators can access complex environment information for support purposes, which appears in the message bar and supplies the CRM support team with the necessary information.

Opens an editor for writing and sending a message.

Locks the login for all non-administrators. Normal users are rejected by the system.

Unlocks the login for all non-administrators. Normal users can log on to the system again.

Deletes the object cache to persist changes made to objects, and also triggers the Java gar­bage collection for automatic memory clean up.

You can specify here whether the system should send an email or automatically delete the cache when a given memory utilization ratio is reached. The corresponding SMTP parame­ters must be provided if you want to receive an email.

If on a server more than one application server is running for the same database (eg Job Server), the host name, port, and file server name (psc.env.srv), if set in the properties, are written to the body of the message.

On the one hand, the dialog is for setting the Global configuration for a system user (who is not logged in, i.e. global). This allows you to configure the email dispatch for the memory warning.

Furthermore, the Defaults of the email configuration can be provided for all users when they send emails "directly". Note in this context that there is the PSA_PSP_USE_DFV environment variable. By means of the value y, the users are prevented from receiving pop-ups with the configuration data when sending emails, i.e. the defaults are auto­matically used. The value n will open the pop-up query for users sending their email directly for the first time. The default value is y.

Here, also the Global configuration by the administrator for the Groupware connector can be made.

Edit the Log4j property file.

Instead of writing errors and information messages to the standard output, such messages are passed to the logging system, and, at the same time, categorized by their importance. The filtering and type of the output can be configured at runtime.

The system can display the appender for the transmitted emails or the storage properties.

Opens a list with the messages of all loggers. You can search for logger messages or load everything in the list.

Opens a list with all logged-in users with communication and support options. After marking an entry, user-specific functions can be executed.

You can analyze problems of individual users at runtime better by switching on a user-specific SQL-Trace. If a trace is still running, it is automatically switched off when starting a new trace. You can only select traces with a specified logfile because it is stored on the server.

Selected functions are cluster-overlapping and selectively executable.

The user list displays all logged-in users on the cluster servers. The functions "Global message", "Disable/Unlock login" and "Jobs" refer to all cluster servers. The functions "Stacktrace", "Transactions", "Open dialogs", "Client information", "SQL trace" and "Stop session" refer to the cluster server on which the user is logged in.

The functions "Message", "Ping" and "Call" don’t require cluster ability due to their implementation.

Current information about the used print server is given in the message bar.

Indicates various pieces of system information of the application in the message bar.

Resets all locked data records (PSC_LCK flag).

You can stop the timer that initiates the various events (internal or other messages) if you plan anal­yses or something similar. The client specifies the interval for the resubmission check by means of the PSA_SET_RSM_TIM_ITV vari­able within minutes. If you specify 0, the timer is switched off. All resubmissions still end up in the list of the open messages, but do not pop up anymore.

This allows you to check why a record is not visible in a derived DTO (data object) because of absent components (which is the case if a hyperlink opens an empty form).

Checks for typical errors in the repository and in Java and provides corresponding messages and warnings in the message bar. Various checks are implemented, for example:

• Compiler
• Class path
• Manifesto
• Valid data objects
• Windward reports
• Crystal reports
• Zip code database
• Full text index
• Missing PSC_OUT
• Missing PSC_CLS
• Missing default values OPR_IDN
• Wrong super classes
• Locked records
• Subdialog uses
• Views with unnecessary tables
• and many others

Other or additional functions can be placed through customizing in the Jar or dynamic Java.

Updates the recently pulled licenses from the database (licenses must have been provided). See also the section Licensing.

Shows the monitor for the current sessions. Here, faulty sessions can be terminated (e.g. after a system breakdown).