:serveruser: pbcom
:dbserverhost: 172.30.22.30
:appserverhost: 172.30.22.29
:dbuser: pbcom
:dbpassword: PBC0mu@t
:ribuser: pbcom
:tanukiwrapperdir: /home/{ribuser}/installers/wrapper-linux-x86-64-3.5.30
:membranedir: /var/lib/membrane
:membranebindir: {membranedir}/bin
:javadownloadlink: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
:membraneinstallerlink: google
:amqversion: 5.14.3

== Membrane Service Proxy Setup
Membrane Service Proxy (https://www.membrane-soa.org/service-proxy/) will provide a REST-to-SOAP middleware interface for RIB microservices to communicate to T24 and CMS using REST API.
For that, microservices in app server/s should have access to membrane server's ports `8085` and `8095`.

To install Membrane Service Proxy with Tanuki wrapper, follow the instructions below:

. Download `membrane-service-proxy-4.3.0.zip` and `membrane-uat.zip` from {membraneinstallerlink} and transfer to server.
. Using root or sudoer account unzip `membrane-service-proxy-4.3.0.zip`
+
[subs="attributes"]
[source,bash]
----
$ sudo unzip membrane-service-proxy-4.3.0.zip -d /var/lib/
$ sudo mv /var/lib/membrane-service-proxy-4.3.0 /var/lib/membrane
$ sudo unzip membrane-uat.zip -d /var/lib/membrane/
----
. Create `pbcom-membrane` link in `/etc/init.d/`
+
[subs="attributes"]
[source,bash]
----
$ sudo ln -s /var/lib/membrane/bin/membrane /etc/init.d/pbcom-membrane
----
. Add rc.d of pbcom-membrane
+
[subs="attributes"]
[source,bash]
----
$ sudo update-rc.d pbcom-membrane defaults
----
. Start `Membrane Service Proxy`
+
[subs="attributes"]
[source,bash]
----
$ sudo service pbcom-membrane start
Starting Membrane Proxy of T24...
Waiting for Membrane Proxy of T24........
running: PID:16028
----
. Check log file to see that proxy started properly
+
[subs="attributes"]
[source,bash]
----
$ tail -f /var/log/pbcom-membrane.log
----
. If an error was encountered, `wrapper.log` file will contain error details.
+
[subs="attributes"]
[source,bash]
----
$ tail -f /var/lib/membrane/wrapper.log
----

== ActiveMQ Setup
. Download a copy of activemq bin distribution from {amqversion} http://mirror.rise.ph/apache//activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz and transfer to server
. Create user `activemq` in server
+
[subs="attributes"]
[source,bash]
----
$ sudo useradd -r activemq
----
. Untar `apache-activemq-5.14.3-bin.tar.gz` to /var/lib/
+
[subs="attributes"]
[source,bash]
----
$ sudo tar -xzvf apache-activemq-5.14.3-bin.tar.gz -C /var/lib/
$ sudo mv /var/lib/apache-activemq-5.14.3 /var/lib/activemq/
----
. Edit `/var/lib/activemq/bin/env` and set
+
[subs="attributes"]
[source,bash]
----
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=$ACTIVEMQ_CONF/login.config -Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,com.pbcom,org.springframework"
----
. Create `activemq` link in `/etc/init.d/`
+
[subs="attributes"]
[source,bash]
----
$ sudo ln -s /var/lib/activemq/bin/linux-x86-64/activemq /etc/init.d/activemq
----
. Add rc.d of activemq
+
[subs="attributes"]
[source,bash]
----
$ sudo update-rc.d activemq defaults
----
. Start `activemq`
+
[subs="attributes"]
[source,bash]
----
$ sudo service activemq start
----
. Check logfiles
+
[subs="attributes"]
[source,bash]
----
$ tail -f /var/lib/activemq/data/wrapper.log
$ tail -f /var/lib/activemq/data/activemq.log
----