This page (revision-61) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
61 26-Nov-2021 10:22 10 KB Karen Parrott to previous

Page References

Incoming links Outgoing links
IMST
IMST

Version management

Difference between version and

At line 4 removed one line
[CLEANUP]
At line 9 added 2 lines
If any of the 'Mail' information on the Environment tab is changed (Mail Host, Mail Domain, Mail Port or Mail Auth User), the application will need to be restarted to establish the new values.
\\ \\
At line 12 changed 4 lines
;[Activation Key|ACTIVATION_KEY]:The activation key informs the application that the client is an authorized and licensed user of the system, and advises the system as to which modules and applications have been purchased.
;[Demo Key|DEMO_KEY]: The demo key is an access code assigned to a client that enables them to access the complete product (all applications) for a specific time period. Clients may be granted a trial period for the purpose of experiencing evaluating new applications and features that they are considering purchasing. Once the expiration date passes, the applications not purchased can no longer be accessed.
;[Demo Expiry Date|DEMO_EXPIRY]:This field indicates the expiration date of the demonstration period.
;[License Type|LICENSE_TYPE]: This field specifies the type of product license granted to the site. \\An extended license enables the site to create new tables in the database in order to integrate custom solutions with the application. It is reserved for sites that have a full Oracle development environment and in-house Oracle database expertise. \\ A standard license enables the site to access and report on the database with read only capability. It is designated for sites that have a trained Oracle database administrator, but do not have an Oracle development environment. \\ A basic license enables the site to access and report on the database through the application only.
;Ping Tax Server: This button is used to verify that the Tax Server is working, and will respond with the Symmetry engine version and the Tax Table release.
At line 17 removed one line
;[Concurrent Users|CONCURRENT_USERS]:This field is used to indicate the estimated number of users that would be logged into the application at one time. This field is used for information purposes only.
At line 22 changed 10 lines
;[Windward Version|]:
;[Mail Host|MAIL_HOST]:
;[Mail Domain|MAIL_DOMAIN]:
;[Site Logo|SITE_LOGO]:
;[Build Version|]:
;[Build Date|]:
;[Database IP|]:
;[Database SID|]:
;[Backend Version|]:
;[Environment|ENVIRONMENT]:
;[Windward Version|DRV_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|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|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|MAIL_PORT]: The TCP port number that is used to connect to the mail host, for a secured mail host.
;[Mail Auth User|MAIL_AUTHENTICATION_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|MAIL_AUTHENTICATION_PW]: Pressing this button will enable the user to set or change the password used when authenticating to the secured email user.
;[Build Version|DRV_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|DRV_SERVER_VERSION]: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|DRV_DB_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|DRV_DB_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
At line 33 changed one line
[CLEANUP]
;[Backend Version|DRV_DB_VERSION]:The version of the application's backend software the database is running will display here.
;[Site Logo|SITE_LOGO_FILE]: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.
;Resources: This field is used to display the current HLAppResources URL.
;[Environment|ENVIRONMENT]: This field was used in prior products to track certain system information; however, this is no longer used in the current application.
At line 35 removed 4 lines
!Client
;[Trigger Logging Level|]:
;[Reload Style (Professional)|]:
;[Reload Trace Rules (Professional)|]:
At line 37 added 5 lines
!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|ACT_TRIGGER_LOGGING_LEVEL_CLIENT]: 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)|ACT_RELOAD_PROF_STYLE]: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)|ACT_RELOAD_TRACE_RULES_PROF]: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.
At line 41 changed 3 lines
;[Trigger Logging Level|]:
;[Reload Style (Web)|]:
;[Reload Trace Rules (Web)|]:
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|ACT_TRIGGER_LOGGING_LEVEL_SERVER]: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)|ACT_RELOAD_WEB_STYLE]: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)|ACT_RELOAD_TRACE_RULES_SERVER]: 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.
At line 66 changed 2 lines
;[Message|]
;[Send to all active users|]
This message is sent to all Professional users that are connected to that application servers. The message is not sent to any professional users who are connected to a different load sharing instance.
As of the 5.05.23 release, this message will also be sent to all the Self Service users connected to that application server.
;[Message|DRV_ALL_USERS_MESSAGE]:This area allows the Administrator to enter a message that will display within the application for all active users of Professional and 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|ACT_MESSAGE_ALL_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 IMST 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 IMST. On the Form Layout tab, for Seq#120, Form Group ‘BUTTONS LEFT’, add a Group Items for the applicable button to be created.
Example:
[{Image src= [MSTActionCol.png|thumb|right| width='600'}]
\\
;MST ACTIONS
ACT_GARBAGE_COLLECT\\- 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()\\ \\
----
![Notes|Edit:Internal.IMST]
[{InsertPage page='Internal.IMST' default='Click to create a new notes page'}]
This page (revision-61) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop