M I O app User Guide. a n a g e r. Version

Transcription

1 M I O app User Guide M a n a g e r Version

2 MIOsoft Corporation U.S. Corporate Headquarters 33 East Main Street Madison, WI Copyright MIOsoft Corporation, All Rights Reserved. No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of MIOsoft Corporation. MIOapp, MIObdt, MIOdata, MIOdb, MIOdeveloper, and MIOviewer are registered trademarks of MIOsoft Corporation. All other product or company names mentioned in this publication are trade names, trademarks, or registered trademarks of their respective owners.

3 Table of Contents Table of Contents MIOsoft MIOapp Manager User Guide... 1 Table of Contents... 2 Chapter 1: Introduction MIOapp Manager Map of MIOapp Manager Log in and out Log in Log out Change your password Definitions and important concepts MIOapp Resources and slices Resource sets Identical web resources Environments Manipulate MIOapp Manager Resize Keyboard shortcuts Chapter 2: Containers Definition of a container Containers and container contents Available containers Processing Slices Quotas and availability The environment pane Slice allocation Injectors Container types Chapter 3: Create and edit MIOapps Find MIOapps View MIOapps MIOsoft Confidential - For licensed use only

4 MIOsoft MIOapp Manager User Guide Select MIOapps Select multiple MIOapps View MIOapps by environment Create a container Select the new container's resource set Duplicate an existing container Delete Delete a container Clear a container Lock and allocate containers Allocate slices Deallocate slices Lock a container Unlock a container Start, stop, and open MIOapps Start Start in suspended mode Stop Automatic restart Open the console Web servers Start a web server Stop or shut down a web server Open a portal in a web browser View web URLs Add, remove, or change a web resource Configure automatic scaling Chapter 4: Monitor and deploy MIOapps Monitor Identification information The details pane The description pane Add or change a MIOapp's description Refresh and show changes Refresh Complete refresh MIOsoft Confidential - For licensed use only 3

5 Table of Contents Show changes View details Slice details Server details Exceptions Use show changes and slice details Gauge the distribution of your MIOapp's work MIOapp status: The information pane Web server status Export and import MIOapp configuration MIOapp metadata Export a MIOapp Export a MIOapp configuration Import a MIOapp Deploy an upgrade Configuration deployment and possible discrepancies Discrepancy reports Chapter 5: Maintenance and recovery Compact or resize Create a compact target container Compact a MIOapp Resize a MIOapp Checkpoints Create a checkpoint Revert to a checkpoint Resource replication Ghost MIOapps Hot standby Web servers Continuous loading: Capture files Batch loading Snapshot backups Back up a MIOapp and its data Back up data for reloading Glossary MIOsoft Confidential - For licensed use only

6 MIOsoft MIOapp Manager User Guide Figures and tables MIOsoft Confidential - For licensed use only 5

7 Chapter 1: Introduction Chapter 1: Introduction 1.1 MIOapp Manager With MIOsoft MIOapp Manager, you can easily and effectively administer your organization s MIOapps. Whether you want to create, edit, or manage a MIOapp, the tools you need are at your fingertips. You never have to worry about the complex questions of how to put your MIOapps to work in your organization s private cloud: MIOapp Manager and its underlying MIOsoft MIOedge platform have already answered them for you, while the MIOsoft operations team handles the maintenance and management of your cloud s hardware. With MIOapp Manager, your only concern is making sure that your MIOapps meet the needs of your business. 1.2 Map of MIOapp Manager MIOapp Manager has four panes and a menu bar (fig. 1-1) Figure 1-1. MIOapp Manager (annotated) 1.3 Log in and out Log in Your organization s MIOedge configuration dictates whether you have to log in before accessing any of MIOapp Manager s functions. If you do have to log in, your organization might use multiple security servers. You need to know which security server(s) you can log in to, as well as your MIOedge MIOsoft Confidential - For licensed use only

8 MIOsoft MIOapp Manager User Guide username and password. If you do not have a MIOedge username and password, or you do not know which security server to use, contact your organization s MIOedge security administrator. To log in to a MIOedge security server: 1. Open MIOapp Manager. 2. Click Login in the main menu bar, prompting the Login menu (fig. 1-2). Figure 1-2. Login menu 3. Click Login, prompting the Log in dialog box (fig. 1-3). Figure 1-3. Log in dialog box 4. Select the security server you want to log in to from the list in the Security server area. 5. Enter your MIOedge username into the User name field. 6. Enter your MIOedge password in the Password field. 7. Click Log in. MIOapp Manager logs you in MIOsoft Confidential - For licensed use only 7

9 Chapter 1: Introduction Log out If you are logged in through a security server, log out before you stop using MIOapp Manager and end your MIOedge session. This prevents unauthorized users from gaining access to MIOedge through an unattended machine and lets MIOedge terminate your session in a more orderly way. To log out: 1. Click Login in the main menu bar, prompting the Login menu. 2. Click Logout username, where username is your MIOedge username. The system immediately logs you out of MIOedge. 1.4 Change your password You can change your login password at any time. By default, your password must: Be at least 12 characters Be different from all your previous passwords Contain at least one of each character class: Numeric digit (0-9) Uppercase letter (A-Z) Lowercase letter (a-z) Non-alphanumeric character #, $, etc.) Have no more than 5 of any character class in a row MIOapp Manager lists these requirements in the Change password dialog box. If your organization has customized your cloud s password requirements, the dialog box s requirements list contains the customized rules. To change your password: 1. Click Login in the main menu bar, prompting the Login menu. 2. Click Change password, prompting the Change password dialog box (fig. 1-4) MIOsoft Confidential - For licensed use only

10 MIOsoft MIOapp Manager User Guide Figure 1-4. Change password dialog box 3. Enter your new password in both data entry fields. MIOapp Manager does not activate the OK button until both versions of your password match. 4. Click OK. MIOedge changes your password immediately and returns you to MIOapp Manager. Use your new password to log in from now on. If your password does not meet all the requirements, MIOedge prompts you to correct your password and lists the requirement(s) that must be met. 1.5 Definitions and important concepts MIOapp A MIOapp is a comprehensive definition of everything needed for a complex, data-driven enterprise application. A MIOapp can be developed in MIOapp Console and then run in the cloud, where security, reliability, and scalability are added without the intervention of developers MIOsoft Confidential - For licensed use only 9

11 Chapter 1: Introduction When a MIOapp is deployed to the cloud, it leverages the MIOedge platform s distributed computing technology to create a MIOdb database, allowing data and computation to take place across as many servers as the specific MIOapp needs. This makes MIOapp applications extremely flexible, so they can be used for applications with smaller amounts of data or users and the largest enterprise applications alike. A MIOapp file can be used to share MIOapps and to deploy a MIOapp to the cloud. A MIOapp file contains all the definitions required for a MIOapp, including: An object-oriented database and application logic model Data cleansing, standardization, and consolidation rules Import data format definitions, including transformations Report and export format definitions Web portal and web services definitions When you design your MIOapp, you do not need to address the complexities of scalable distributed computing: MIOedge addresses these automatically. Everything you need to do to build your MIOapp can be done using MIOapp Console s graphical interface, including: Defining all the pieces of a MIOapp mentioned above Viewing data sources to help determine the correct rules and formats Loading and exporting data to test the database model, application logic, and rules Operating web portals and allowing you to test them in a web browser of your choice Operating web services servers and clients to test their intended functionality Throughout the process of defining your MIOapp, changes are saved directly to a MIOapp file Resources and slices Your MIOapp runs on one or more computing resources, which you assign it. Each resource defines a certain share of your MIOapp s work, which is to be performed by a slice of actual computing power. The resources you assign to your MIOapp specify how many slices you want and what share of the work each should do. After you assign the resources, MIOedge uses them as templates to create the slices of computing power for your MIOapp and distribute its work accordingly. Assigning your MIOapp more than one slice allows it to take advantage of MIOedge s cloud computing capabilities. MIOapps can use two different kinds of resources: database resources and web MIOsoft Confidential - For licensed use only

12 MIOsoft MIOapp Manager User Guide resources. Database resources are at the core of your MIOapps: every MIOapp has a database with the data it loads and uses database slices to perform any processing. Each database slice in a MIOapp runs independently of other slices except while they exchange data. After a shutdown and restart, database slices resume processing at the point they left off. Slice processing resumes regardless of whether the shutdown was intentional or unintentional, as in the event of a power failure. Web resources handle any interaction between your MIOapp and a web browser. Shutting down a web server does not shut down its MIOapp, although the MIOapp loses the capacity to gather data from web input Resource sets The MIOsoft operations team manages your resources for you, including the creation of resource sets. These resource sets define different combinations of resources and MIOedge engines available for your MIOapps. The resources in a resource set are both database and web resources. The more database resources in a resource set, the more processing power it has. Every time you create a MIOapp, you select which combination of resources you want the MIOapp to have. MIOapp Manager implements these resources as part of a container, which you use to hold your MIOapp. You can select high-power resource sets for containers which will hold high-priority or large MIOapps and lower-power resource sets for containers which will hold smaller MIOapps. As soon as you select a resource set, MIOapp Manager creates a new container with slices to match the definition you selected and uses the associated MIOedge engine to run the container s MIOapp. If you need a MIOapp with a web resource, create your container by selecting a resource set with a web resource attached. If the resource set you need is not associated with a web resource, create your container with the resource set and contact the MIOsoft operations team to have a web resource assigned to your container. If you have questions about your resource sets, or you need a new resource set, contact the MIOsoft operations team Identical web resources The definition of the web resource includes a port number for the resource to use. If two web servers on the same host use the same port, they cannot be active at the same time. Be sure a new MIOapp will not need its web server at the same time as 2013 MIOsoft Confidential - For licensed use only 11

13 Chapter 1: Introduction any MIOapps previously created with the same resource set need their web servers Environments An environment is a group of machines that provide computing power. MIOapps belong to an environment when they use any slices from the environment. The MIOsoft operations team implements your organization s desired environments. Your organization might, for example, create a different environment for each department. Your organization s security settings may allow you access to some or all of your organization s environments. Each environment has its own quota, use, and availability calculations (see Quotas and availability) visible in MIOapp Manager s environment pane. 1.6 Manipulate MIOapp Manager Resize You can resize MIOapp Manager by clicking and dragging an edge or corner of the MIOapp Manager window. You can also resize the details and description panes by clicking and dragging the border between them (fig. 1-5); this is the only adjustable pane sizing in MIOapp Manager. Figure 1-5. Resize details and description panes Keyboard shortcuts MIOapp Manager has some keyboard shortcuts which make it easier to perform common actions. See table 1-A for a complete list of keyboard shortcuts. Table 1-A. Keyboard shortcuts Key Action For more information, see combination F5 Refresh Refresh Shift + F5 Complete refresh Complete refresh F6 Show changes Show changes Ctrl + S Start Start Ctrl + Shift + S Stop Stop Ctrl + W Start a web server Start a web server MIOsoft Confidential - For licensed use only

