Personal Library

Reference - Ansible4IOM Processes 1.0

https://support.intershop.com/kb/28380A

Product Version	2.2
Product To Version	2.2
Status	final

1 Introduction

This document lists all predefined operational processes and their scope that can be used within Ansible4IOM to manage tasks like setup, reconfiguration or cleanup of system components of an IOM-Installtion. For every process, a description, included tasks as well as background information and examples are provided.

The target group of this document are developers of a project as well as system administrators.

1.1 Glossary

Term	Description
Ansible4IOM	Ansible4IOM is a tool of IOM for server configuration management. Additionally operation tasks are predifined and can be customized.
Azure	A cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through a global network of Microsoft-managed data centers.
CI	Continous integration
Configuration Repository	In the scope of Ansible4IOM a configuration repository is a set of configurations that describes the used machines, values of variables hooks and more. It's a descripton of how to install a custom IOM.
DB	Database
EPEL	Extra Packages for Enterprise Linux is a repository of the Fedora-Project (https://fedoraproject.org/wiki/EPEL).
FS	File system
Gluster-FS	A scale-out network-attached storage file system
Hook	Hooks are part of Ansible4IOM. Hooks are a sophisticated way to customize processes. Additionally the behavior of processes can be simply customized by various variables.
IOM	The abbreviation for Intershop Order Management
IOM Watchdog	A tool of IOM to monitor and manage the availablity of IOM application servers
JMS	Java Message Service
OMS	The abbreviation for Order Management System, the technical name of the IOM
PG	PostgreSQL
RHEL	Red Hat Enterprise Linux
SQL	Structured Query Language

1.2 References

and

2 Ansible4IOM Processes

Title	Description	Valid From
Process - Cleanup Database Account 1.0	The process cleanup_omsdb removes an existing Database account. The process is intended to be used by CI processes or on preproduction systems, in order to reset a database back into initial state.	2.2
Process - Cleanup Load Balancer 1.0	The process cleanup_load_balancer removes an installed load balancer. The process is used by CI processes, in order to reset a machine back into initial state.	2.2
Process - Cleanup OMS Node 1.0	The process cleanup_oms_node removes an IOM installation.	2.2
Process - Cleanup Postgres Server 1.0	The process cleanup_pgserver removes a simple PostgreSQL-server (installed before using Process - Setup Postgres Server 1.0) and according data. The process is intended to be used by CI processes, in order to reset a machine back into initial state.	2.2
Process - Reconfigure Load Balancer 1.0	The process reconfigure_load_balancer applies configuration changes to an installed load balancer, based on an Apache httpd-server. For installation see Process - Setup Load Balancer 1.0.	2.2
Process - Reconfigure OMS Node 1.0	The process reconfigure_oms_node is the right choice to update the project code and configuration. The process executes all hooks, which should be used by projects and it redeploys all artifacts. If you are using the process reconfigure_oms_node to update project code and configuration, you should execute the process on all servers in parallel (forcing a downtime) to avoid inconsistency between project code and project specific data-structures in database.	2.2
Process - Reconfigure Postgres Server 1.0	The process reconfigure_pgserver updates selected PostgreSQL settings of a database installed before using Process - Setup Postgres Server 1.0. Since reconfiguration of the database server requires restart of the database server, the process is forcing a downtime of the whole IOM system.	2.2
Process - Setup Load Balancer 1.0	The process setup_load_balancer installs a new load balancer for a distributed IOM installation. It works on servers assigned to group load_balancer. Also see Concept - Ansible4IOM. The load balancer, installed this way, is an Apache HTTP-server, configured to work as load balancer for IOM.	2.2
Process - Setup OMS Node 1.0	The process setup_oms_node installs a new IOM node. It works for all server-groups, which might be used for oms-nodes: oms_single_node, oms_ha_node and oms_azure_node.	2.2
Process - Setup or Reconfigure Database Account 1.0	The process setup_omsdb sets up or reconfigures a DB account suitable for use by IOM on an existing PostgreSQL-server.	2.2
Process - Setup Postgres Server 1.0	The process setup_pgserver installs a simple PostgreSQL-server, without any high-availabilty features. It can be used by IOM application-servers.	2.2
Process - Update OMS Node 1.0	The process update_oms_node updates an IOM node to a newer IOM version. IOM updates mostly require database migrations, therefore the update process forces a downtime of the whole system. For the same reason, you should execute updates for the whole cluster only. The process update_oms_node is working for all server groups, which might be used for oms-nodes: oms_single_node, oms_ha_node and oms_azure_node.	2.2

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.