Name: ansible-role-infosvr
Owner: International Business Machines
Description: Ansible role for automating the deployment of IBM InfoSphere Information Server
Created: 2018-05-11 11:43:52.0
Updated: 2018-05-20 15:49:09.0
Pushed: 2018-05-21 14:25:53.0
Size: 136
Language: null
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Ansible role for automating the deployment of an IBM InfoSphere Information Server environment, including:
and the following modules of Enterprise Edition, which can be disabled through the variables described below (eg. if not entitled to use them or you do not want to install / configure them):
Currently the deployment only caters for DB2 as the back-end, though works for both installing and configuring the bundled DB2 as well as configuring a pre-existing DB2. Either a full WebSphere Application Server Network Deployment configuration or a WebSphere Liberty Profile configuration will be installed (see variables below for more details); currently the role is not able to configure a pre-existing WebSphere installation.
See defaults/main.yml for inline documentation, and the example below for the main variables needed. The defaults file contains the default settings you would find for a vanilla v11.7 installation already, so you only need to override those variables for which you do not wish to use the default (ie. passwords for users).
The minimal variables that likely need to be overridden are as follows:
ibm_infosvr_media_dir: the location on your Ansible host where the installation binaries have already been downloaded (eg. from Passport Advantage)ibm_infosvr_media_bin dict: the names of the binaries to use for the installation (by default the vanilla v11.7 files are there; if you want to install v11.5 these need to be replaced with the v11.5 file names)ibm_infosvr_ug_storage: the extra, raw storage device on the Unified Governance tier to be used by kubernetes (should be raw: unmounted, not in an lvm group, etc)ibm_infosvr_features dict: defining the features you want (True) vs do not want (False)Finally, the various credentials variables should be overridden to create a sufficiently secure environment. Searching for _upwd_ will reveal all of the password variables in the defaults/main.yml that you will want to override.
The configuration of Information Analyzer makes use of the IBM.infosvr-metadata-asset-manager role indirectly, using the import_role directive. Therefore IBM.infosvr-metadata-asset-manager is not explicitly in the dependencies of this role, but it does need to be installed for this role to work (if you are installing and configuring the Information Analyzer feature).
The following example playbook will do a complete installation and configuration of IBM InfoSphere Information Server using the default parameters from defaults/main.yml (and any overrides you've placed in eg. group_vars/all.yml). Note that because the entire installation is done across multiple tiers by this single role, you should use any_errors_fatal to avoid partial install / configuration of a tier in the event an earlier step fails on a different tier.
me: install and configure IBM InfoSphere Information Server
sts:
- ibm-information-server-repo
- ibm-information-server-domain
- ibm-information-server-engine
- ibm-information-server-clients
- ibm-information-server-ug
y_errors_fatal: true
les:
- ibm-infosvr
The following groups are expected in the inventory, as they are used to distinguish where various components are installed. Of course, if you want to install multiple components on a single server this can be done by simply providing the same hostname under each group. In the example below, for instance, the repository and domain tiers are both placed on 'serverA' while the engine tier will be installed separately on 'serverB' and the Unified Governance tier is also given its own system 'serverC'.
-information-server-repo]
nux host where the repository tier (database) should be installed (DB2)
erA.somewhere.com
-information-server-domain]
nux host where the domain (services) tier should be installed (WebSphere)
erA.somewhere.com
-information-server-engine]
nux host where the engine tier should be installed
erB.somewhere.com
-information-server-clients]
ndows host where the client applications should be installed, and a Metadata Interchange Server configured for Windows-only brokers / bridges
nt.somewhere.com
-information-server-ug]
nux host where the v11.7+ Unified Governance tier shuold be installed (kubernetes)
erC.somewhere.com
-information-server-external-db]
nux host that holds a pre-existing database into which to deploy XMETA, etc -- if no host provided, or this group is missing entirely, will install the bundled DB2 onto ibm-information-server-repo server
erD.somewhere.com
-cognos-report-server]
nux host where a pre-existing Cognos BI installation exists (for Information Governance Dashboard)
os.somewhere.com
-bpm]
nux host where a pre-existing BPM installation exists (currently unused)
somewhere.com
As with any Ansible inventory, sufficient details should be provided to ensure connectivity to the servers is possible (see http://docs.ansible.com/ansible/latest/intro_inventory.html#list-of-behavioral-inventory-parameters).
Apache 2.0
Christopher Grote