14 MIOsoft MIOapp Manager User Guide Ctrl + Shift + W Stop a web server Stop a web server Ctrl + C Create a MIOapp 3.2 Create a container container Ctrl + Shift + C Delete the container Delete a container Ctrl + L Lock the container Lock a container Ctrl + Shift + L Unlock the container Unlock a container Ctrl + A Allocate the Allocate slices container s slices Ctrl + Shift + A Deallocate the Deallocate slices container s slices Ctrl + D Change description Add or change a MIOapp s description Ctrl + O Open the console Open the console Ctrl + I Import a MIOapp Import a MIOapp Ctrl + U Deploy an upgrade Deploy an upgrade 2013 MIOsoft Confidential - For licensed use only 13

15 Chapter 2: Containers Chapter 2: Containers 2.1 Definition of a container A container provides the resources you need to run a MIOapp in the cloud. It establishes two things: a name and a resource set, which MIOapp Manager uses to allocate physical resources, or slices. When you create a container, you choose the name of the container and one of a number of pre-defined resource sets. The name identifies the container and is unique. Once you name a container, you cannot change it; MIOapps take the name of their container. The resource set defines what resources MIOapp Manager should assign to the container and what engine it should use to run the MIOapp Containers and container contents It is almost always useful in MIOapp Manager to distinguish between containers and MIOapps. The exception is the information pane, where both MIOapps and containers are listed under MIOapp. A container has slices and an engine, but no metadata or configuration. A MIOapp has metadata and a configuration, but no slices or engine. Without slices and an engine, a MIOapp cannot run: MIOapps must be placed in containers for them to function. Because you need containers to manage and run MIOapps, MIOapp Manager lists containers both with and without MIOapps under MIOapp in the information pane. MIOapps in a container thus also appear in the information pane, but exported MIOapp files never appear until they are imported into a container. In the MIOapp menu, MIOapp Manager identifies its container-specific features: creating, deleting, clearing, locking, and allocating. Knowing the difference between a MIOapp and its container makes it clear how container-specific features behave and what they might affect, so you can better choose the correct feature to accomplish your goals Available containers Because the point of a container is to hold a MIOapp, your available containers are listed under the MIOapp column in your information pane. Most of MIOapp Manager s real estate is devoted to giving you information about your MIOapps. If you do not have any MIOapps in your containers, MIOapp Manager continues to report on your containers status alone. Status indicator symbols, beside MIOsoft Confidential - For licensed use only

16 MIOsoft MIOapp Manager User Guide your container names, provide a visual indicator of your containers states. See table 2-A for a full list of possible status indicator symbols. Table 2-A. Status indicator symbols Symbol color Meaning More information green Started, no reported problems Start white Stopped Stop green and white Started, automatic scaling enabled for multiple slices Configure automatic scaling red Started, at least one reported Start in suspended mode problem red and blue Recovered, at least one Ghost MIOapps unresolved host conflict blue Recovered, original host slice Ghost MIOapps now available yellow Waiting for information Refresh and show changes Symbol shape Meaning More information circle Primary MIOapp Chapter 3: Create and edit MIOapps astroid Standby MIOapp 5.4 Hot standby circle with web Web server 3.6 Web servers overlay padlock Locked Lock a container no padlock Unlocked Unlock a container universal no symbol Not enough slices available in quota to start Quotas and availability 2.2 Processing Slices As discussed in Resources and slices and Resource sets, your MIOapp uses an assigned number of slices of computing power to perform its work. Your organization s MIOedge cloud is made up of a certain number of slices, with each slice being essentially equal in processing capability. The Slices column in MIOapp Manager s information pane refers to the total number of slices assigned to the container. For more information about slices assigned to a container, see View details Quotas and availability The number of slices your organization can use at any one time has an upper limit: 2013 MIOsoft Confidential - For licensed use only 15

17 Chapter 2: Containers the quota. Your quota is equal to the total number of slices your organization purchased from MIOsoft. If your organization chose to divide its slices into environments, each environment also has a quota. If you do not have access to all of your organization s environments, the quota you see in MIOapp Manager can be lower than your organization s quota as a whole. Only slices assigned to started MIOapps or slices allocated to a specific MIOapp count against your quota. Slices assigned to stopped MIOapps are not counted against your quota, so you can have more slices assigned to your stopped MIOapps than your quota has available. MIOapp Manager does not count security server container slices or injector slices of size zero against the quota; see Injectors for information about injectors. You can get information about your quota situation from the environment pane The environment pane The environment pane provides you with information about the quota status of your available environment(s) (fig. 2-1). Figure 2-1. The environment pane Environment indicates the names of the environments you have access to. Quota indicates the slice quota of the environment. Used indicates the number of slices assigned to started MIOapps plus the number of slices allocated to specific MIOapps. Avail indicates the number of slices currently available for use by stopped, deallocated MIOapps. MIOapp Manager calculates your available slices by subtracting your used slices from your slice quota. If you attempt to start a MIOapp which requires more slices than you have available, MIOapp Manager displays an error message and does not start your MIOapp (fig. 2-2) MIOsoft Confidential - For licensed use only

18 MIOsoft MIOapp Manager User Guide Figure 2-2. Slice quota exceeded pop-up When you start and stop MIOapps, the information in the environment pane updates automatically. You do not need to refresh MIOapp Manager to check on the current status of your quota. Sorting the environment pane MIOapp Manager defaults to arranging your environments in alphabetical order. However, you can sort your list of environments by any of the information available in the environment pane. To sort by a column in the environment pane: Click on the column header. Your first click sorts the column least-to-most, or A-to-Z for the environment name. Click on the column header a second time to reverse the sort order. MIOapp Manager indicates the direction of the current sort with an embossed arrow in the column header. A downward-pointing arrow ( ) indicates a least-to-most, A-to-Z sort, while an upward-pointing arrow ( ) indicates a most-to-least, Z-to-A sort. The sort direction arrow does not appear until you sort by a column Slice allocation Allocation allows you to set slices aside for use by a particular container. No other container can use the slices allocated to that container, even if the container you allocated slices to is stopped. Slice allocation is useful when a critical MIOapp does not run constantly, such as a MIOapp that does your company s billing, but runs only once a day at 2 a.m. and is stopped except during its early-morning run. Because it is important to your company that the billing MIOapp run successfully, you 2013 MIOsoft Confidential - For licensed use only 17

19 Chapter 2: Containers might want to ensure that the billing MIOapp always has enough slices to start, even if other MIOapps also try to start at 2 a.m. To achieve this, you can allocate the billing MIOapp s slices. Allocated slices can only be used by the MIOapp they are allocated to, and therefore are considered in use even if the MIOapp is not currently running. If you use a workflow server to allocate the billing MIOapp s slices at 4:00 p.m., the workflow can a notification if allocation fails and the recipient(s) can address the issue promptly because they receive the notification at a time when they are readily available. This combination of slice allocation and the workflow server allows you to ensure that the billing MIOapp always has slices available to start while letting you use those slices during the day. For information about allocating slices to a container, see Allocate slices. For information about using a workflow server, see the MIOsoft Workflow Console User Guide Injectors Most MIOapps use one or more injectors, which act as a gateway to the MIOapp. An injector accepts data from one or more data sources and then directs the subsequent flow of work to the MIOapp s slices. Any MIOapp slice can be an injector, even if it is doing other work. However, injectors are most efficient when they do not have other work. The MIOsoft operations team creates these injectors by assigning a slice zero shares of work. Because they have no work share, these slices cannot do anything except act as injectors. Injector slices of size zero do not count against your slice quota. 2.3 Container types MIOapp Manager allows you to work with three kinds of containers: MIOapp, workflow, and backup. MIOapp containers are discussed in detail in Containers and container contents. Workflow containers are used to build automated MIOapp-managing operations, including container starts and stops, data loading, and report extraction. For more information about workflows, see the MIOsoft Workflow Console User Guide. Backup containers are used to create independent backups of mqcapture and web MIOsoft Confidential - For licensed use only

20 MIOsoft MIOapp Manager User Guide capture files. For more information about backup containers, see the MIOsoft Backup Console User Guide. Each container type is restricted to its particular function. MIOapp containers can only be edited with MIOapp Console, workflow containers with Workflow Console, and backup containers with Backup Console. MIOapp Manager does not provide a function to change a container s type. The MIOapp Manager features described in chapters 3-5 apply to all container types, although instructions generally refer to MIOapp containers and MIOapps for simplicity MIOsoft Confidential - For licensed use only 19

21 Chapter 3: Create and edit MIOapps Chapter 3: Create and edit MIOapps 3.1 Find MIOapps View MIOapps MIOapp Manager collects your MIOapps information into one primary window, allowing you to focus on access to and information about your MIOapps. The bulk of your MIOapp Manager window is the central information pane, which is devoted to monitoring your MIOapps. It lists your existing containers in alphabetical order. If you have more than one environment available, MIOapp Manager shows the MIOapps from all of your environments by default. A secondary window provides slice-level information about individual MIOapps; see Viewing slice details for more information Select MIOapps To perform any action on a MIOapp and/or container, you need to select it first. To select a single MIOapp: Click the MIOapp in the information pane. Selected MIOapps are highlighted in gray Select multiple MIOapps You can select multiple MIOapps using the standard keyboard commands. You can apply start/stop, allocation, and (un)locking functions to a multi-mioapp selection. To select multiple non-adjacent MIOapps: Hold down the Ctrl key and click each MIOapp you want to select. To select multiple adjacent MIOapps: Select the uppermost MIOapp of the group you want to select, hold down the Shift key, and select the final MIOapp of the group MIOsoft Confidential - For licensed use only

