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

© 2013 MIOsoft | Confidential - For licensed use only 65

MIOapp Manager takes some portal string settings from the development configuration and some from production. Portal strings taken from production are:

● LoginRequired

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) A new format page which has not been configured by the production MIOapp has been added by the development MIOapp.

Removed format pages -

Renamed format page -

Load suites

Removed root contexts (and associated

data sources) -

Renamed data source -

Unconfigured data sources A new data source which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp.

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 The production configuration checked data

sources which were unchecked in the development MIOapp.

Data sources removed (unchecked) by

config file The production configuration unchecked

data sources which were checked in the development MIOapp.

Reply report no longer exists -

Renamed load suite A load suite which existed in the production configuration has been renamed in the development MIOapp.

Report suites

Missing reports -

Renamed report suite 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 The production configuration checked reports which were unchecked in the development MIOapp.

Removed report suites -

Unconfigured report suites A report suite which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp.

Inconsistent report suites 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.

Reports

Invalid extract path The file path for the extract is invalid.

© 2013 MIOsoft | Confidential - For licensed use only 67

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) A new web service which has not been configured by the production MIOapp's configuration file has been added by the development MIOapp.

Unconfigured web service settings (new) 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.

Obsolete web service settings A setting which was in use by a web service is no longer available in MIOedge.