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

87 

Full text

(1)

M I O a p p

®

M a n a g e r

(2)

MIOsoft Corporation

U.S. Corporate Headquarters 33 East Main Street

Madison, WI 53703 www.miosoft.com

Copyright © 2011-2013 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

MIOsoft® MIOapp® Manager User Guide ... 1

Table of Contents ... 2

Chapter 1: Introduction ... 6

1.1 MIOapp Manager ... 6

1.2 Map of MIOapp Manager ... 6

1.3 Log in and out ... 6

1.3.1 Log in ... 6

1.3.2 Log out ... 8

1.4 Change your password ... 8

1.5 Definitions and important concepts ... 9

1.5.1 MIOapp ... 9

1.5.2 Resources and slices ... 10

1.5.3 Resource sets ... 11

1.5.3.1 Identical web resources ... 11

1.5.4 Environments ... 12

1.6 Manipulate MIOapp Manager ... 12

1.6.1 Resize ... 12

1.6.2 Keyboard shortcuts ... 12

Chapter 2: Containers ... 14

2.1 Definition of a container ... 14

2.1.1 Containers and container contents ... 14

2.1.2 Available containers ... 14

2.2 Processing ... 15

2.2.1 Slices ... 15

2.2.2 Quotas and availability ... 15

2.2.2.1 The environment pane ... 16

2.2.3 Slice allocation ... 17

2.2.4 Injectors ... 18

2.3 Container types ... 18

Chapter 3: Create and edit MIOapps ... 20

3.1 Find MIOapps ... 20

(4)

© 2013 MIOsoft | Confidential - For licensed use only 3

3.1.2 Select MIOapps ... 20

3.1.2.1 Select multiple MIOapps ... 20

3.1.2.2 View MIOapps by environment ... 21

3.2 Create a container ... 21

3.2.1 Select the new container's resource set ... 22

3.2.2 Duplicate an existing container ... 24

3.3 Delete ... 25

3.3.1 Delete a container ... 26

3.3.2 Clear a container ... 27

3.4 Lock and allocate containers ... 27

3.4.1 Allocate slices ... 28

3.4.2 Deallocate slices ... 29

3.4.3 Lock a container ... 29

3.4.4 Unlock a container ... 30

3.5 Start, stop, and open MIOapps ... 31

3.5.1 Start ... 32

3.5.2 Start in suspended mode ... 32

3.5.3 Stop ... 33

3.5.4 Automatic restart ... 34

3.5.5 Open the console ... 34

3.6 Web servers ... 35

3.6.1 Start a web server ... 36

3.6.2 Stop or shut down a web server ... 36

3.6.3 Open a portal in a web browser ... 37

3.6.4 View web URLs ... 38

3.6.5 Add, remove, or change a web resource ... 38

3.6.6 Configure automatic scaling ... 40

Chapter 4: Monitor and deploy MIOapps ... 43

4.1 Monitor ... 43

4.1.1 Identification information ... 43

4.1.1.1 The details pane ... 43

4.1.1.2 The description pane ... 43

4.1.1.3 Add or change a MIOapp's description ... 44

4.1.2 Refresh and show changes ... 45

4.1.2.1 Refresh ... 45

(5)

4.1.2.3 Show changes ... 46

4.1.3 View details ... 47

4.1.3.1 Slice details ... 48

4.1.3.2 Server details ... 49

4.1.3.3 Exceptions ... 50

4.1.4 Use show changes and slice details ... 51

4.1.4.1 Gauge the distribution of your MIOapp's work ... 54

4.1.5 MIOapp status: The information pane ... 55

4.1.5.1 Web server status ... 57

4.2 Export and import ... 57

4.2.1 MIOapp configuration... 57

4.2.2 MIOapp metadata ... 58

4.2.3 Export a MIOapp ... 59

4.2.4 Export a MIOapp configuration ... 60

4.2.5 Import a MIOapp ... 61

4.2.6 Deploy an upgrade ... 62

4.2.6.1 Configuration deployment and possible discrepancies ... 64

4.2.6.2 Discrepancy reports ... 68

Chapter 5: Maintenance and recovery ... 71