22 MIOsoft MIOapp Manager User Guide MIOapp Manager selects all of the intervening MIOapps as well. To deselect a MIOapp: Hold down the Ctrl key and click the each MIOapp you want to deselect. To perform a function on a multi-mioapp selection: Follow the instructions for performing the function on a single MIOapp, but with multiple MIOapps selected instead of one. If you are starting, allocating slices, or deallocating slices, all of the MIOapps you select must have the opposite status stopped, deallocated, and allocated, respectively for MIOapp Manager to perform the function. If you are stopping, locking, or unlocking, you do not need all the selected MIOapps to have the opposite status for MIOapp Manager to perform the function View MIOapps by environment You can also view MIOapps from one or a selected subset of your environments and hide the remaining MIOapps. To view a subset of your MIOapps: Select only the environment(s) with the MIOapps you want to view. You can select multiple environments using the standard Ctrl and Shift key methods described in the previous section. As soon as you deselect an environment, MIOapp Manager hides its MIOapps. Showing and hiding MIOapps using the environments pane only affects their display in the information pane; their status and operation is unaffected. 3.2 Create a container You can create a new container either by selecting a resource set or by duplicating an existing container. If you choose to select a resource set, you can select from a list which includes the sets names and the numbers of resources each containers. You also see a version number associated with each resource set, which identifies the engine that MIOedge uses to run the container s contents. You create a container using the upper portion of the MIOapp section of the MIOapp menu (fig. 3-1), which is fourth from the top MIOsoft Confidential - For licensed use only 21

23 Chapter 3: Create and edit MIOapps Figure 3-1. MIOapp section of the MIOapp menu Select the new container's resource set To create a new container and select its resource set: 1. Make sure no MIOapps are selected in the information pane. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Create MIOapp container, Create workflow container, or Create backup container, prompting a resource set selection dialog (fig. 3-2). Figure 3-2. Resource set selection dialog 4. Select the resource set you want your new container to use. 5. Click OK, prompting the Enter MIOapp container information dialog box (fig. 3-3) MIOsoft Confidential - For licensed use only

24 MIOsoft MIOapp Manager User Guide Figure 3-3. Container name dialog 6. Enter your new container s name in the MIOapp name field. You cannot have two containers with identical names. Your MIOapp name can include: letters: a-z and A-Z numbers: 0-9 periods commas underscores hyphens plus signs Other special characters and spaces are not allowed. The OK button is enabled only after you enter an appropriate name for your container. 7. Click OK. You return to MIOapp Manager, which pauses briefly while it creates the new container. The new container appears in the information pane (fig. 3-4) in alphabetical order; MIOapp Manager orders numbers by their individual digits, not by the number as a whole. If your quota has enough available slices to start the container, MIOapp Manager does so. If your quota does not have enough available slices, your new container is stopped MIOsoft Confidential - For licensed use only 23

25 Chapter 3: Create and edit MIOapps Figure 3-4. New container in information pane Duplicate an existing container Duplicating an existing container is particularly useful if you plan to import or compact an existing MIOapp into the new container. Duplicating the source MIOapp s container ensures that your new container can support the incoming MIOapp s metadata and configuration. Duplicating a container does not mean the new container uses the same slices as the source container; when the new container uses the source container s resource template, it creates a separate (but identical) set of slices. If you duplicate a container with a web resource, your new container s web server uses the same port as the original web server. Web servers sharing a port cannot run at the same time; see Identical web resources for more information. To duplicate an existing container: 1. Select the container you want to duplicate. The container can be either started or stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. Figure 3-5. Container name dialog 3. Click Create MIOapp container, Create workflow container, or Create MIOsoft Confidential - For licensed use only

26 MIOsoft MIOapp Manager User Guide backup container, prompting the Enter MIOapp container information dialog box (fig. 3-5). 4. Enter your new container s name in the MIOapp name field. You cannot have two containers with identical names. Your MIOapp name can include: letters: a-z and A-Z numbers: 0-9 periods commas underscores hyphens plus signs Other special characters and spaces are not allowed. The OK button is enabled only after you enter an appropriate name for your container. 5. Click OK. You return to MIOapp Manager, which pauses briefly while it creates the new container. The new container appears in the information pane (fig. 3-6) in alphabetical order. MIOapp Manager orders numbers by their individual digits, not by the number as a whole. Apollo_11 precedes Apollo_8 because the leading 1 in 11 comes before 8. Figure 3-6. Duplicate container in information pane As with creating a container by selecting the resource set, your new container is started if your quota has enough slices to do so and stopped if it does not. 3.3 Delete MIOapp Manager offers two kinds of deletion for your MIOapps and containers MIOsoft Confidential - For licensed use only 25

27 Chapter 3: Create and edit MIOapps Clearing the container deletes the MIOapp completely, including all data and parts of the object model, but leaves the container intact. Deleting the container deletes the MIOapp and also the container. Deletion is carried out from the deletion section of the MIOapp menu (fig. 3-7), which is at the bottom. Figure 3-7. Deletion section of the MIOapp menu Delete a container Deleting a container permanently erases the container. If you delete a container with a MIOapp, all of the MIOapp s data, metadata, databases, and local files are also deleted. You cannot undo deleting a container or recover anything associated with the container from MIOapp Manager. To delete a container: 1. Select the container you want to delete. The container must be stopped, deallocated, and unlocked. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Delete container, prompting a confirmation dialog (fig. 3-8). Figure 3-8. Container deletion warning pop-up 4. Click Yes. MIOapp Manager pauses briefly while it deletes your container and removes it from the information pane. You can also use the keyboard shortcut Ctrl+Shift+C to delete a container MIOsoft Confidential - For licensed use only

28 MIOsoft MIOapp Manager User Guide Clear a container Clearing a container completely deletes all data, metadata, and the configuration; the container retains only its name, description, and slices. When you clear a container, you must have enough slices available in your quota for MIOapp Manager to start it. To clear a container: 1. Select the container you want to clear. The container must be stopped, unlocked, and you must have enough slices available in your quota for MIOapp Manager to start it. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Clear container, prompting a confirmation dialog (fig. 3-9). Figure 3-9. Clear a container warning pop-up 4. Click Yes. You return to MIOapp Manager; the container you cleared is now started. If you click No, you do not clear the container and you return to MIOapp Manager. 3.4 Lock and allocate containers Locking and allocation of containers allows you to control the level at which a container s contents can be accessed and whether a MIOapp has reserved slices so it can run, respectively. You apply these functions through the lock and allocate section of the MIOapp menu (fig. 3-10), which is the second section from the bottom MIOsoft Confidential - For licensed use only 27

29 Chapter 3: Create and edit MIOapps Figure Lock and allocation section of the MIOapp menu Allocate slices Allocating slices to a container guarantees that your container can always start, but counts those allocated slices against your quota even while the container is stopped. To allocate slices to a MIOapp: 1. Select the MIOapp that you want to allocate slices to. The MIOapp can be either started or stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Allocate container. This returns you to MIOapp Manager. You can also use the keyboard shortcut Ctrl+A to allocate a container. If you allocated to a stopped MIOapp, a green outline appears around the MIOapp s status indicator symbol. You can also look at the Used column in your environment pane and see that MIOapp Manager considers the slices you allocated to be in use even though the MIOapp is stopped. If you allocated to a started MIOapp, you do not see any effects from the allocation until the MIOapp is stopped. You can allocate slices to more than one MIOapp at the same time. This does not allocate one set of slices to be shared among those MIOapps: it allocates each MIOapp all the slices it needs. You cannot allocate the same slices to multiple MIOapps, even if the MIOapps would not use the slices simultaneously. You also cannot allocate more slices than are available in your quota. MIOapp Manager displays a pop-up error message (fig. 3-11) if you attempt this MIOsoft Confidential - For licensed use only

30 MIOsoft MIOapp Manager User Guide Figure Cannot allocate container pop-up Deallocate slices Deallocating a container makes its slices generally available for use. If you deallocate a container, the container is no longer guaranteed sufficient slices to start at any time, but the container s slices no longer count against your quota while it is stopped. Deallocation of a started MIOapp does not take effect until the MIOapp is stopped. To deallocate a container: 1. Select the MIOapp that you want to deallocate. The MIOapp can be either started or stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Deallocate container. You can also use the keyboard shortcut Ctrl+Shift+A to deallocate a container. If you deallocated a stopped MIOapp, the green outline disappears from the MIOapp s status indicator symbol. You can also look at the Used column of the environment pane and see that MIOapp Manager no longer considers the slices you deallocated to be in use. If you deallocated a started MIOapp, you do not see any effects from the deallocation until the MIOapp is stopped Lock a container Locking a container prevents you from performing most overwriting and clearing actions. You can lock or unlock a container at any time; locking is not intended to be an absolute protection against editing. Use locking to indicate that a container should not be edited and prevent the use of wholesale overwriting functions. You cannot perform the following operations on a locked container: 2013 MIOsoft Confidential - For licensed use only 29

31 Chapter 3: Create and edit MIOapps Use Import MIOapp Use the container as the target of a deployed upgrade Use the container as the target of a compacting or resizing process Use Revert to checkpoint Delete the container Clear the container You can perform the following operations on a locked container: Change the container s description Use Start to start the container Open the container s console and make changes Use Stop to stop the container Export the container s MIOapp and/or its configuration Use the container as the source of a deployed upgrade Use the container as the source of a compacting or resizing process Create a checkpoint Allocate and deallocate the container Configure the container s web server automatic scaling Toggle the container s Automatically restart flag You can lock and unlock containers at will. To lock a container: 1. Select the container you want to lock. The container can be either started or stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Lock container. After a brief pause, a padlock icon appears next to the status indicator symbol of the container you selected; the container is now locked. You can also use the keyboard shortcut Ctrl+L to lock a container Unlock a container Unlocking a container removes the restrictions locking placed on it. An unlocked container can have wholesale overwriting functions performed on it or be deleted. To unlock a container: 1. Select the container that you want to unlock. The container can be either started or stopped MIOsoft Confidential - For licensed use only

32 MIOsoft MIOapp Manager User Guide 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Unlock container. After a brief pause, the padlock icon disappears from your selected container s status indicator symbol; the container is now unlocked. You can also use the keyboard shortcut Ctrl+Shift+L to unlock a container. 3.5 Start, stop, and open MIOapps Starting, stopping, and opening MIOapps are the basic tasks that allow you to run and edit a MIOapp. You can check a MIOapp s start/stop status in the information pane s Status column (fig. 3-12). Figure MIOapp start/stop status in the information pane Each MIOapp has a status indicator symbol. The color of the symbol reflects the MIOapp s current status: green for started and white for stopped. Stopped MIOapps have a universal no symbol if there are not enough slices in your quota to start the MIOapp. See table 4-A in MIOapp status: The information pane for a complete table of the status indicator symbol meanings. In addition to the status indicator symbol, started MIOapps have bold names in the information pane. Starting, stopping, and opening a MIOapp s console is performed through the start/stop section of the MIOapp menu (fig. 3-13), which is second from the top MIOsoft Confidential - For licensed use only 31

