Managing Ensemble Productions - InterSystems Documentation

More documents

Recommendations

Info

Maintenance 2. From the Maintenance menu click Purge Management Data. 3. The Purge Management Data page displays. Under the Purge page title bar is a display area; the Maintenance menu is at the top left corner of this display. Under the title bar and to the right of the menu is a row of commands, as follows: • Show Event Log displays the [Ensemble] > [Event Log] page. You can use this page to get information about event log entries that you might want to purge or avoid purging. • Show Messages displays the [Ensemble] > [Messages] page. You can use this page to get information about messages that you might want to purge or avoid purging. • Show Business Processes displays the [Ensemble] > [Business Processes] page. You can use this page to get information about business process instances that you might want to purge or avoid purging. • Show Business Rule Log displays the [Ensemble] > [Business Rule Log] page. You can use this page to get information about rule log entries that you might want to purge or avoid purging. If you click one of these commands to view information, you can return to the Purge page by navigating back to the Purge Management Data page described at the beginning of this section or by using the Back command on your browser. Below the row of commands on the Purge page is a dialog box that contains the following fields: • Type of Record — Identifies the purpose of each row in the table. Each row contains one type of artifact that the currently running production is producing on an ongoing basis: Event Log, Messages, Business Processes, Business Rule Log, or I/O Archive. • Current Count — Total number of entries of this type that are now in the persistent store for this production. Use the Current Count to decide whether or not it is worthwhile to purge the records and if so, how many days’ worth of records you want to keep. • Include message bodies — If selected, this check box indicates that when Ensemble purges message headers, it should also purge the associated message bodies. Ensemble verifies that body classes exist and are persistent, before purging them. If this check box is clear (the default) message header data is purged, but message body data is retained. Important: When Ensemble purges a message body object, it does not automatically delete any embedded persistent object your code references as a property in your message body class. As a developer, you must appropriately handle the deletion of these referenced objects using a mechanism such as a delete trigger, a %OnDelete() method, or through relationships. • Keep data integrity — If selected (the default) this check box indicates that when Ensemble purges message headers, even if a message meets the age criterion for purging, it is not deleted unless its status is complete. Ensemble considers messages to be complete if they are marked Complete, Error, Aborted, or Discarded. This is to keep session-level integrity. The query that identifies the messages to delete checks all the messages (including business process instances) in a session to see whether any of them are not complete. The purge only performs the delete if all the messages are complete. The scope of this query, therefore, has an impact on the time taken to do the purge. This option is important to support long-running business processes. Usually this is the desired behavior. However, if you know there are old messages in the system whose incomplete status is not significant, you can purge them by clearing the Keep data integrity check box. Important: The purge criteria for using Keep data integrity also includes Ensemble system processes such as the Scheduler. Before clearing this check box, carefully consider the value for the Do not purge most recent setting. 106 Managing Ensemble Productions
Credentials • Do not purge most recent — This tells Ensemble how many days’ worth of records to keep. The number can be 0 (zero), which keeps nothing and deletes all entries that exist at the time of the purge operation. The default value for Do not purge most recent is 7, which keeps entries for the last seven days. The count of days includes today, so keeping messages for 1 day keeps the messages generated on the current day, according to local server time. At the bottom of the dialog is the Start Purge command. If you click it, Ensemble immediately purges the persistent store according to the parameters you have entered in the Purge page. The page uses a background job to do purges, and reports the results of the last-run purge, including a status code, or a notice if the background job is running or has failed to run. CAUTION: You cannot undo the Start Purge operation. 12.3 Credentials Some remote systems require a username and password to log into that system. A username-and-password pair is a login credential. Ensemble permits you to store login credentials in a centralized table that can be viewed and edited only by users with access to the Ensemble Management Portal. Each entry in the Credentials table has an ID by which you can refer to it when configuring business services or business operations for the production. Adding an entry to the Credentials table for a production consists of assigning an ID to a username-and-password pair. The [Ensemble] > [Maintenance] > [Credentials] page displays the Credentials table for the currently running production. You can display the Credentials page as follows: 1. From the [Ensemble] home page menu, choose Maintenance. 2. From the Maintenance menu choose Credentials. 3. The Credentials page displays. There is no menu on the Credentials page. Under the title bar is a row of commands, as follows: • Home — Click to return to the Ensemble home page. • Create New Credentials — If you click this command, a dialog displays in the bottom half of the Credentials page. You can enter information in this dialog to create a new entry for the Credentials table. Below these commands, the Credentials page displays text — The following Credentials are currently defined — and a table. The table lists all the credentials associated with the currently running production. Each row in the table has the following columns: • ID — The configured name of the username-and-password pair. This is the name to be used when configuring a business service or business operation to establish a remote connection. • User — The username. • Password — The password. To the right of each entry in the Credentials page table are two commands: • Edit displays a dialog in which you can edit the Username or Password for an entry. You cannot change the ID of an entry. To use a different ID, you must create a new entry by clicking Create New Credentials. Then, if you want, you can delete the old entry. Managing Ensemble Productions 107
Page 1 and 2:
Managing Ensemble Productions Versi
Page 3 and 4:
Table of Contents About This Book .
Page 5 and 6:
9.1 Business Process List .........
Page 7:
List of Tables Table 1-1: Ensemble
Page 11 and 12:
1 Ensemble Management Portal This c
Page 13 and 14:
Login 1.3 Login The Ensemble Manage
Page 15 and 16:
Ensemble Home Page • Jobs — lis
Page 17 and 18:
Ensemble Home Page If you click the
Page 19 and 20:
Portal Command Summary Page or Comm
Page 21:
Portal Command Summary Page or Comm
Page 24 and 25:
Management Tasks Task View Alternat
Page 26 and 27:
Management Tasks Monitor... Message
Page 28 and 29:
Management Tasks 2.9 Viewing Items
Page 30 and 31:
What to Manage Production Task Purg
Page 32 and 33:
What to Manage • Business process
Page 34 and 35:
What to Manage the item to be stopp
Page 36 and 37:
What to Manage For example, an item
Page 38 and 39:
What to Manage Each dashboard is as
Page 40 and 41:
What to Manage At far right, the ti
Page 42 and 43:
What to Manage Event Log Task Filte
Page 44 and 45:
What to Manage • Mode — The exe
Page 46 and 47:
What to Manage 3.10.2 Messages in P
Page 48 and 49:
What to Manage Workflow Task Manage
Page 50 and 51:
Productions • Last Stop Time —
Page 52 and 53:
Productions If you click this comma
Page 54 and 55:
Configuration • Configuration Dia
Page 56 and 57:
Configuration The Copy command is u
Page 58 and 59:
Configuration 5.1.4 Status Indicato
Page 60 and 61:
Configuration When you click Apply
Page 62 and 63:
Configuration Column Value Source D
Page 64 and 65: Configuration Beneath the row of co
Page 66 and 67: Configuration From the Production C
Page 68 and 69: Configuration Adapter Class The cla
Page 70 and 71: Configuration Adapter SETTINGS Belo
Page 73 and 74: 6 System Monitor The [Ensemble] > [
Page 75 and 76: 7 Event Log The [Ensemble] > [Event
Page 77: Event Log Purge • Click Reset to
Page 80 and 81: Message Browser • Session — The
Page 82 and 83: Message Browser Some business opera
Page 84 and 85: Message Browser • The segment nam
Page 86 and 87: Message Browser When you have selec
Page 88 and 89: Message Browser If the Color By sel
Page 90 and 91: Message Browser Table 8-2: Options
Page 92 and 93: Message Browser Operator > >= < , >
Page 94 and 95: Message Browser 8.3.1 Resend Editor
Page 96 and 97: Business Processes 9.2 BPL Viewer T
Page 98 and 99: Business Processes - Includes — A
Page 100 and 101: Business Processes • SessionId
Page 103 and 104: 10 Host Monitor The [Ensemble] > [H
Page 105 and 106: Monitor Instances To the right of e
Page 107 and 108: 11 Queues The [Ensemble] > [Queues]
Page 109 and 110: Message Details this value is the s
Page 111 and 112: 12 Maintenance The [Ensemble] > [Ma
Page 113: Purge Management Data To the right
Page 117 and 118: Lookup Settings When the Run Archiv
Page 119 and 120: Enterprise Message Bank Click Save
Page 121 and 122: Enterprise Message Bank • The Mes
Page 123: Enterprise Message Bank Pattern cha
Page 126 and 127: Testing Service Enable Testing If t
Page 129 and 130: 14 EDI / HL7 Manager The [Ensemble]
Page 131 and 132: Index A actor pool and jobs, 35 and
Page 133 and 134: starting, 4 tasks to perform, 15 En
Page 135 and 136: R Reply Code Actions field, 61, 62
show all

Managing Ensemble Productions - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?