xCP environment registration Part III

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).

xms_app_registration_detail_000064
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.

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.xms_app_registration_detail_000065

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

xms_app_registration_detail_000066
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.

27. August 2013Permalink

xCP environment registration Part II

The heart of the xCelerated Management System version 1.0 are the xms-tools.

xms_bin_folder
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 main bin folder. Ensure you have set the xms-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_000070
xMS Tools version 1.0
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.

xms_app_registration000071
This screenshot shows all the commands that are executed in the CLI.
19. August 2013Permalink

xCP environment registration Part I

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.

  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

     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

    Apache Tomcat 7.0 Properties
    Apache Tomcat 7.0 Properties
  6. Start Apache Tomcat Services
    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

    xms_app_registration_detail_000063
    Testwebpage to check the xMS Agent and xMS registered environment

Download Apache Tomcat 7.0.29 from the Apache archive.

9. August 2013Permalink

short tutorial: upgrading Content Server

short tutorial: upgrading Content Server

Upgrading your Content Server on Windows Server OS

The current version of xCelerated Composition Platform (xCP) is version 1.5 (6.6 release). It is not possible to update the entire software platfrom 1.5 to 1.6 (6.7 release).

Note: Due to changes in the licensing of some 3rd party components that are used in the xCP Developer Edition, the 1.6 release has been delayed.  Please watch this page for an announcement of its availability. 

https://community.emc.com/docs/DOC-7850

The first step is to upgrade the Content Server from the released version 6.6 to the current version 6.7 SP1. Here is the upgrade checklist with additional screenshots and comments.

checklist

  1. Back up the repository.
  2. Back up  customized formats(dm_format objects)

    Content Server 6.7 SP1 start installation
  3. Run the consistency checker job or dmbasic syntax (optional, if you are not upgrading an new xCP installation)
  4. Disable all jobs in the Documentum Administrator
  5. Shut down the repository and the connection broker (docbroker) in the Server Manager
  6. Shut down the Documentum Java Method Server services. Switch the start up method from automatic to manual to ensure that the services does not start automatically after a host restart.
  7. Start the installation
  8. install xPlore or FAST search engine (FAST is not supported)

    Content Server 6.7 SP1 select search engine
  9. select upgraderepository and docbrocker

    Content Server 6.7 SP1 upgrade repository
  10. don’t select create additional repository or docbrocker and finish the section

    Content Server 6.7 summary information
  11. finish installation, check install logfile in the source folder
  12. restart the environment (check Java memory size in Windows Task Manager, check the Documentum Services in the Windows Services, check the log files in the new JBoss 5.1 folder)
  13. stop the Application Server Service
  14. deploy JBoss war files for Taskspace, Administrator etc. in the deploy folder
  15. restart Application Server Service
  16. install DAR applications (Taskspace, Administrator etc.) using Composer 6.7 DARInstaller