33 Chapter 3: Create and edit MIOapps Figure Start/stop section of the MIOapp menu Start Starting a MIOapp starts all its database slices. You start and stop any associated web servers independently; see 3.6 Web servers for more information. To start a MIOapp: 1. Select the MIOapp you want to start. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Start. After a brief pause, the information pane refreshes; the MIOapp name is in bold and the status indicator symbol updated Start in suspended mode If one of your MIOapps develops a problem during processing, you can start the MIOapp in suspended mode. As with a normally started MIOapp, you can open, edit, and debug a suspended MIOapp. Injection of loaded records continues, but the injection records are not acted upon in a suspended MIOapp. This makes a suspended MIOapp especially useful if your MIOapp is experiencing loading problems, as you can open and edit the suspended MIOapp without the error occurring. Once you have resolved your problem, you can stop the MIOapp and then restart it normally. When your MIOapp is restarted normally, it uses its new database schema to resume processing at the point just prior to the transaction that caused the problem. To start a MIOapp in suspended mode: 1. Select the MIOapp you want to start in suspended mode. The MIOapp must be stopped MIOsoft Confidential - For licensed use only

34 MIOsoft MIOapp Manager User Guide 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Start suspended. You return to MIOapp Manager. Your selected MIOapp starts, but reports a paused state. You can now debug your MIOapp. To remove a MIOapp from suspended mode: 1. Resolve the problem which prompted you to use suspended state mode. 2. Stop the MIOapp normally. 3. Start the MIOapp normally. Use the instructions in Start and Stop for steps 2 and 3, respectively Stop Stopping a MIOapp prompts the system to shut down all of the MIOapp s processes, on all slices. Stopping a MIOapp with web servers shuts down both the MIOapp and its associated servers; however, stopping the web servers does not stop the associated MIOapp. Stopping a MIOapp allows you to perform routine maintenance or free the MIOapp s slices for use by another MIOapp, if the MIOapp is not allocated. Certain tasks a MIOapp performs, such as loads, always resume at the point they were interrupted when you restart the MIOapp. Some MIOedge tasks are not interruptible: sorts, frequencies, reports, extracts, and exports. If you stop a MIOapp in the middle of one of these processes, the process does not resume when you restart the MIOapp; you have to restart the process from the beginning. Your MIOapp might also spawn tasks which take place outside of the MIOedge environment, which might or might not be interruptible. When stopping a MIOapp, check that it is not in the middle of an uninterruptible task, or, if it is, that you are willing to restart the task and your interfaced system can handle any duplicate data the restart produces MIOsoft Confidential - For licensed use only 33

35 Chapter 3: Create and edit MIOapps To stop a MIOapp: 1. Select the started MIOapp that you want to stop. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Stop. After a brief delay, the indicator pane refreshes. The MIOapp you stopped now has a white status indicator symbol Automatic restart You can add an automatic restart flag to a container to specify that the container, if stopped by any means other than a Stop command, should be automatically restarted when possible. The container does not automatically restart after being stopped using a Stop command even if this flag is set. Unlike the standard Start and Stop commands, the automatic restart flag is located in the MIOapp section of the MIOapp menu. To toggle the automatic restart flag: 1. Select the container you want to toggle the flag for. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. 3. Click Automatically restart. If you added the flag to the MIOapp, MIOapp Manager adds a checkmark beside the Automatically restart menu entry when the MIOapp is selected; if you removed the flag, MIOapp Manager removes the checkmark Open the console Opening the console gives you access to all the editing tools necessary to build or use your MIOapp: MIOapp containers open MIOapp Console, workflow containers open Workflow Console, and backup containers open Backup Console. Once your MIOapp is in production, you can also make further changes or fixes, if necessary, through the console. To open the console: 1. Select the MIOapp you want to edit. The MIOapp must be started MIOsoft Confidential - For licensed use only

36 MIOsoft MIOapp Manager User Guide 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Open console, prompting MIOapp Console (fig. 3-14), Workflow Console, or Backup Console to open, as appropriate to the selected container. Figure MIOapp Console For information about using MIOapp Console to build a MIOapp, see the MIOsoft MIOdeveloper and MIOapp Console User Guide. For information about using Workflow Console to create workflows, see the MIOsoft Workflow Console User Guide. For information about using Backup Console to back up MQ queues, see the MIOsoft Backup Console User Guide. 3.6 Web servers Web servers support your MIOapp s web-based input and presentation functions. Each web server resource is assigned a port, so only one MIOapp can use a web server resource at any one time. To avoid conflicts between MIOapps, creating a separate web resource for every MIOapp that needs one is strongly recommended. MIOapps which are expected to carry heavy loads can have more than one web resource slice assigned. Web resources are controlled through the web resource section of the MIOapp menu (fig. 3-15), which is third from the top. By default, web load automatic scaling is enabled for web resources MIOsoft Confidential - For licensed use only 35

37 Chapter 3: Create and edit MIOapps Figure Web resource section of the MIOapp menu Start a web server Starting a MIOapp s web server makes its web portals available for use. You can edit the web portals in MIOapp Console while the web server is not running, but you and other users cannot view the web portals until you start the web server. MIOapp Manager does not start the web server automatically when you start a MIOapp; you must always start the web server separately. To start a web server: 1. Select the container with the web server you want to start. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Start web server. You can also start the web server using the Ctrl+W keyboard shortcut. After a brief pause, the information pane refreshes. The web server you started now has a green status indicator symbol. You and other portal users can now view web portals or URLs Stop or shut down a web server Stopping a web server immediately ends the web server s operations and makes the MIOapp s web portals unavailable through the browser. You can still edit the web portals using MIOapp Console. If you stop a MIOapp, its web server also stops automatically. Shutting down a web server ends the web server s operations in an orderly way. The web server no longer allows new logins; after the final currently logged in session logs out, the web server stops. To stop a web server: MIOsoft Confidential - For licensed use only

38 MIOsoft MIOapp Manager User Guide 1. Select the MIOapp with the web server you want to stop. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Stop web server. You can also stop the web server using the Ctrl+Shift+W keyboard shortcut. After a brief pause, the information pane refreshes. The web server you stopped now has a white status indicator symbol. To shut down a web server: 1. Select the MIOapp with the web server you want to shut down. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Shutdown web server. After all current user sessions have ended, the web server stops Open a portal in a web browser MIOapp Manager s Open web browser feature lets you open any web portal your MIOapp generates in any web browser your computer has installed. To open a web browser: 1. Select the MIOapp generating the web page you want to open. Both the MIOapp and its web server must be started. 2. Click MIOapp in the main menu bar. You can also right-click in the information pane instead. 3. Hover over Open web browser, prompting the web browser selection submenu (fig. 3-16). Figure Web browser selection submenu 4. Hover over your choice of web browser, prompting the web portal selection submenu (fig. 3-17) MIOsoft Confidential - For licensed use only 37

39 Chapter 3: Create and edit MIOapps Figure Web portal selection submenu 5. Click the web portal you want to open. The portal opens automatically, using the web browser you chose View web URLs You can also view a complete list of all URLs associated with a MIOapp without opening any of them. To view web URLs: 1. Select the MIOapp you want to view the URLs for. Both the MIOapp and its web server must be started. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click View web URLs. This prompts a pop-up window containing the URLs of the selected MIOapp s web portals (fig. 3-18). You can view the URLs in this window or copy its text to use elsewhere. To close the window, click the x in the upper right-hand corner. Figure URLs pop-up window Add, remove, or change a web resource You can add, remove, or change a MIOapp s web resource directly from MIOapp Manager. All three operations use the same Select web resources dialog box. Only assign a resource to one MIOapp. To open the Select web resources dialog box: 1. Select the MIOapp you want to edit the web resources of. If the MIOapp has MIOsoft Confidential - For licensed use only

40 MIOsoft MIOapp Manager User Guide any web resources, they must be stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Change MIOapp WebApp slices, prompting the Select web resources for MIOappName dialog box (fig. 3-19). Figure Select web resources dialog box Each web resource is listed in the format host.port, where host is the name of the machine the resource is located on and port is the port number the resource is assigned to. 4. Select or deselect the web resources you want to add to or remove from the MIOapp: a. To add a web resource to the MIOapp, select the name of the resource. b. To add all available web resources to the MIOapp, click the Select All button. c. To remove a web resource from the MIOapp, hold down the Ctrl key and select the name of the resource. d. To remove all web resources from the MIOapp, click the Select All button twice. 5. Click the OK button. You return to MIOapp Manager. There might be a pause while MIOapp Manager adds or removes a web server status icon, if necessary MIOsoft Confidential - For licensed use only 39

41 Chapter 3: Create and edit MIOapps Configure automatic scaling Automatic scaling allows you to implement web server balancing and computer resource allocation. You can configure individual scaling individually for each MIOapp, and set different values for burst traffic and sustained traffic. This is possible because MIOapp Manager polls the web servers for their state and the number of logged in sessions, or load, on each server at a configurable interval. You can set thresholds for a single poll and for an average of polls that, if met or exceeded, will trigger a server to stop or start. Single-poll thresholds are called burst traffic control and should be designed to handle rapidly changing server loads. Averaged-poll thresholds are called sustained traffic control and should be designed to handle fairly consistent server loads. To configure automatic scaling: 1. Select the MIOapp you want to implement automatic scaling for. It must have at least one web resource, and the web server must be stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Configure WebApp automatic scaling, prompting the Configure WebApp automatic scaling dialog box (fig. 3-20) MIOsoft Confidential - For licensed use only

42 MIOsoft MIOapp Manager User Guide Figure Configure WebApp automatic scaling dialog box 4. Configure the automatic scaling using the available fields, which are described in table 3-A. If a field has a red asterisk (*), its value is invalid. All fields must have valid values for automatic scaling to be implemented. 5. Click OK. You return to MIOapp Manager. When automatic scaling is enabled for a MIOapp with more than one web server slice and the web server is started, the web server status icon is partially colored with green on the bottom and white on the top. Table 3-A. Configure WebApp automatic scaling configuration options Option Description Enabled Determines whether automatic scaling is enabled MIOsoft Confidential - For licensed use only 41

