REPORT INSTANCE CLIENT SITE INFORMATION#
The Report Instance Client Site Information (IMSTR) screen allows you to access the report server, if setup. The data base will be all the same but it is running in the separate report server so you can trigger the trace level or see the Windward versions, etc. from this deployment.
The definition data for the Report Instance Client Site Information screen is stored in the P2K_AM_SITES, P2K_AM_PREFERENCE_VALUES and P2K_AM_LANGUAGES tables.
- Site Code
- This field identifies the site within the system.
- Description
- This field provides a short description of the site.
Environment tab#
- Windward Version
- This field will display the current version of Windward that has been installed. This is only updated during application upgrades. If errors occur when running a Windward report, users may want to verify the version displayed here to ensure it is the latest released.
- Mail Host
- This field refers to the location of the mail server (i.e. mail.mycorp.com). In the case of standalone environments this should be set to “localhost”. This field is used to generate emails from the application, i.e: for workflow or for forgotten passwords. If your mail server is a secured server (like an MS Exchange Server) then you will also need to provide the authentication information (below) for port, user and password.
- Mail Domain
- This field refers to the local domain (i.e. highlinecorp.com) to be used for any emails to be generated from the application.
- Mail Port
- The TCP port number that is used to connect to the mail host, for a secured mail host.
- Mail Auth User
- This is the user name that is used to sign on to the secured mail host. Note that this is not necessarily the same as the From email address that is used for sending mail. If the from email address is not the same, the authentication user must be granted the rights to send emails as the from user account.
- Set/Reset Mail Auth Password
- Pressing this button will enable the user to set or change the password used when authenticating to the secured email user.
- Build Version
- The version of the build the application is currently running is displayed here. This is derived from the files within the HLAPPResources. This date would only be updated during an upgrade of the application.
- Build Date
- The date displayed in this field is the date the ear was physically created, this is not the date the ear was applied to the instance. If, after an upgrade, this date does not change the ear should be un-deployed and then re-deployed.
- Database IP
- This field is used to display the IP Address of the database that the application instance is configured for. The IP that is reflected here stems from the set up that was done in the Admin Console for the Application Server.
- Database SID
- The SID (unique name given for the database instance) that the application instance is configured for is displayed here. Like the IP Address, this stems from the set up that was done in the Admin Console for the Application Server.
- Service Name
- Backend Version
- The version of the application's backend software the database is running will display here.
- Site Logo
- This field indicates the location of where the site logo is kept. If a logo is loaded here it will be used as the Report Logo on standard Windward reports.
- Environment
- This field was used in prior products to track certain system information; however, this is no longer used in the current application.
Client#
The Client side deals with the presentation of the Professional application, the GUI (Graphical User Interface) and the other processing that may occur on the client.- Trigger Logging Level
- This button when pressed changes the application's tracing level from FINE to FINEST. This may be used to troubleshoot issues encountered on the client side. The tracing may be seen in the appropriate Java Console log and the Application Server's default log file. To turn off the increased tracing, simply press the button again. The button's prompt will reflect the current tracing level.
- Reload Style (Professional)
- This button forces the application to pick up any changes that have been made to the GUI via the style sheets or the xml file. If this is not pressed and there have been changes made to the GUI, the changes will not appear until the Application Server has been restarted.
- Reload Trace Rules (Professional)
- This button forces the client to pick up any changes that may have been to the TraceRules.xml file. The TraceRules.xml file is where really high level tracing may be turned on for specific Java classes. The trace has to already be at the "highest" level before any of the additional tracing has any impact.
Server#
The following section applies to both the Self Service and Professional applications. The following buttons deal with the presentation of the application, the GUI (Graphical User Interface) and the other processing that may occur on the applications.- Trigger Logging Level
- This button when pressed changes the application's tracing level from FINE to FINEST. This may be used to troubleshoot issues encountered on the server side. The tracing may be seen in the appropriate Java Console log and the Application Server's default log file (i.e. OC4J~QA3~default_group~1). To turn off the increased tracing, simply press the button again. The button's prompt will reflect the current tracing level.
- Reload Style (Web)
- If changes have been made to the Self Service GUI via the style sheets or the xml file, users can press this button to have the changes reflected in the application rather than having to stop and restart the application server. Note that the web cache MAY still need to be restarted, if used.
- Reload Trace Rules (Web)
- This button forces the client to pick up any changes that may have been to the TraceRules.xml file. The TraceRules.xml file is where really high level tracing may be turned on for specific Java classes. The trace has to already be at the "highest" level before any of the additional tracing has any impact.
Preferences tab#
Preferences are site wide items that control the manner the application is presented to the users. Some preferences also control how the application will be executed in various areas when run. In IMSTR users may establish the setting of system preferences that apply to the site.- Preference
- This field identifies the preference code.
- Priority
- This field prioritizes the preference which determines the order in which the preference is used.
- Value
- The preference's value is specified here. Each preference may have different values so it is suggested to review the preference definition in system preferences.
Languages tab#
This tab is view only Any languages that may have been defined for the client in IMLA will reflect in this tab.- Seq#
- The sequence of the translation. The sequence order determines the order of translation therefore, the language that you are translating into must have the HIGHEST (i.e. 99999) sequence number.
- Usage
- This field indicates if the language was pre-defined with the application or if it was custom made by the client.
- Language
- This field holds the primary language used at the site. English will default.
- Country
- This field identifies the country associated with the site
- Role
- A language may be defined for a specific role, if so the role name the language is tied to will display here.
Message All tab#
- Message
- This area allows the Administrator to enter a message that will display within the application for all active users of Professional and not Self Service users. The Administrator may view the VMJLOG screen to see all of the active sessions in the application. The message may hold 2000 alphnumeric characters.
- Send to all active users
- Pressing this button will cause the message to be sent. There is no need to save the message as once this button has been pressed the message will clear out of the field above.
Optional Debugging Tools#
The following MST Action columns are not supplied as form items to our clients as defaults, but can be added to IMSTR and will create a button on the screen for debugging purposes.The setup for these will be done on the IMFDH form for the function IMSTR. On the Form Layout tab, for Seq#120, Form Group ‘BUTTONS LEFT’, add a Group Items for the applicable button to be created.
Example:
 |
- MST ACTIONS
- Calls System.gc()
- https://docs.oracle.com/ javase/7/docs/api/java/lang/System.html#gc()
- No argument for algorithm – it probably uses whatever is setup in JVM
ACT_PRINT_JAVA_ENV
- Prints the JVM parameters/System Properties, including the Classpath to the server log
- Prints IP address information
- Logger hierarchy details
ACT_PRINT_SYSTEM_INFO
- Prints similar info to ACT_PRINT_JAVA_ENV, but ALSO internal application info
- All currently Scheduled Reports
- Lists all logged in Users – MSA.ID, db Session ID, all opened forms, current open forms
- Database Change Monitor statistics: Avg scan time, # of timeouts, # default scans, lock owners, etc.
- Business Object Cache statistics: Cache TableNames, ‘child’ caches & row counts
- Threads available from java.management.ManagementFactory
https://docs.oracle.com/javase/7/docs/api/java/lang/management/ManagementFactory.html#getThreadMXBean()
