Deploy xMS Agent on Apache Tomcat
This
is part one of an additional guide to deploy the xms-server.war on a DIY
Windows Environment. The next part describe the registration of an xCP
environment manually.
If you are install xCP 2.0 on Windows you can download the compiled exe-package. The *.exe download package does not include the catalina.bat file, because the *.exe package installs tomcat as a Windows Service. The tomcat memory settings are set in the Apache Tomcat 7.0 Properties Application. The zipped package includes the catalina.bat file. The full requirements are listet on the D7 xMS preparation page.
If you are install xCP 2.0 on Windows you can download the compiled exe-package. The *.exe download package does not include the catalina.bat file, because the *.exe package installs tomcat as a Windows Service. The tomcat memory settings are set in the Apache Tomcat 7.0 Properties Application. The zipped package includes the catalina.bat file. The full requirements are listet on the D7 xMS preparation page.
1.
Stop
Apache Tomcat 7.0 Services
2.
Copy
the xms-server.war file in the Tomcat 7.0 webapps folder
3.
Rename
the *.war extension to *.zip and extract the file and delete the original *.zip
file afterwards
4.
Open
cmd – the windows command center
navigate to \webapps\xms-server\WEB-INF
navigate to \webapps\xms-server\WEB-INF
xcopy
xms-agent-context.xml xms-server-context.xml
ensure
that the xms-agent-context and the xms-server-context files are equal
<bean
id="xmsServerConfigurator"
class="com.documentum.xms.server.XmsServerConfiguration"> <!--
Whenever an xMS agent is being deployed, set applicationType to
"AGENT_TYPE" --> <property
name="applicationType" ref="AGENT_TYPE"/> </bean>
5.
Open
the Apache Tomcat 7.0 Properties Application and set:
-XX:MaxPermSize=2048m
-XX:MaxPermSize=2048m
Apache Tomcat 7.0
Properties
6.
Start
Apache Tomcat Services
wait >1 minutes until the xms-server is completely deployed
wait >1 minutes until the xms-server is completely deployed
7.
check
the deployment: http://<localhost>:<8080>/xms-server
port 8080 for non SSL / port 8443 for SSL connection
port 8080 for non SSL / port 8443 for SSL connection
Testwebpage to check
the xMS Agent and xMS registered environment
The
heart of the xCelerated Management System version 1.0 are the xms-tools.
All files located in
the bin folder of the xms-tools-1.0 package.
The
tool include the Command Line Interface (CLI) , the xMS Agent, the xMS Server
and some batch files.
The xms.bat is called CLI in the documentation and located in the mainbin folder. Ensure you have set thexms-server.properties file correctly (located in the folder config). The CLI is not only a small administrative command tool, you can display all environments (show-environments) or one in detail (show-environment-details –name test_xcp) , import and export the configuration, show/create/disable users and execute the deployment into the registed environment.
The xms.bat is called CLI in the documentation and located in the mainbin folder. Ensure you have set thexms-server.properties file correctly (located in the folder config). The CLI is not only a small administrative command tool, you can display all environments (show-environments) or one in detail (show-environment-details –name test_xcp) , import and export the configuration, show/create/disable users and execute the deployment into the registed environment.
xMS Tools version 1.0
2013 © Mr.Crazyapple
2013 © Mr.Crazyapple
The
xMS Server is only available, if you have installed the vFabric tc Server in
your VMWare environment.
The
xMS Agent reffered to the xms-env-registration-ui.bat. In this user-interface you can add all your
available Documentum components (eg.: Repository, CTS, CIS, BAM, etc). This
Agent make your xCP Applications in your environment available.
This screenshot shows
all the commands that are executed in the CLI.
The
xMS Agent reffered to the xms-env-registration-ui.bat file.
In this user-interface you can add all your available Documentum components
(eg.: Repository, CTS, CIS, BAM, etc).
The manual
registration is only necessary if you don’t use the xMS Server and the
blueprint installation.
This
Agent make your xCP application in your do-it-yourself-environment
available.
If
the utility is accessing the xMS Agent for the first time, it prompts you to
set a password for the
default admin user. Use this password for subsequent access to the utility.
default admin user. Use this password for subsequent access to the utility.
You
do not have to create additional system accounts, because there can be only one
SERVICE account per environment.
You
can use the SERVICE_ENDPOINT system account type, if you want to create a
generic account for use across several vDCs. SERVICE_ENDPOINT is specific
to each environment, and you need to specify it in the environment profile
XML file for each environment.
This
screenshot was taken from the xMS Agent environment registration utility.
Register
your environment manually. Create a new environment blueprinte file and
register all the recommended Documentum components:
Repository: Content Server Ver.7.0
BAM: BAM-Server 2.0
App Host: Tomcat Server 7.0.29
Documentum Administrator: DA 7.0
Search: xPlore 1.3
BPS: Process Integrator 2.0
Content Intelligence Server: CIS 7.0
Content Transformation Server: CTS 7.0
(optional) Thumbnail Server 7.0
Repository: Content Server Ver.7.0
BAM: BAM-Server 2.0
App Host: Tomcat Server 7.0.29
Documentum Administrator: DA 7.0
Search: xPlore 1.3
BPS: Process Integrator 2.0
Content Intelligence Server: CIS 7.0
Content Transformation Server: CTS 7.0
(optional) Thumbnail Server 7.0
This screenshot
displays the registration of the primary repository. You can add as many
repositories you like.
Save
your settings and restart the xMS Agent. Remember: the agent is part of the app
server (Tomcat) webapps. Please restart the Tomcat services on your host
windows server.
Wait until all webapps was successfully (re)deployed.
Wait until all webapps was successfully (re)deployed.
No comments:
Post a Comment