43 Chapter 3: Create and edit MIOapps Minimum number of active slices Sample period Burst traffic control: Start a slice at avg. sessions Burst traffic control: Stop a slice at avg. sessions Sustained traffic control: Interval size Sustained traffic control: Start a slice at avg. sessions Sustained traffic control: Stop a slice at avg. sessions Slice options: Refuse new connections at sessions Slice options: Refuse new logins at sessions Select this checkbox to enable automatic scaling; deselect this checkbox to disable it. If you deselect the checkbox, MIOapp Manager preserves any values you entered in other fields. This checkbox is selected by default. Specifies the minimum number of active slices for the web server. Enter an integer of one (1) or greater. Specifies the interval at which each server is polled for its state and load. Each poll is used to determine whether loads meet burst traffic thresholds. Enter an integer. Specifies that another server should be started if a single poll of a slice returns a load that is at or greater than this number of sessions. Enter an integer. Specifies that a server should be stopped if a single poll of a slice returns a load that is at or less than this number of sessions. Enter an integer. Specifies the interval at which polled load samples are averaged to determine whether loads meet sustained traffic thresholds. Enter an integer greater than the integer specified for Sample period. Specifies that another server should be started if an averaged load sample returns a load that is at or greater than this number of sessions. Enter an integer. Specifies that a server should be stopped if an averaged load sample returns a load that is at or less than this number of sessions. Enter an integer. Specifies that a server will not accept new login requests once it has this number of new sessions. Existing sessions can continue to log in. Enter an integer. Specifies that a server will not accept new login requests or sessions once it has this number of sessions. New login attempts, including those from existing sessions, will be refused. Enter an integer MIOsoft Confidential - For licensed use only

44 MIOsoft MIOapp Manager User Guide Chapter 4: Monitor and deploy MIOapps 4.1 Monitor MIOapp Manager s monitoring and information functions allow you to get identification and status information about all of your MIOapps. Monitoring functions are controlled through the monitoring section of the MIOapp menu (fig. 4-1), which is first from the top. Figure 4-1. Monitoring section of the MIOapp menu Identification information The details and description panes (fig. 4-2) give you information about the currently selected container. Figure 4-2. Details and description panes The details pane Started shows the date and time of the MIOapp s most recent start. Created shows the date and time the MIOapp s container was created; it is reset every time the container is cleared or used as the target of an upgrade deployment, resize, or compacting process. It is also reset if the container is used as the target of a copy process, which can only be performed in MIOapp Platform Manager. MIOapp file shows the name of the MIOapp file most recently imported into the container. If no MIOapp files have been imported into the container, this column reads n/a The description pane If a MIOapp container has a description, it appears in full in this window. If the description is too long to fit in the pane, you can use the scroll bar on the right side 2013 MIOsoft Confidential - For licensed use only 43

45 Chapter 4: Monitor and deploy MIOapps of the pane to view the rest of it. If no one has entered a description for the container, this pane reads Description. For information about changing a MIOapp s description, see Add or change a MIOapp s description Add or change a MIOapp's description Because container names are fixed, a description helps you and other users find, identify, and describe MIOapps with more flexibility than the container name alone. MIOapp descriptions are also updated with timestamped notations when some container operations, such as clearing the container or using the container as the target for a deployed upgrade, compact, or resize operation. The description for the selected MIOapp is visible in MIOapp Manager s description pane. If you select multiple MIOapps, the most recently selected MIOapp s description is visible. To add or change a MIOapp s description: 1. Select the MIOapp you want to add or change the container description for. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Change description, prompting the container description window (fig. 4-3). 4. Enter your new description in the window MIOsoft Confidential - For licensed use only

46 MIOsoft MIOapp Manager User Guide Figure 4-3. Container description window 5. Click OK. After a brief pause, the container s new description appears in the description pane. If you click Cancel, your changes are erased and you return to MIOapp Manager Refresh and show changes There are three refresh-related options in MIOapp Manager: refresh, complete refresh, and show changes. These options allow you to manually update your MIOapp Manager window to see more recent information about your MIOapp(s). All options have global effects in MIOapp Manager Refresh Refresh is the standard refresh. It updates MIOapp Manager to show the most recent state of your environments and the MIOapps in your environments, but does not force the cache of host and environment information to clear. If one of your MIOapps has a yellow status indicator symbol, meaning waiting for information, you can use refresh to prompt MIOapp Manager to clear and update the status. To perform a refresh: 1. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 2. Click Refresh MIOsoft Confidential - For licensed use only 45

47 Chapter 4: Monitor and deploy MIOapps After a brief pause, MIOapp Manager updates to display the latest information Complete refresh As with the standard refresh, complete refresh updates environment and MIOapp status; however, it also clears the cache before the refresh takes place, ensuring that changes made on other hosts in your environment are always visible. To perform a cache clear refresh: 1. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 2. Click Complete refresh. MIOapp Manager pauses briefly while it clears the cache and then updates to show the latest information Show changes Show changes refreshes your information pane to show your MIOapps deltas: the changes in your MIOapps statistics since the last time you refreshed. To show changes: 1. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 2. Click Show changes. After a brief pause, MIOapp Manager updates to display the deltas for your MIOapps. If you use Show changes more than once without doing a refresh, MIOapp Manager treats your previous Show changes as the refresh and calculates your deltas from that point. Performing a refresh or showing changes permanently resets the point MIOapp Manager calculates the delta values from. You cannot get delta values which include anything that happened before the time of your most recent refresh or Show changes. While you can get aggregate data about your MIOapps deltas by looking at MIOapp Manager s information pane, the most effective way to use the delta information from showing changes is to look at your slice details MIOsoft Confidential - For licensed use only

48 MIOsoft MIOapp Manager User Guide View details While it is often useful to get information about your MIOapp as a whole, you can also view the same information about individual slices and web servers. When you use the slice details in conjunction with the Show changes function, you can more effectively assess and monitor your MIOapp s status. To view slice details: 1. Select the MIOapps you want to view slice or server details for. The MIOapp must be started. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Open the details window you want to look at: a. To view server details, click Show WebApp slice details, prompting the server details window. You can right-click in the window to access the webapp slice details menu (fig. 4-4). Figure 4-4. Server details window and details menu b. To view slice details, click Show slice details, prompting the slice details window. You can right-click in the window to access a menu (fig. 4-5) MIOsoft Confidential - For licensed use only 47

49 Chapter 4: Monitor and deploy MIOapps Figure 4-5. Slice details window and details menu Each slice or server in your selected MIOapp has its own row in the details window. To sort the details window: Click the column header you want to sort by. A sort arrow appears beside the column label. An up arrow ( ) indicates a least-to-greatest sort while a down arrow ( ) indicates a greatest-to-least sort. To reverse the sort order: Click the column header a second time. You can only sort by one column at a time. To refresh the details window: Press F5. You can also right-click in the window and select Refresh from the menu instead. To close the slice window: Click the x in the upper right-hand corner. MIOapp Manager closes the details window. You can re-open the details window at any time Slice details Each slice assigned to your selected MIOapp has its own row and status information in MIOsoft Confidential - For licensed use only

50 MIOsoft MIOapp Manager User Guide the slice details window: Slice is the slice number of the slice. State shows the current state of the MIOapp and uses red text if one or more slices have an exception. See table 4-B in MIOapp status: The information pane for more detailed information about possible MIOapp states. % shows the completed percentage of compacting and checkpoint activities. Executed shows a count of the jobs the slice has executed. Backlog shows a count of the jobs the slice has received but not yet executed. Outbound shows a count of jobs to be sent to other slices. Min Disk shows the free disk space remaining for the slice. The color of the Min Disk entry changes from black to yellow to red as disk space decreases. Running out of disk space stops a slice s operations. RAM shows the memory footprint of the slice. The color of the RAM entry changes from black to yellow to red as the amount of RAM consumed increases. A slice stops when it reaches approximately 1.8GB of RAM. Commit timestamps the last commit transaction with the slice; if this took place during the current calendar day, the timestamp is not dated. CPU shows the total CPU time per slice. This time is the actual CPU time, not the elapsed clock time. Refreshed shows when you last refreshed MIOapp Manager. If your most recent refresh-related action was a refresh, this column timestamps that refresh in yyyy-mm-dd hh:mm:ss format. If you used Show changes most recently, this column displays the time interval between your most recent Show changes and the previous refresh or Show changes, with the previous refresh s timestamp in parentheses. The State, %, Executed, Backlog, Min Disk, and Max Ram columns are slice-specific versions of the same columns in the information pane Server details Each server assigned to your selected MIOapp has its own row and status information in the server details window: 2013 MIOsoft Confidential - For licensed use only 49

51 Chapter 4: Monitor and deploy MIOapps Slice ID is the webapp s slice identifier. Status shows the status of the web server. Sessions shows the number of active session currently logged in to the web server. Logins shows the number of successful logins since the web server was started. Searches shows the total number of searches performed. Links shows the total number of links users have traversed from accessed web pages. Updates show the total number of updates committed to the database by web transactions. Failed pages shows the total number of failed page accesses. All columns are server-specific versions of the same columns in the information pane. You can use selected commands from the web resource section of the MIOapp menu on an individual slice by right-clicking on it, prompting a slice details menu. For more information about web resource menu options, see 3.6 Web servers Exceptions If one of your MIOapps experiences an exception, the MIOapp indicates this using red text in the relevant column of the information pane and the details window. In the slice or server details window, you can see which slice or server has the exception, and view the exception itself. To view exceptions: 1. Open the details window for the slice or server with the exception. 2. Click on the slice or server with the exception you want to view, highlighting it. 3. Right-click on the highlighted slice, prompting a pop-up details menu (fig. 4-6) MIOsoft Confidential - For licensed use only

52 MIOsoft MIOapp Manager User Guide Figure 4-6. View slice or server exceptions 4. Click View exceptions, prompting an Exceptions pop-up window (fig. 4-7). Figure 4-7. Slice or server exceptions window You can exit the exceptions window by clicking the x in the upper right-hand corner. You can also right-click in the window for a menu with optional actions, including the option to copy the message text. You must highlight the text before copying it Use show changes and slice details Monitoring the status of your MIOapps allows you to manage your organization s slices and assess your MIOapps function. When you are interested in the function of a specific MIOapp, you can get the most detailed information by viewing the slice details for the MIOapp after using Show changes. Using Show changes gives you the delta value information to assess how your MIOapp is functioning over time, while using slice details allows you to study not just the changes in numbers, but the distribution of work across your slices. Elapsed time To put your deltas into context, the first thing to look for when you use slice details with Show changes is the elapsed time. The elapsed time tells you the time period over which your deltas were calculated. This can be a matter of seconds, minutes, hours, or even days. The elapsed time can differ between slices; usually the degree of difference is only a few seconds. To find the elapsed time in the slice details window, look at the Refreshed column. MIOapp Manager lists the elapsed time first in this column, followed by the timestamp 2013 MIOsoft Confidential - For licensed use only 51