5.1 Compact or resize ... 71

5.1.1 Create a compact target container ... 72

5.1.2 Compact a MIOapp ... 72 5.1.3 Resize a MIOapp ... 74 5.2 Checkpoints ... 75 5.2.1 Create a checkpoint ... 76 5.2.2 Revert to a checkpoint ... 77 5.3 Resource replication ... 78 5.3.1 Ghost MIOapps ... 78 5.4 Hot standby ... 79 5.4.1 Web servers ... 80

5.4.2 Continuous loading: Capture files ... 80

5.4.3 Batch loading ... 81

5.5 Snapshot backups ... 81

5.5.1 Back up a MIOapp and its data ... 81

5.5.2 Back up data for reloading ... 81

(6)

© 2013 MIOsoft | Confidential - For licensed use only 5 Figures and tables ... 85

(7)

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

1.3.1 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

(8)

© 2013 MIOsoft | Confidential - For licensed use only 7 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.

(9)

1.3.2 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).

(10)

© 2013 MIOsoft | Confidential - For licensed use only 9

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

1.5.1 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.

(11)

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.

1.5.2 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.

(12)

© 2013 MIOsoft | Confidential - For licensed use only 11 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.

1.5.3 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.

1.5.3.1 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

(13)

any MIOapps previously created with the same resource set need their web servers.

1.5.4 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 2.2.2 Quotas and availability)visible in MIOapp Manager’s environment pane.

1.6 Manipulate MIOapp Manager

1.6.1 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

1.6.2 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

combination Action For more information, see

F5 Refresh 4.1.2.1 Refresh

Shift + F5 Complete refresh 4.1.2.2 Complete refresh

F6 Show changes 4.1.2.3 Show changes

Ctrl + S Start 3.5.1 Start

Ctrl + Shift + S Stop 3.5.3 Stop

(14)

© 2013 MIOsoft | Confidential - For licensed use only 13

Ctrl + Shift + W Stop a web server 3.6.2 Stop a web server Ctrl + C Create a MIOapp

container 3.2 Create a container

Ctrl + Shift + C Delete the container 3.3.1 Delete a container Ctrl + L Lock the container 3.4.3 Lock a container Ctrl + Shift + L Unlock the container 3.4.4 Unlock a container Ctrl + A Allocate the

container’s slices 3.4.1 Allocate slices Ctrl + Shift + A Deallocate the

container’s slices 3.4.2 Deallocate slices

Ctrl + D Change description 4.1.1.3 Add or change a MIOapp’s description Ctrl + O Open the console 3.5.5 Open the console

Ctrl + I Import a MIOapp 4.2.5 Import a MIOapp Ctrl + U Deploy an upgrade 4.2.6 Deploy an upgrade

(15)

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.

2.1.1 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.

2.1.2 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

(16)

© 2013 MIOsoft | Confidential - For licensed use only 15 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 3.5.1 Start

white Stopped 3.5.3 Stop

green and white Started, automatic scaling

enabled for multiple slices 3.6.6 Configure automatic scaling

red Started, at least one reported

problem 3.5.2 Start in suspended mode

red and blue Recovered, at least one

unresolved host conflict 5.3.1 Ghost MIOapps

blue Recovered, original host slice

now available 5.3.1 Ghost MIOapps

yellow Waiting for information 4.1.2 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

overlay Web server 3.6 Web servers

padlock Locked 3.4.3 Lock a container

no padlock Unlocked 3.4.4 Unlock a container

universal no

symbol Not enough slices available in quota to start 2.2.2 Quotas and availability

2.2 Processing

2.2.1 Slices

As discussed in 1.5.2Resources and slices and 1.5.3 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 4.1.3 View details.

2.2.2 Quotas and availability

(17)

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 2.2.4 Injectors for information about injectors. You can get information about your quota situation from the environment pane. 2.2.2.1 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).

(18)

© 2013 MIOsoft | Confidential - For licensed use only 17

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.

2.2.3 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.

(19)

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 email 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 3.4.1 Allocate slices. For information about using a workflow server, see the MIOsoft Workflow Console™ User Guide.

