How to configure Enterprise Message Service Central Administration (EMS CA)client and server initially after installation?
Article ID: KB0085172
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = =
After installing the EMS CA Server on a Linux box and the EMS CA client on a Windows box, it is very confusing to configure them appropriately simply by following the documentation.
Environment:
= = = = = = =
Linux 2.6 kernel or higher for EMS CA server
Any Windows machine for EMS CA client
EMS Central Administration Server software
EMS Central Administration Client Software
Resolution:
1). The EMS CA server software needs to be installed on a Linux box with kernel version 2.6 or higher. This package has not been tested on machines having 2.4 kernels and httpd startup issues have been seen when the software is installed on Linux machines with 2.4 kernels.
2). The httpd.conf file located in $TIBCO_HOME/ems/ca/1.0/httpd/conf needs to be modified as follows:
<Location /svn>
DAV svn
SVNPath $TIBCO_HOME/ems/ca/1.0/repos
</Location>
If not already set, point the SVNPath to the repos directory of your current EMS CA installation.
For LDAP based authentication, the <Location> section of the file needs to be modified as follows:
<Location />
Order allow,deny
Allow from 127.0.0.1/255.0.0.0
#
AuthUserFile /dev/null
AuthType Basic
AuthName "TIBCO EMS Central Administration"
AuthBasicProvider file ldap
AuthzLDAPAuthoritative off
# windows directory server
AuthLDAPURL "ldap://10.105.70.170:389/DC=test,DC=na,DC=tibco,DC=com?cn?sub?(objectClass=*)"
AuthLDAPBindDN "CN=Administrator,CN=Users,DC=test,DC=na,DC=tibco,DC=com"
AuthLDAPBindPassword Tibco123
Require valid-user
Satisfy Any
</Location>
For file based authentication, the <Location> section of the file needs to be modified as follows:
<Location />
Order allow,deny
Allow from 127.0.0.1/255.0.0.0
#
AuthUserFile /home2/corp/foo/tibco_linux/ems/ca/user_auth.txt
AuthType Basic
AuthName "TIBCO EMS Central Administration"
AuthBasicProvider file
AuthzLDAPAuthoritative off
# windows directory server
# AuthLDAPURL "ldap://10.105.70.170:389/DC=test,DC=na,DC=tibco,DC=com?cn?sub?(objectClass=*)"
# AuthLDAPBindDN "CN=Administrator,CN=Users,DC=test,DC=na,DC=tibco,DC=com"
# AuthLDAPBindPassword Tibco123
Require valid-user
Satisfy Any
</Location>
3). A sample user “foo”, whose password is set to “foo” should be created in all EMS servers that are to be monitored.
4). Use the command “grant admin user=foo all” for all EMS servers.
5). Use the command “add member $admin foo” for all EMS servers.
6). Now download the “htpasswd” utility from the Internet onto your Linux box, if you do not have this already.
7). Use the command “htpasswd –c /home2/corp/foo/tibco_linux/ems/ca/user_auth.txt foo”.
8). When prompted for new password and retype the password, entering “foo”.
9). The “pre-commit.perms” file located at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the user “foo” in a new line.
10). Modify the “svnserve.conf” file in $TIBCO_HOME/ems/ca/1.0/repos/conf to un-comment the following lines:
anon-access = read
auth-access = write
password-db = passwd
authz-db = authz
11). The authz file at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the following line:
foo = rw
12) .The passwd file at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the following line:
foo=foo
13). Go to $TIBCO_HOME/ems/ca/1.0/bin and run the “setenv” script.
14). Now start the CA server as “emsca start”.
15). Create a new deployment server as “emsca server create bar-lnx1”. “bar-lnx1” is the name of the box where the CA server is running. This name is the name of the deployment server.
16. Do a “emsca server restart bar-lnx1”. This will start the deployment server.
17. Create an agent for each EMS server you want to monitor. In this example, we have created two agents to monitor two EMS servers running on a desktop and a laptop respectively. Both will be using the same deployment server bar-lnx1.
emsca agent create bar-lnx1 name=FOO-DESKTOP path= TIBCO_HOME/ems/ca/FOO-DESKTOP.emsserver url=tcp://foo-dt:7222
emsca agent create bar-lnx1 name=FOO-LAPTOP path= TIBCO_HOME/ems/ca/FOO-LAPTOP.emsserver url=tcp://foo-t400:7222
18. Now install the EMS CA client on a Windows box.
19. Start the EMSCA Eclipse environment. It will ask you to provide a workspace directory.
20. Do a File->New->TIBCO EMS Central Administration Project. It will ask you for the host name, where the CA server is running and the port number. The port number is 9011 by default. If it asks you for the username/password, use “foo/foo”.
After this, the documentation is very straight forward on how to sync the configs and how to save configurations to a repository.
Description:
= = = = = =
After installing the EMS CA Server on a Linux box and the EMS CA client on a Windows box, it is very confusing to configure them appropriately simply by following the documentation.
Environment:
= = = = = = =
Linux 2.6 kernel or higher for EMS CA server
Any Windows machine for EMS CA client
EMS Central Administration Server software
EMS Central Administration Client Software
Resolution:
1). The EMS CA server software needs to be installed on a Linux box with kernel version 2.6 or higher. This package has not been tested on machines having 2.4 kernels and httpd startup issues have been seen when the software is installed on Linux machines with 2.4 kernels.
2). The httpd.conf file located in $TIBCO_HOME/ems/ca/1.0/httpd/conf needs to be modified as follows:
<Location /svn>
DAV svn
SVNPath $TIBCO_HOME/ems/ca/1.0/repos
</Location>
If not already set, point the SVNPath to the repos directory of your current EMS CA installation.
For LDAP based authentication, the <Location> section of the file needs to be modified as follows:
<Location />
Order allow,deny
Allow from 127.0.0.1/255.0.0.0
#
AuthUserFile /dev/null
AuthType Basic
AuthName "TIBCO EMS Central Administration"
AuthBasicProvider file ldap
AuthzLDAPAuthoritative off
# windows directory server
AuthLDAPURL "ldap://10.105.70.170:389/DC=test,DC=na,DC=tibco,DC=com?cn?sub?(objectClass=*)"
AuthLDAPBindDN "CN=Administrator,CN=Users,DC=test,DC=na,DC=tibco,DC=com"
AuthLDAPBindPassword Tibco123
Require valid-user
Satisfy Any
</Location>
For file based authentication, the <Location> section of the file needs to be modified as follows:
<Location />
Order allow,deny
Allow from 127.0.0.1/255.0.0.0
#
AuthUserFile /home2/corp/foo/tibco_linux/ems/ca/user_auth.txt
AuthType Basic
AuthName "TIBCO EMS Central Administration"
AuthBasicProvider file
AuthzLDAPAuthoritative off
# windows directory server
# AuthLDAPURL "ldap://10.105.70.170:389/DC=test,DC=na,DC=tibco,DC=com?cn?sub?(objectClass=*)"
# AuthLDAPBindDN "CN=Administrator,CN=Users,DC=test,DC=na,DC=tibco,DC=com"
# AuthLDAPBindPassword Tibco123
Require valid-user
Satisfy Any
</Location>
3). A sample user “foo”, whose password is set to “foo” should be created in all EMS servers that are to be monitored.
4). Use the command “grant admin user=foo all” for all EMS servers.
5). Use the command “add member $admin foo” for all EMS servers.
6). Now download the “htpasswd” utility from the Internet onto your Linux box, if you do not have this already.
7). Use the command “htpasswd –c /home2/corp/foo/tibco_linux/ems/ca/user_auth.txt foo”.
8). When prompted for new password and retype the password, entering “foo”.
9). The “pre-commit.perms” file located at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the user “foo” in a new line.
10). Modify the “svnserve.conf” file in $TIBCO_HOME/ems/ca/1.0/repos/conf to un-comment the following lines:
anon-access = read
auth-access = write
password-db = passwd
authz-db = authz
11). The authz file at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the following line:
foo = rw
12) .The passwd file at $TIBCO_HOME/ems/ca/1.0/repos/conf needs to be modified in order to include the following line:
foo=foo
13). Go to $TIBCO_HOME/ems/ca/1.0/bin and run the “setenv” script.
14). Now start the CA server as “emsca start”.
15). Create a new deployment server as “emsca server create bar-lnx1”. “bar-lnx1” is the name of the box where the CA server is running. This name is the name of the deployment server.
16. Do a “emsca server restart bar-lnx1”. This will start the deployment server.
17. Create an agent for each EMS server you want to monitor. In this example, we have created two agents to monitor two EMS servers running on a desktop and a laptop respectively. Both will be using the same deployment server bar-lnx1.
emsca agent create bar-lnx1 name=FOO-DESKTOP path= TIBCO_HOME/ems/ca/FOO-DESKTOP.emsserver url=tcp://foo-dt:7222
emsca agent create bar-lnx1 name=FOO-LAPTOP path= TIBCO_HOME/ems/ca/FOO-LAPTOP.emsserver url=tcp://foo-t400:7222
18. Now install the EMS CA client on a Windows box.
19. Start the EMSCA Eclipse environment. It will ask you to provide a workspace directory.
20. Do a File->New->TIBCO EMS Central Administration Project. It will ask you for the host name, where the CA server is running and the port number. The port number is 9011 by default. If it asks you for the username/password, use “foo/foo”.
After this, the documentation is very straight forward on how to sync the configs and how to save configurations to a repository.
Issue/Introduction
How to configure Enterprise Message Service Central Administration (EMS CA)client and server initially after installation?
Feedback
Yes
No
Powered by