53 Chapter 4: Monitor and deploy MIOapps of the last refresh. You need both pieces of information to get the most out of your delta values. The elapsed time tells you the length of the time period the deltas cover, while the time of last refresh tells you when the deltas time period began. It is important to pay attention to the time of last refresh. It can seem intuitive to look at the elapsed time and subtract it from the current clock time, but MIOapp Manager s calculation of your deltas is unrelated to the current clock time: it includes only the time period between your most recent Show changes and the previous refresh or Show changes. The time elapsed since you last showed changes is not accounted for in your delta values. MIOapp Manager keeps the delta information it calculates after Show changes until you next refresh the window, use Show changes again, or close and reopen MIOapp Manager. That means you can open the slice details and look at your delta values well after the time period MIOapp Manager calculated your deltas over. When you look at your delta values, particularly if you are trying to determine the cause of a problem, be sure to check the time of last refresh and confirm that the time period your deltas were calculated over is the time period you are interested in. Jobs executed The Executed column counts how many jobs the slice executed during the elapsed time. For repeated runs of similar data, your MIOapp s slices should complete the runs in approximately the same number of jobs each time. You can monitor this by comparing the delta numbers from the Executed column for a number of data runs. Job backlog The Backlog column counts the change in the slice s backlog during the elapsed time. Outbound jobs The Outbound column counts the number of jobs the slice sent to another slice during the elapsed time. Comparing worker and injector slices Your MIOapp s worker and injector slices have different roles in your MIOapp, and that role difference is reflected in their delta values. While worker slices should have deltas similar to other workers and injector slices MIOsoft Confidential - For licensed use only

54 MIOsoft MIOapp Manager User Guide have deltas similar to other injectors, you should not be surprised to see significant differences between your worker slices and your injector slices as a group. This difference should be especially apparent in the Executed, Backlog, and Outbound columns. Generally, injector slices execute relatively few jobs; instead, they quickly send most jobs out to other slices. They tend to have relatively low execution counts and backlog counts and a high outbound count. Worker slices, on the other hand, execute jobs and return the results, which takes more time. Compared to injector slices, they have higher execution and backlog counts but relatively low outbound counts. Keep in mind when comparing backlog and execution counts that both processes are transient, peaking and falling during processing. If your delta covers a very short period, it might not give you an accurate picture of your MIOapp s slices relative outbound and backlog counts. Even if you do have a delta covering a long enough period to see this effect, high and low are still relative amounts. A high number for one MIOapp might be quite low on another. Commit transactions The Commit column timestamps that slice s most recent commit transaction to your MIOapp s database. Generally, your MIOapp s commit timestamps should not be more than a few minutes old for a running slice. If they are, it is usually due to processing huge contexts, massive matching, or because poor candidate sets (index) were chosen to support matching. You can also have older commit timestamps if the slice has been idle. Min Disk The Min Disk column reports the amount of disk space remaining for the slice. The text in the Min Disk column turns yellow and then red in warning as the slice approaches zero available disk space. RAM The RAM column reports the amount of RAM a slice is using. Once a slice reaches approximately 1.8GB of RAM, it stops. The text in the RAM column turns yellow and then red in warning as a slice approaches its maximum MIOsoft Confidential - For licensed use only 53

55 Chapter 4: Monitor and deploy MIOapps Gauge the distribution of your MIOapp's work You can use your slice detail deltas to show more than the performance of an individual slice or to look at differences between worker and injector slices. A major use for the slice details is to assess the distribution of your MIOapp s work. If you see in MIOapp Manager that your MIOapp has a large or slow-to-clear backlog, for instance, you can check the slice details window for more information about how you might resolve the issue. If all of your worker slices have large backlogs and high execution counts, then your MIOapp s work is evenly distributed. It is probably processing normally, but jobs are coming in faster than they can be executed. If this is the case, resolving the backlog might require you to move the MIOapp to a container with more slices to increase its processing power. But if your slice details indicate that all or most of the backlog is coming from just one slice, then the problem can be with the way your MIOapp s model distributes its work. Uneven work distribution: An example Say your organization has a million customers. Your MIOapp is designed so that every time a customer s information is uploaded, an injector sends that job to a slice for processing. A few of your customers are corporations, but almost all are individuals. So almost all of the time, a slice receives an individual customer s job, processes it without incident, and starts on the next job. But eventually your MIOapp loads a corporate customer s job: not just the information for the corporation, but the information for all of the corporation s customers as well, the equivalent of tens of thousands of individual customers. If your MIOapp does not take that into account, the injector still assigns the corporate job to one slice. The slice takes much longer to execute this corporate job than it would to execute an individual job, but the injector slice continues to assign the busy slice more jobs, which build up into a large backlog. In this case, the issue is not that you lack processing power for your MIOapp, but that your MIOapp is not distributing the work effectively. To resolve this issue, you need to change your MIOapp s modeling and rules to account for your different types of customers. Summary MIOsoft Confidential - For licensed use only

56 MIOsoft MIOapp Manager User Guide When you are trying to determine the cause of a backlog or slowdown in your MIOapp, knowing the distribution of the problem gives you an idea of how to approach solving it. You can see the distribution of your MIOapp s work by using Show changes and then viewing the MIOapp s slice details. A uniform backlog across all slices indicates that you might need more slices to process your data at the speed you require and should consider moving the MIOapp to a container with more slices. A slowdown confined to one or two slices indicates that the MIOapp s modeling cannot efficiently handle those slices current jobs and you should explore changes to the MIOapp s modeling and rules MIOapp status: The information pane You can find information about your MIOapps status in the information pane. The left half of the information pane (fig. 4-8) applies to all containers. Figure 4-8. Information pane (left half, all containers) Status shows the current status of the MIOapp, including started/stopped, locked/unlocked, and primary/standby. See table 4-A at the end of this section for a full list of possible status indicator symbol colors, shapes, and meanings. MIOapp shows the name of the container. MIOapp container names are in black, backup container names are in brown, workflow container names are in green, and security server names are in purple. MIOapp container names are bold while started; backup, workflow and security server container names are bold at all times. Slices shows the number of slices in use out of the total slices assigned to the MIOapp. The Slices entry uses red text if one or more slice hosts are inactive. State shows the current state of the MIOapp, and uses red text if one or more slices have an exception. See table 4-B at the end of this section for the possible states of a MIOapp. % shows the completed percentage of compacting and checkpoint activities. Executed shows a count of the jobs the MIOapp has executed on all slices. Repeated runs on similar data should take approximately the same number of jobs to complete; you can check this using the Executed column MIOsoft Confidential - For licensed use only 55

57 Chapter 4: Monitor and deploy MIOapps Backlog keeps a count of the MIOapp s received but un-executed jobs. Min Disk shows the amount of disk space remaining for whichever of the MIOapp s slices has the least left. Max RAM displays the amount of RAM in use by whichever of the MIOapp s slices is currently using the most. Table 4-A. Status indicator symbols Symbol color Meaning For more information, see green Started, no reported problems Start white Stopped Stop green and white Started, automatic scaling enabled for multiple slices Configure automatic scaling red Started, at least one reported Start in suspended mode problem red and blue Recovered, at least one Ghost MIOapps unresolved host conflict blue Recovered, original host slice Ghost MIOapps now available yellow Waiting for information Refresh and show changes Symbol shape Meaning For more information, see circle Primary MIOapp Chapter 3: Create and edit MIOapps astroid Standby MIOapp 5.4 Hot standby circle with web Web server 3.6 Web servers overlay padlock Locked Lock a container no padlock Unlocked Unlock a container universal no symbol Not enough slices available in quota to start Quotas and availability Table 4-B. MIOapp states State Meaning - Not running or not reporting back running (green text) Executing jobs running (red text) Executing jobs, but encountered an error installed Started, but has not performed any activities injecting Actively loading data idle Not currently executing any jobs creating checkpoint Currently creating a checkpoint for the MIOapp creating checkpoint (%: The last operation performed created a checkpoint done) MIOsoft Confidential - For licensed use only

58 MIOsoft MIOapp Manager User Guide compacting Currently compacting the MIOapp compacting (%: done) The last operation performed compacted the MIOapp reverting to checkpoint The system is reverting the MIOapp to a previous checkpoint reverted to checkpoint (%: done) The last operation performed reverted the MIOapp to a previous checkpoint paused Started in a suspended state, but has active jobs paused (idle) Started in a suspended state, but has no active jobs Web server status The right side of the information pane (fig. 4-9) is only relevant to MIOapps with a web server. Figure 4-9. Information pane (right half, web servers only) Sessions shows the number of active sessions currently logged in to the web server. Logins shows the number of successful logins since the web server was started. Searches shows the total number of searches performed. Links shows the total number of links users have traversed from accessed web pages. Updates shows the total number of updates committed to the database by web transactions. Failed pages shows the total number of failed web page accesses. 4.2 Export and import MIOapp configuration Your MIOapp s configuration is analogous to a laptop s docking station. It describes how your MIOapp should connect to anything outside itself, including both incoming and outgoing information MIOsoft Confidential - For licensed use only 57

59 Chapter 4: Monitor and deploy MIOapps The configuration of your MIOapp includes configurations for its: Load suites, determining where the MIOapp looks for input data and how it loads that data Portal strings, dictating settings for your MIOapp s web portals, if any Report suites, governing what reports your MIOapp can produce and how it produces them Data source partitioning settings, controlling how to load a large data source using multiple slices in parallel You can import and export configurations to apply the same interaction-based settings to MIOapps with different functionality. Import and export functions are controlled through the lower portion of the MIOapp section of the MIOapp menu (fig. 4-10), which is fourth from the top. Figure MIOapp section of the MIOapp menu MIOapp metadata Unlike the container and resources discussed previously, the metadata determines your MIOapp s actual function: it tells your MIOapp what to do. The metadata includes the configuration, but also includes the object modeling, rules, functions, schema, data source formats, etc. for the MIOapp. It does not include any of the MIOapp s existing data, which must be loaded separately. Even after your MIOapp is complete and you have loaded data, the metadata can be used to import and export your MIOapp, making copies or moving it from container to container. The metadata describes your desired data processing and uses the configuration to perform the correct external input/output actions. It does not need to know anything about what machine it is running on, how many slices its container has, or where the slices are. Instead, the MIOedge platform knows about the container and slice locations. MIOedge distributes the metadata s jobs across the MIOapp s assigned slices without knowing what the jobs are doing MIOsoft Confidential - For licensed use only

