IBM’s product, Partner Engagement Manager (PEM), have been available as a SaaS offering for quite some time. But customer requirements have also made IBM offer an On Premise version. The way this is done is actually to offer a Docker Container with PEM. In that way the install is easy, and the PEM on Premise will be updated in the same way as PEM as a Service. So that IBM don’t end up with customers running on an outdated PEM on Premise in their local environment.
I will in this post go through an installation of PEM on Premise.
Server Info
I will start by setting up a new server on my VMWare Fusion. This server is installed with the following setup (based on the requirements on this link):
| OS: | RedHat Enterprise Linux 7 64-bit – Minimal Install |
| Processors: | 2 |
| Memory: | 2 GB |
| Hard Disk: | 50 GB |
| Network: | Static: 192.168.192.31 (Hostname: pemonpremise.demos.ibm.int) |
| Users: | root, pem |
Install steps
There are some Install steps needed to make this work.
- Access to IBM Bluemix, and IBM Bluemix Docker Registry.
- Install Docker Engine 1.11.0 or later
- Install Cloud Foundry CLI
- Install IBM Containers Cloud Foundry Plug-Ins
- Pull PEM Docker Image
- Install DB2 10.5 FP7 or Oracle 12c Database
- Set up The MountDirectory
Access to IBM Bluemix and Bluemix Docker Registry
Since this is software delivered as a Docker Container, it is a new way of getting it compared to traditional software. So for getting access to this an account on IBM Bluemix is needed. Since I am an IBM’er I have access already. But the way of doing this for others is described here.
Install Docker Engine 1.11.0 or later
Next thing is to is to get the Docker engine installed on my VMWare Image.
- Update Yum Registry
[root@pemonpremise ~]# yum update
2. Add the YUM Repo
[root@pemonpremise ~]# tee /etc/yum.repos.d/docker.repo <<-EOF > [dockerrepo] > name=Docker Repository > baseurl=https://yum.dockerproject.org/repo/main/centos/7 > enabled=1 > gpgcheck=1 > gpgkey=https://yum.dockerproject.org/gpg > EOF
3. Install Docker Package
[root@pemonpremise ~]# yum -y install docker-engine
4. Start the Docker Deamon
[root@pemonpremise ~]# systemctl start docker
[root@pemonpremise ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2016-06-30 05:21:31 PDT; 6s ago
Docs: https://docs.docker.com
Main PID: 9617 (docker)
Memory: 15.1M
CGroup: /system.slice/docker.service
├─9617 /usr/bin/docker daemon -H fd://
└─9622 docker-containerd -l /var/run/docker/libcontainerd/docker-c...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int docker[9617]: time="2016-06-30T05:...
Jun 30 05:21:31 pemonpremise.demos.ibm.int systemd[1]: Started Docker Applica...
Hint: Some lines were ellipsized, use -l to show in full.
[root@pemonpremise ~]#
5. Test that Docker works
[root@pemonpremise ~]# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
ad01a741289f: Pull complete
Digest: sha256:af451bc5c4d6e87b64303f707f7bd98debd7fd3175a676c08f4bf46cb48813d4
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker Hub account:
https://hub.docker.com
For more examples and ideas, visit:
https://docs.docker.com/engine/userguide/
[root@pemonpremise ~]#
Install Cloud Foundry CLI
Next step is to install the Cloud Foundry CLI. This can be downloaded from this link for your OS. I chose to download it by using wget since my server don’t have a GUI. So I get the filepath to the correct file, and is giving the file the name cf-cli-installer.rpm. The complete steps for the following is described here.
[root@pemonpremise ~]# wget -O cf-cli-installer.rpm https://cli.run.pivotal.io/stable?release=redhat64&version=6.20.0&source=github-rel
Install the RPM.
[root@pemonpremise ~]# rpm -i cf-cli-installer.rpm
Check that Cloud Foundry was correctly installed.
[root@pemonpremise ~]# cf -v cf version 6.20.0+25b1961-2016-06-29
Install IBM Containers Cloud Foundry Plug-Ins
The different paths for different OS is described on this link.
[root@pemonpremise ~]# cf install-plugin https://static-ice.ng.bluemix.net/ibm-containers-linux_x64 **Attention: Plugins are binaries written by potentially untrusted authors. Install and use plugins at your own risk.** Do you want to install the plugin https://static-ice.ng.bluemix.net/ibm-containers-linux_x64? (y or n)> y Attempting to download binary file from internet address... 12425856 bytes downloaded... Installing plugin ibm-containers-linux_x64... OK Plugin IBM-Containers v0.8.897 successfully installed.
Verify the installation
[root@pemonpremise ~]# cf plugins Listing Installed Plugins... OK Plugin Name Version Command Name Command Help IBM-Containers 0.8.897 ic IBM Containers plug-in
Login to IBM Bluemix through Cloud Foundry
When all is created, I log in with my IBM Bluemix account.
[root@pemonpremise ~]# cf login -a https://api.ng.bluemix.net
API endpoint: https://api.ng.bluemix.net
Email> erlend.smines@no.ibm.com
Password>
Authenticating...
OK
Select an org (or press enter to skip):
1. erlend.smines@no.ibm.com
2. PEM
Org> 2
Targeted org PEM
Targeted space prod
API endpoint: https://api.ng.bluemix.net (API version: 2.54.0)
User: erlend.smines@no.ibm.com
Org: PEM
Space: prod
Then log in to the IBM Container Plugin to be able to pull the PEM Docker Image. Select option number 2.
[root@pemonpremise ~]# cf ic login
List the images you have access to.
[root@pemonpremise ~]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE registry.ng.bluemix.net/gold/pem 3.4.24 5fbd6d79dbee 9 weeks ago 478.5 MB registry.ng.bluemix.net/ibm-mobilefirst-starter latest 3479cbb0ebf3 8 weeks ago 523.6 MB registry.ng.bluemix.net/ibm-node-strong-pm latest 37a6db86742f 8 weeks ago 240.4 MB registry.ng.bluemix.net/ibmliberty javaee7 77b68609eecb 2 weeks ago 325.4 MB registry.ng.bluemix.net/ibmliberty latest 77b68609eecb 2 weeks ago 325.4 MB registry.ng.bluemix.net/ibmliberty webProfile6 cd1753bef3b8 2 weeks ago 264.8 MB registry.ng.bluemix.net/ibmliberty webProfile7 c0aa4441c231 2 weeks ago 283.1 MB registry.ng.bluemix.net/ibmnode latest 22c21d740b39 8 days ago 188 MB registry.ng.bluemix.net/ibmnode v4 22c21d740b39 8 days ago 188 MB registry.ng.bluemix.net/ibmnode v1.1 3be9730288e5 8 days ago 177.5 MB registry.ng.bluemix.net/ibmnode v1.2 57609972b824 8 days ago 183.7 MB [root@pemonpremise ~]#
Pull PEM Docker Image
To pull the image, first unset the DOCKER_HOST and DOCKER_TLS_VERIFY vaiables.
[root@pemonpremise ~]# unset DOCKER_HOST DOCKER_TLS_VERIFY
Pull the PEM Docker image. It will take a while to download. Go grab a coffee…
[root@pemonpremise ~]# docker pull registry.ng.bluemix.net/gold/pem:3.4.24 3.4.24: Pulling from gold/pem f075d88cadb6: Downloading [==> ] 4.226 MB/71.13 MB dd95d93417e7: Downloading [=> ] 3.707 MB/100.9 MB c6509c3fb5b5: Download complete 4a32c24ccfaf: Downloading [==========================> ] 4.825 MB/9.188 MB 3f061f06dca9: Waiting da0398e0dac8: Waiting c2b25665bca5: Waiting e3a498a3915c: Waiting c961da4de4c9: Waiting 9dde4b67a785: Waiting c03340520f04: Waiting 73d6918a1f03: Waiting a0bb0fba2d73: Waiting 699fa0581193: Waiting f29715c8f250: Waiting a09df7535deb: Waiting 3d23dc15185e: Waiting 7b72d3826ab1: Waiting ad98e24e601d: Waiting 66172ec2fdab: Waiting 947e581518a4: Waiting 9ce18becacef: Waiting c5e93e6d1bfe: Waiting 8cbb9b6986fa: Waiting 98a3eba4d6c0: Waiting 0584546cd248: Waiting 037d91b3dcdf: Waiting 48219d0d93a9: Waiting 8afb08f8a99c: Waiting 181d043c385b: Waiting
Install DB2 10.5 FP7 or Oracle 12c Database
Regarding the Database step, I already have a DB2 10.5 server installed in my environment, and is using this existing server. So I will not go through the installation of the Database server.
Mount Directory setup
The MountDirectory.zip can be downloaded from the following url: http://idev2008server.irv.ustx.ibm.com:9090/kc/SSKPRS/com.ibm.help.pem.local.doc/c_components_of_MountFiles.html
Put the zip-file somewhere on the host machine and unzip it.
0 comments on “Installing Partner Engagement Manager (PEM) on Premise” Add yours →