2.2.4 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 2.1.1 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

(20)

© 2013 MIOsoft | Confidential - For licensed use only 19 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.

(21)

Chapter 3: Create and edit MIOapps

3.1 Find MIOapps

3.1.1 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 4.1.4 Viewing slice details for more information.

3.1.2 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.

3.1.2.1 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.

(22)

© 2013 MIOsoft | Confidential - For licensed use only 21 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.

3.1.2.2 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.

(23)

Figure 3-1. MIOapp section of the MIOapp menu

3.2.1 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).

(24)

© 2013 MIOsoft | Confidential - For licensed use only 23

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.

(25)

Figure 3-4. New container in information pane

3.2.2 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 1.5.3.1 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

(26)

© 2013 MIOsoft | Confidential - For licensed use only 25

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

(27)

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

3.3.1 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.

(28)

© 2013 MIOsoft | Confidential - For licensed use only 27

3.3.2 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.

(29)

Figure 3-10. Lock and allocation section of the MIOapp menu

3.4.1 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.

(30)

© 2013 MIOsoft | Confidential - For licensed use only 29

Figure 3-11. Cannot allocate container pop-up

3.4.2 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.

3.4.3 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.

(31)

● 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.

3.4.4 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.

(32)

© 2013 MIOsoft | Confidential - For licensed use only 31 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 3-12. 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 4.1.5 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.

(33)

Figure 3-13. Start/stop section of the MIOapp menu

3.5.1 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.

3.5.2 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.

(34)

© 2013 MIOsoft | Confidential - For licensed use only 33 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 3.5.1 Start and 3.5.3 Stop for steps 2 and 3, respectively.

3.5.3 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.

(35)

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.

3.5.4 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.

3.5.5 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:

(36)

© 2013 MIOsoft | Confidential - For licensed use only 35 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 3-14. 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.

(37)

Figure 3-15. Web resource section of the MIOapp menu

3.6.1 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.

3.6.2 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.

(38)

© 2013 MIOsoft | Confidential - For licensed use only 37 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.

3.6.3 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 3-16. Web browser selection submenu

4. Hover over your choice of web browser, prompting the web portal selection submenu (fig. 3-17).

(39)

Figure 3-17. Web portal selection submenu

5. Click the web portal you want to open.

The portal opens automatically, using the web browser you chose.

3.6.4 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 3-18. URLs pop-up window

3.6.5 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:

(40)

© 2013 MIOsoft | Confidential - For licensed use only 39 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 3-19. 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.

(41)

3.6.6 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).

(42)

© 2013 MIOsoft | Confidential - For licensed use only 41

Figure 3-20. 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

(43)

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.

Minimum number of

active slices Specifies the minimum number of active slices for the web server. Enter an integer of one (1) or greater. Sample period 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.

Burst traffic control: Start a slice at __ avg. sessions

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.

Burst traffic control: Stop a slice at __ avg. sessions

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.

Sustained traffic

control: Interval size 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.

Sustained traffic control: Start a slice at __ avg. sessions

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.

Sustained traffic control: Stop a slice at __ avg. sessions

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.

Slice options: Refuse new connections at __ sessions

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.

Slice options: Refuse new logins at __ sessions

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.

(44)

© 2013 MIOsoft | Confidential - For licensed use only 43

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

4.1.1 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

4.1.1.1 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.

4.1.1.2 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

(45)

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 4.1.1.3 Add or change a MIOapp’s description.

4.1.1.3 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).

(46)

© 2013 MIOsoft | Confidential - For licensed use only 45

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.

4.1.2 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. 4.1.2.1 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.

(47)

After a brief pause, MIOapp Manager updates to display the latest information. 4.1.2.2 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.

4.1.2.3 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.

(48)

© 2013 MIOsoft | Confidential - For licensed use only 47

4.1.3 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).

(49)

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.

4.1.3.1 Slice details

(50)

© 2013 MIOsoft | Confidential - For licensed use only 49 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 4.1.5 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.

4.1.3.2 Server details

Each server assigned to your selected MIOapp has its own row and status information in the server details window:

Figure

Updating...

References

Updating...

Related subjects :