60 MIOsoft MIOapp Manager User Guide The MIOapp does not know anything about the container because MIOedge handles that, and MIOedge does not know anything about the metadata because the MIOapp s functionality is self-contained. This is useful to you because you can transfer a MIOapp s metadata between containers and have the new MIOapp run exactly like the original without changing the metadata or adjusting anything for the new slices. When MIOapp Manager refers to exporting or importing a MIOapp without any other modifiers, it means exporting or importing the metadata Export a MIOapp Exporting your MIOapp creates an external file with all of your MIOapp s metadata. This file can be uploaded to other containers and replicate your current MIOapp without affecting it. You can also use the export function to back up your MIOapp s metadata. Your export can include either the started, active version of your MIOapp schema or all versions of your MIOapp schema. Exporting the active version includes only the settings you are currently using for the MIOapp, while exporting all versions includes your MIOapp s version history and associated changes in the export file. To export a MIOapp: 1. Select the MIOapp you want to export. The MIOapp must be started. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Hover over Export, prompting the export submenu (fig. 4-11). Figure Export submenu 4. Select either Export MIOapp (active version only) or Export MIOapp (all versions) from the export submenu to export only the active version or all versions. The save process is the same for both. If you choose to export only the active version, but the active schema is not the newest, MIOapp Manager exports all schemas for safety reasons and displays a pop-up window informing you of this (fig. 4-12) MIOsoft Confidential - For licensed use only 59

61 Chapter 4: Monitor and deploy MIOapps Figure All schemas will be exported warning pop-up 5. A standard save dialog appears; you can change the file location and filename if you want to. MIOapp Manager defaults to a filename of ContainerName yyyy.mm.dd#, where # is an alphabet sequence beginning with a. MIOapp Manager increments the # based on whether a file with an identical ContainerName yyyy.mm.dd already exists in the file location the save dialog initially opens. 6. Click the Save button. You return to MIOapp Manager while it exports your MIOapp as a.mioapp file, to the location and with the filename you selected. You do not see any visible effects in MIOapp Manager from exporting a MIOapp Export a MIOapp configuration Exporting a configuration allows you to take the configuration of an existing MIOapp and create an external file of those settings, which you can then apply to a different container without affecting your existing MIOapp. To export your MIOapp s configuration: 1. Select the MIOapp you would like to export the configuration of. The MIOapp must be started. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Hover over Export, prompting the Export submenu. 4. Click Export MIOapp configuration. 5. A standard save dialog appears; you can change the file location and filename if you want to. MIOapp Manager defaults to a filename of ContainerName yyyy.mm.dd#, where # is an alphabet sequence beginning with a. MIOapp Manager increments the # based on whether a file with an identical ContainerName yyyy.mm.dd already exists in the file MIOsoft Confidential - For licensed use only

62 MIOsoft MIOapp Manager User Guide location the save dialog initially opens. 6. Click the Save button. You return to MIOapp Manager while it exports your MIOapp s configuration as a.mioconfig file to the location and with the filename you selected. You do not see any visible effects in MIOapp Manager from exporting a configuration Import a MIOapp After you export a MIOapp, you can import it into a different container, replacing the container s current metadata with the metadata from the.mioapp file. You should always import a.mioapp file into a new container or a newly-cleared container; importing into a container with existing data can result in unintended behavior. You can import a.mioapp file into more than one container, although you cannot import into more than one container simultaneously. Once you have exported the.mioapp file, it is detached from its parent MIOapp, and subsequent actions you take with it do not affect the parent MIOapp. You can use export and import to create a copy of a MIOapp for testing without affecting the MIOapp you are currently using. To import a MIOapp: 1. Select the container you want to import the metadata into. The container must be started and unlocked, and will have its current metadata (if any) permanently overwritten. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Import MIOapp. If your container has existing metadata, this prompts a warning pop-up (fig. 4-13). Figure Importing into a container with metadata warning pop-up 4. Click Yes to confirm you want to overwrite the container s current contents. Clicking No cancels the import process MIOsoft Confidential - For licensed use only 61

63 Chapter 4: Monitor and deploy MIOapps Clicking Yes prompts a standard navigation dialog. 5. Find and select the.mioapp file you want to import. 6. Click Open. MIOapp Manager might pause briefly; after the import takes place, you return to MIOapp Manager. There are no visual indicators that an import has just taken place except in the container s details pane, which updates to show the filename of the import Deploy an upgrade Deploying an upgrade allows you to merge a development MIOapp with functional upgrades and a production MIOapp with your desired configuration into an existing container in one step. The target container s upgraded MIOapp has the development MIOapp s changes in models, rules, and other functionality, and the production MIOapp s configuration but not structure of loading and reporting suites, portal strings, and data source partitioning. You select the upgrade MIOapp and the production MIOapp separately, so MIOapp Manager is able to import the upgrade MIOapp and then overwrite only its configuration. Neither your upgraded MIOapp source file nor the production MIOapp from which the configuration comes are affected by deploying the upgrade; only the target container is altered. Deploying an upgrade is a useful tool when you want to introduce a new version of an existing MIOapp into production. Your target container, into which you deploy the upgrade and configuration, has its metadata completely erased. Be sure that you do not need the target container s current contents before deploying an upgrade into it. To deploy an upgrade: 1. Stop the target MIOapp you are deploying the upgrade to. This target container will have its metadata erased and replaced and must be unlocked. 2. Start the production MIOapp you are deploying the upgrade from. This MIOapp will not be affected; its configuration will be copied and applied to the target container. This MIOapp must have an active schema version. 3. Select the MIOapp you are deploying the upgrade from. 4. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can MIOsoft Confidential - For licensed use only

64 MIOsoft MIOapp Manager User Guide also right-click in the information pane instead. 5. Click Deploy upgrade. The Deployer window appears (fig. 4-14). Figure Deployer window 6. In the Target application field of the Deployer window, select the target container. MIOapp Manager pre-screens target containers, so you see only stopped, available target containers in this list. 7. Click the Browse button. This launches a standard navigation dialog. Find the upgrade.mioapp file you want to apply the production configuration to. 8. Select the.mioapp file containing the upgrade and open it with the navigation dialog. 9. Click the OK button in the Deployer window. This deploys the metadata from your selected upgrade file into the target container 2013 MIOsoft Confidential - For licensed use only 63

65 Chapter 4: Monitor and deploy MIOapps and then applies the configuration of the production MIOapp Configuration deployment and possible discrepancies MIOapp Manager considers some settings of your MIOapp s configuration to be safe for automatic upgrade. In these cases, if there s a difference between your development and production MIOapps, MIOapp Manager uses the production MIOapp s setting. For other settings which could potentially affect your MIOapp s functionality, MIOapp Manager marks any differences as discrepancies and alerts you to them. Addition and deletion When MIOapp Manager is replacing your development configuration with a production configuration, it exhibits specific behavior if the new, production configuration requires addition to or deletion from the development configuration s data sources, report suites, and similar components. These changes are potentially undesirable for your MIOapp, so MIOapp Manager uses two principles when handling them: that it is important for you to verify these changes, and that it is easier for you to delete extra components than it is to add missing ones. To minimize your workload, when MIOapp Manager imports the production configuration, it adds any additional components and identifies but does not delete any extraneous components in the upgraded MIOapp. When MIOapp Manager creates the discrepancy report, it alerts you to all the additions and all the would-be deletions. You can then delete any additions that should not have been added and make any deletions that should have taken place. Once you make these deletions, the deleted components are removed from your upgraded MIOapp. If you use your just-created MIOapp as the production configuration for future upgrade deployments, it does not include the deleted components, so you do not need to address them again. MIOapp Manager alerts you to the presence of any non-development components you kept during future upgrades as well, but keeping a production-only component in place does not require any action from you to preserve it. With discrepancy reports, you only ever have to delete extra components, never have to re-add incorrectly deleted components, and all potentially undesirable changes are verified by you, safeguarding your MIOapp. Portal strings MIOsoft Confidential - For licensed use only

66 MIOsoft MIOapp Manager User Guide MIOapp Manager takes some portal string settings from the development configuration and some from production. Portal strings taken from production are: LoginRequired DisplayWebDebugStack Log-HeaderFields LogFailures LogLogins LogLoginFailedAttempts LogReads LogSecurityErrors LogSearches LogWrites TitleLogo UserWidgetLibraryPath WebServerPublicDirectory MIOapp Manager considers all portal strings not listed above to be updated by development. Types of discrepancies MIOapp Manager currently checks for 42 discrepancies. Some types of discrepancies, like renaming, recur for several components, while others are unique to a component. Table 4-C below lists potential discrepancy messages you can encounter, sorted by component. For some discrepancy messages an additional description is provided in the table. Table 4-C. Discrepancy messages Discrepancy message Description Format pages Removed format pages from a data source - New format pages (unconfigured) Removed format pages - Renamed format page - Load suites Removed root contexts (and associated data sources) Renamed data source - Unconfigured data sources A new format page which has not been configured by the production MIOapp has been added by the development MIOapp. - A new data source which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp MIOsoft Confidential - For licensed use only 65

67 Chapter 4: Monitor and deploy MIOapps Data sources added by config file The production configuration added a data source which did not exist in the development MIOapp. Unconfigured load suites A new load suite which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp. Removed load suites - Data sources in config file but no longer - present in system Data source file set discrepancies - Data sources added (checked) by config file Data sources removed (unchecked) by config file Reply report no longer exists - Renamed load suite Report suites Missing reports - Renamed report suite The production configuration checked data sources which were unchecked in the development MIOapp. The production configuration unchecked data sources which were checked in the development MIOapp. A load suite which existed in the production configuration has been renamed in the development MIOapp. The report suite was renamed. This appears as a sub-entry under Inconsistent report suites. Reports removed (unchecked) in config file The production configuration unchecked reports which were checked in the development MIOapp. Reports added (checked) by config file Removed report suites - Unconfigured report suites Inconsistent report suites Reports Invalid extract path The production configuration checked reports which were unchecked in the development MIOapp. A report suite which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp. Reports within the suite have been checked or unchecked, and/or the report suite was renamed. If the report suite was renamed, the renaming discrepancy appears as a sub-entry under the Inconsistent entry. The file path for the extract is invalid MIOsoft Confidential - For licensed use only

68 MIOsoft MIOapp Manager User Guide Bad path for destination queue manager The attribute path through the model is bad. Bad path for destination queue The attribute path through the model is bad. Switches Added switches - Unconfigured switches A new switch which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp. Attempt to add obsolete switches (no - longer in default) Changed switches - Switch key changed - Switch configuration added - Web portals Portal settings not updated - Unconfigured portal settings (new) A setting is now available in MIOedge for use in portals; this setting did not exist in MIOedge previously and must be configured for existing portals. Obsolete portal settings A setting which was in use by a portal is no longer available in MIOedge. Modified default portal settings - Missing portals (renamed or removed) - Unconfigured portals (new) A new portal which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp. Web service servers Missing web services (renamed or - removed) Unconfigured web services (new) Unconfigured web service settings (new) Obsolete web service settings A new web service which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp. A setting is now available in MIOedge for use in web services; this setting did not exist previously in MIOedge and must be configured for existing web services. A setting which was in use by a web service is no longer available in MIOedge MIOsoft Confidential - For licensed use only 67

69 Chapter 4: Monitor and deploy MIOapps Discrepancy reports Discrepancy reports identify differences between your production configuration and your development MIOapp s configuration that are not automatically upgraded. MIOapp Manager made any additions and marked any components slated for deletion. You can use the discrepancy report to examine these changes and determine which ones you want to keep. MIOapp Manager checks for discrepancies every time you deploy an upgrade. If you have no discrepancies, it notifies you with a pop-up message (fig. 4-15). Figure No discrepancies notification If you do have a discrepancy, it displays a report of all discrepancies and their locations (fig. 4-16). The report is auto-expanded to show all discrepancies; you can use the arrows beside an entry to collapse or expand it. Each discrepancy is in bold MIOsoft Confidential - For licensed use only

70 MIOsoft MIOapp Manager User Guide Figure Discrepancy report The report allows you to go immediately to the site of any discrepancy. To go to a discrepancy: 1. Find the name of the discrepancy you want to go to. 2. Double-click the discrepancy (fig. 4-17) MIOsoft Confidential - For licensed use only 69

71 Chapter 4: Monitor and deploy MIOapps Figure Go to the location of a discrepancy MIOapp Console opens at the discrepancy s location. Once in MIOapp Console, you can check the discrepancy and correct it if necessary. For more information about working in MIOapp Console, see the MIOsoft MIOdeveloper and MIOapp Console User Guide. Once you close the discrepancy report, you cannot re-open it. To close the discrepancy report: Click OK. The discrepancy report closes, but MIOapp Console remains open MIOsoft Confidential - For licensed use only

72 MIOsoft MIOapp Manager User Guide Chapter 5: Maintenance and recovery MIOapp Manager has several features enabling you to maintain, back up, and recover of your MIOapp. To create a new version of your MIOapp with only the most current data, you can use the compacting and resize functions. To see your MIOapp before and after a set of changes, you can use the checkpoint function. Creating a checkpoint for a state allows you to return your MIOapp to that exact state later, even if you make changes to and save the MIOapp. The compacting and checkpoint functions are performed through the maintenance and recovery section of the MIOapp menu (fig. 5-1), which is third from the bottom. Figure 5-1. Maintenance and recovery section of the MIOapp menu To recover your MIOapp, you can use resource replication. Resource replication duplicates your MIOapp s slices as they are written, so you have a complete copy of your MIOapp and all its data. To ensure continuity of function in your MIOapp, you can use a hot standby. Hot standby MIOapps are independent of but identical to your primary MIOapp, and can pick up immediately if your primary MIOapp fails. To make a snapshot backup preserving your MIOapp and/or its loaded data before a version change or other major upgrade, you can use MIOapp Manager s compact feature or your MIOapp s report suite. These features let you preserve the current state of your MIOapp and its data before your new functionality or data is loaded. 5.1 Compact or resize Since MIOedge preserves old data instead of overwriting it, your MIOapp database files can accumulate significant amounts of historical data. This is especially true for dynamic databases, where large volumes of data are updated very frequently, creating multiple old versions of modified data. You can create a copy of your MIOapp but with a reduced database size using the MIOapp compacting feature. Compacting copies your MIOapp and the most recent copy of everything in its database to a new container. This new MIOapp has smaller 2013 MIOsoft Confidential - For licensed use only 71

73 Chapter 5: Maintenance and recovery database files than your old MIOapp files because it contains only the most recent copy of all your data. You can also compact a MIOapp if you want to create a copy of your MIOapp with its current data loaded, either for testing or for backup purposes. When you compact a MIOapp, the target container must have the same number of slices, with the same relative shares, on the same hosts as the original MIOapp s container. Resizing a MIOapp essentially the same process as compacting it, but allows you more latitude in selecting the container for the new MIOapp. When you resize a MIOapp, the target container can have any number of slices with any share distribution and be on any host MIOapp Manager can access. If the MIOapp you are resizing has data sources with a host specified or a partitioned data source, the slice assignments are automatically reassigned. You cannot load data into the resized MIOapp using a Partial changes load relative to data you loaded before the resize. As with deploying an upgrade, the container you compact or resize your MIOapp into is called the target. All of the target s metadata and data, if any, will be overwritten during the compact or resize process. Checkpoints are not retained when you compact or resize a MIOapp. If you need to preserve a checkpoint from an original MIOapp, you must revert the MIOapp to that checkpoint and then compact or resize it into an empty container. During both compacting and resizing, MIOapp Manager presents you with a list of containers that are permitted targets for the process. However, MIOapp Manager does not indicate whether the containers have any existing metadata or data. You are responsible for ensuring that the target you select can safely have its existing contents, if any, overwritten Create a compact target container If you do not have an appropriate target container for the compacting process, you must create one before you can compact the MIOapp. The most straightforward way to do this is to duplicate the existing MIOapp s container. For information about duplicating a container, see Duplicate an existing container Compact a MIOapp To compact one MIOapp into another: 1. Select your source MIOapp that you want to compact. The MIOapp must be stopped and unlocked. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead MIOsoft Confidential - For licensed use only

74 MIOsoft MIOapp Manager User Guide 3. Click Compact into. This prompts the compact target selection window (fig. 5-2), with a list of all valid compact targets. Figure 5-2. Compact target selection window MIOapp Manager displays a warning pop-up if all your possible targets are started (fig. 5-3) or if no possible targets exist (fig. 5-4). Stop a target container, or see Create a compact target container for information about creating a target container, then return to step 1. Figure 5-3. All compatible compact targets are started pop-up Figure 5-4. No compatible and permissible targets pop-up 4. Select the target MIOapp container. 5. Click OK MIOsoft Confidential - For licensed use only 73

75 Chapter 5: Maintenance and recovery MIOapp Manager reappears, and pauses briefly while it compacts your source MIOapp into your target container. If you click Cancel on the target selection pop-up, you return to MIOapp Manager and do not compact your selected MIOapp. When the compacting process is complete, your target container contains the compacted version of your source MIOapp Resize a MIOapp Before you resize a MIOapp, it must have completed any active MQ loading, the injection phase of loading from a file or files, and all changes to the metadata, such as saving a schema. MIOapp Manager does not perform the resize if you attempt to resize a MIOapp that was stopped while one of these high-priority system actions was in progress. To resize one MIOapp into another: 1. Select your source MIOapp that you want to resize. The MIOapp must be stopped and unlocked. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Resize into. This prompts the resize target selection window (fig. 5-5), with a list of all valid resize targets. Figure 5-5. Resize target selection window MIOapp Manager displays a warning pop-up if all your possible targets are started (fig. 5-6). Stop a target container, then return to step MIOsoft Confidential - For licensed use only

76 MIOsoft MIOapp Manager User Guide Figure 5-6. All compatible targets are started pop-up 4. Select the target MIOapp container. 5. Click OK. MIOapp Manager reappears, and pauses briefly while it resizes your source MIOapp into your target container. If MIOapp Manager does not perform the resize because the MIOapp was stopped during a metadata change, active MQ loading, or the injection phase of loading from a file or files, restart the MIOapp and wait for the action to complete before performing the resize again. If you click Cancel on the target selection pop-up, you return to MIOapp Manager and do not resize your selected MIOapp. When the compacting process is complete, your target container contains the resized version of your source MIOapp. Any data source mappings are reassigned using the formula X = ((N-1) mod M) + 1, where X is the mapping s target slice assignment, N is the mapping s source slice assignment, and M is the number of slices in the target MIOapp. If the target has fewer slices than the source, this distributes the assignments across the available slices as evenly as possible; if the target has more slices than the source, this retains all the original slice assignments. If necessary, you can change the slice assignment of any data source that has not yet been loaded individually after the resize. All job execution statistics from the original MIOapp appear in slice #1 of the new MIOapp. 5.2 Checkpoints The checkpoint function takes a snapshot of your complete MIOapp, including all of its configuration settings and database slices. To return the MIOapp to the exact state of the snapshot, you can revert it to the checkpoint. Creating a checkpoint is especially useful if you are about to make significant changes to a MIOapp. If your changes do not yield acceptable results or you encounter irresolvable problems, you can easily reverse all of your changes by reverting to the checkpoint MIOsoft Confidential - For licensed use only 75

77 Chapter 5: Maintenance and recovery If you create multiple checkpoints, you can move between them to freely reverse and reinstate changes. You can create more than two checkpoints and move between any of them at any time: this allows you to compare multiple sets of changes, see previous versions of your MIOapp, or keep a record of your work as you develop your MIOapp. Do not use checkpoints as a substitute for backing up files. Checkpoints preserve your MIOapp s previous versions, but they require that your MIOapp s metadata, database, and container be intact. If any of these are damaged through an event such as an environmental disaster, a checkpoint cannot repair them Create a checkpoint To create a checkpoint: 1. Select the MIOapp for which you want to create a checkpoint. The MIOapp must be stopped. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Create checkpoint. 4. This prompts the checkpoint name dialog (fig. 5-7). By default, MIOapp Manager uses a checkpoint name of your current time and date in yyyy-mm-dd-hh.mm.ss format. Figure 5-7. Checkpoint name dialog 5. If you want to rename the checkpoint, enter your changes in the data entry field. If you use a checkpoint name which has already been used for the MIOapp, MIOapp Manager automatically overwrites the previous checkpoint. 6. Click OK. After you click OK, you return to MIOapp Manager. After a brief pause, it updates; the state of your selected MIOapp changes to creating checkpoint, with % indicating the percent completed MIOsoft Confidential - For licensed use only

78 MIOsoft MIOapp Manager User Guide When your checkpoint is finished, the % changes to done. 7. Stop the MIOapp. Your MIOapp is now ready to be restarted for normal use Revert to a checkpoint Reverting to a checkpoint returns a MIOapp to the state it was in when you created the checkpoint. If you might want to return to your MIOapp s current state the state you are reverting from you must create a checkpoint for your current state before reverting. To revert to a checkpoint: 1. Select the MIOapp you want to revert. The MIOapp must be stopped and unlocked. 2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead. 3. Click Revert to checkpoint. This prompts the checkpoint selection dialog (fig. 5-8) Figure 5-8. Checkpoint selection dialog 4. Select the checkpoint you want to revert to from the list. 5. Click OK to revert to the selected checkpoint. After you click OK, you return to MIOapp Manager. After a brief pause, during which your MIOapp s state reads reverting to checkpoint, your MIOapp s % changes to done. If you click Cancel, you return to MIOapp Manager and do not revert the MIOapp to 2013 MIOsoft Confidential - For licensed use only 77