xCP 2.0 install questions.

Hi everyone. I've installed an xCP environment as the one described in the xcp2 deploy guide but have a couple of questions as my testing xcp app doesn't work right. I've seen that people are already messing with xcp so these should be easy for you...

1.- There's a manager.war (unzipped in xml-tools) that should be copied in the application server (aka tomcat in my case) webapps folder but... there's already a manager webapp there. It doesn't seem to overwrite the app already deployed so I've changed the war's name to manager2.war and referenced it in the xMs Agent Environment for the deployment but it doesn't seem to work. With the "original" manager webapp in tomcat the xcp war gets copied to the webapp but doesn't get deployed. ¿Is the manager.war necesary for tomcat or only for tc Server?

2.- I'm getting an in the deployment of that xcp app reported on the bam.log file when the xcp app is deploying

[16:37:20] ERROR [ContextLoader] Context initialization failed

org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'dataSourceEngineService' defined in URL [jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/temp/5-testxcp/WEB-INF/lib/com.emc.xcp.services.historical-2.0.0000.1303.jar!/com/emc/xcp/config/app/applicationContext-historical.xml]: Could not resolve placeholder 'bam.server.host'

at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:209)

This looks like a jar file packaged in xcp designer, ¿what am I missing?

3.- Also when the deployment succeeds ¿? the following webpage is opened http://D7xCP2:8000/testxcp?reload with a 8000 port ¿where can I configure this to call the right port (8080)?

4.- If I'm lucky enough to get this going I'd like to try a OOTB deployment with xMS Server but ¿Can you install the server in tomcat or only on tc Server as the deployment guide says? ¿Has anyone tried?

Thanks.

Find more posts tagged with

Documentum

Captiva

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

jazuli14

Hi Carlos,

1. Which version of Tomcat you are using? xCP 2.0 and xMS only support Tomcat 7, not Tomcat 6. The manager.war that is shipped will only work on version 7, and it is only needed if you are deploying the Standard Edition of tcServer. If you are using the Developer Edition of tcServer, or you are using vanilla Tomcat, then the manager war is already shipped and you don't need to redeploy it. You will need to configure a user (using tomcat-users.xml) that has access to the "manager-script" role (I usually set up a user called "admin" with the roles "manager-gui,manager-script". The manager war is absolutely necessary for the deployment from xCP Designer/xMS Tools to work. (We use some APIs available from this app to do the deployment of the xCP app war programmatically.)

2. bam.server.host seems to be undefined. Can you verify that you have set this value in the bam-server.properties file? The path to this file is set in wrapper.conf and the value should be set to the ip or hostname of the bam server war. Here are the settings I am using in the environment I set up recently.

You need to have a file called bam-server.properties, which I placed in C:\tcServer\apphost\customConf - and this path is entirely dependent on your environment (you might have installed your tcServer instance somewhere else, and called it something else instead of apphost) and the "customConf" folder name is entirely arbitrary (you can call this whatever you want) - set up correctly. The contents of my bam-server.properties file are:

# BAM Server properties.

# This file contains BAM server endpoint details and used by xCP application for establishing remote session

# with BAM server and performing Spring HTTP remote calls to BAM services

# Note: this file is part of the xCP application template.

# IMPORTANT: No updates performed to this file during deployment of xCP application at the moment.

bam.server.host=localhost

bam.server.port=8000

bam.server.context=bam-server

Of course, the BAM subsystem of xCP needs to be aware of where this file is, and you set up the path to this file in the wrapper.conf file, which I have in c:\tcServer\apphost\conf (the standard conf directory under your installation is where this file is located). Also, one note is that I am using tcServer... and I believe that wrapper.conf is specific to a tcServer setup. (I am not sure where to set this up if you use vanilla Tomcat... my guess is the setclasspath file under <tomcat installation>\bin but I could be wrong... or you could just add it to the environment classpath... hopefully this is documented somewhere. If not, let me know.) My wrapper.conf has the following added line under the section headed "# Java Classpath":

wrapper.java.classpath.5=C:\tcServer\apphost\customConf

(The .5 is also arbitrary, it should be the next number based on the list you have. For example, if the last parameter in the list was "wrapper.java.classpath.7", then you would create yours with .8 instead of .5)

Again, this path is entirely up to you, you can make it wherever you want. Just make sure the following files are there:

bam-server.properties
dfc.keystore
dfc.properties

3. tcServer's default port is 8000 and unfortunately it is an oversight that the deployment code is not able to get the port information back to the Designer to construct the URL correctly based on the selected/defined deployment environment from xMS Agent. This is a known issue. As a temporary measure (until we can fix this issue in an upcoming release), we've set up a parameter you can use in the xcpdesigner.ini file (found in the directory you unzipped the Designer to). The parameter by default is:

-Dxcp.application.url.port=8000

which for your case you can change to:

-Dxcp.application.url.port=8080

and then restart the Designer and the deployment should set the correct URL. If you switch environments between deployments then we recommend for now that all the environments should use the same port if you want the port to auto build correctly. As I said, this is a known limitation and we plan to fix it as soon as time allows (the fix is not trivial - it requires a new callback API to provide Designer with information from xMS which is not how it was originally architected).

4. I believe that xMS should work fine on Tomcat 7.

I believe everything I've mentioned here is documented pretty well, but maybe not all in one place. I'd love to hear your feedback on how we could make the documentation better. Let me know if you need any further clarification, or if you encounter any further issues; I'd be happy to help.

Thanks,

Ahson Ahmad

(Product Manager for xCP Designer at EMC)

All comments

jazuli14

Hi Carlos,

# BAM Server properties.

# This file contains BAM server endpoint details and used by xCP application for establishing remote session

# with BAM server and performing Spring HTTP remote calls to BAM services

# Note: this file is part of the xCP application template.

# IMPORTANT: No updates performed to this file during deployment of xCP application at the moment.

bam.server.host=localhost

bam.server.port=8000

bam.server.context=bam-server

wrapper.java.classpath.5=C:\tcServer\apphost\customConf

Again, this path is entirely up to you, you can make it wherever you want. Just make sure the following files are there:

bam-server.properties
dfc.keystore
dfc.properties

-Dxcp.application.url.port=8000

which for your case you can change to:

-Dxcp.application.url.port=8080

4. I believe that xMS should work fine on Tomcat 7.

Thanks,

Ahson Ahmad

(Product Manager for xCP Designer at EMC)

carlosanchez-g2dHi

Hi Ahson,

Thank you very much for the answers. I'm installing everything over tomcat 7.0 on 2 machines as described in the deployment guide. Tomcat is installed as a service in both machines and an extra tomcat instance with 7xxx ports is manually started/stopped in the content server machine for the xms-tools apps as described in the documents.

As for the wrapper configuration this isn't build in the vanila install of tomcat, everything listed as a wrapper configuration in the guide was added as a "-Dbam.properties=C:\Program Files\Apache Software Foundation\Tomcat 7.0\bam\bam.properties" in the Server startup script.

I grouped all the properties files (dfc, keystore, bam.properties and bam.server in the same folder) and added it to the classpath as my bam installation resides in the same instance as bps.

As for the docs it's very well documented I'd only remove paragraph 15 page 31 of the deployment guide with the manager.war since Tomcat 7.0 has this webapp installed and 7.0 is the only one supported.

Maybe describe the user's that have to be created as Service_endpoints for the xMS Agent (one for the content server, one for the manager deployment...)

And maybe note regarding the wrapper deployment method for Apache tomcat as it isn't bundled with the install package.

Thank you very much for your answers.

I've been able to deploy the app now my sign in page is blank but I'm way nearer the end!!

ranjaswin

Hi Carlos,

trying to install xcp 2.0 in tomcat 7. After a long struggle we finally completed the wrapper deployment for tomcat, now we are struck up with an error saying :

org.springframework.beans.factory.BeanInitializationException: Could not load properties; nested exception is java.io.FileNotFoundException: ${bam.properties} (The system cannot find the file specified)

bam-server.properties,dfc.properties are placed inside customConf and the corresponding updation is done in wrapper.conf..but couldnot find where we are going wrong.. anybody there to help??!

Regards,

Ranjani.A

jazuli14

Carlos,

As for the manager WAR - we should probably make it clear that it is not included in the STANDARD edition of tcServer but if you are using either the DEVELOPER edition of tcServer OR you are using vanilla Tomcat, then you don't need to install the manager WAR as it is already installed.

Let me know if you still need help getting everything running.

jazuli14

Ranjani,

Can you please post the contents of your wrapper.conf?

Thanks,

ranjaswin

Hi Ahson,

Thanks for replying.!! heres the wrapper.conf

#********************************************************************

# Wrapper Properties

#********************************************************************

# Java Application

wrapper.java.command=C:\Program Files\Java\jdk1.6.0_30\bin\java

# Java Main class. This class must implement the WrapperListener interface

# or guarantee that the WrapperManager class is initialized. Helper

# classes are provided to do this for you. See the Integration section

# of the documentation for details.

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp

# Java Classpath (include wrapper.jar) Add class path elements as

# needed starting from 1

wrapper.java.classpath.1=C:\apache-tomcat-7.0.27\instance1\common\lib\wrapper.jar

wrapper.java.classpath.2=C:\Program Files\Java\jdk1.6.0_30\lib\tools.jar

wrapper.java.classpath.3=C:\apache-tomcat-7.0.27\instance1\bin\bootstrap.jar

wrapper.java.classpath.4=C:\apache-tomcat-7.0.27\instance1\bin\threaddumpwrapper.jar

wrapper.java.classpath.5=C:\apache-tomcat-7.0.27\instance1\bin\tomcat-juli.jar

wrapper.java.classpath.6=C:\apache-tomcat-7.0.27\instance1\Customconf

wrapper.java.classpath.7=C:\apache-tomcat-7.0.27\instance1\bin\bootstrap.jar

wrapper.java.classpath.8=C:\apache-tomcat-7.0.27\instance1\bin\wrapper.jar

wrapper.java.classpath.9=C:\apache-tomcat-7.0.27\lib\catalina.jar

wrapper.java.classpath.10=C:\apache-tomcat-7.0.27\lib\tomcat-coyote.jar

wrapper.java.classpath.11=C:\apache-tomcat-7.0.27\lib\catalina.jar

wrapper.java.classpath.12=C:\apache-tomcat-7.0.27\lib\tomcat-util.jar

wrapper.java.classpath.13=C:\apache-tomcat-7.0.27\lib\servlet-api.jar

wrapper.java.classpath.14=C:\apache-tomcat-7.0.27\lib\jsp-api.jar

wrapper.java.classpath.15=C:\apache-tomcat-7.0.27\lib\jasper.jar

wrapper.java.classpath.16=C:\apache-tomcat-7.0.27\lib\tomcat-api.jar

wrapper.java.classpath.17=C:\apache-tomcat-7.0.27\lib\*.jar

wrapper.java.classpath.18=C:\apache-tomcat-7.0.27\instance1\*.properties

wrapper.java.classpath.19=C:\apache-tomcat-7.0.27\instance1\bam\*.properties

# Java Library Path (location of Wrapper.DLL or libwrapper.so)

wrapper.java.library.path.1=C:\apache-tomcat-7.0.27\instance1\common\lib

# Java Additional Parameters

wrapper.java.additional.1=-Djava.endorsed.dirs=C:\apache-tomcat-7.0.27\instance1\common\endorsed

wrapper.java.additional.2=-Dcatalina.base=..

wrapper.java.additional.3=-Dcatalina.home=..

wrapper.java.additional.4=-Djava.io.tmpdir=..\temp

# Comment out the following for Tomcat 5.0 and 4.1.x

wrapper.java.additional.5=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager

wrapper.java.additional.6=-Djava.util.logging.config.file=C:\apache-tomcat-7.0.27\conf\logging.properties

wrapper.java.additional.7=-Dwrapper.dump.port=7777

wrapper.java.additional.8="-Xmx2048M"

wrapper.java.additional.9="-Xss1024K"

wrapper.java.additional.10="-XX:MaxPermSize=512m"

# Initial Java Heap Size (in MB)

wrapper.java.initmemory=128

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=512

# Application parameters. Add parameters as needed starting from 1

# The first application parameter is the name of the class whose main

# method is to be called when the application is launched. The class

# name is followed by the number of parameters to be passed to its main

# method. Then comes the actual parameters.

wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap

#wrapper.app.parameter.1=net.covalent.tomcat.wrapper.ThreadDumpWrapper

wrapper.app.parameter.2=1

wrapper.app.parameter.3=start

# The start parameters are followed by the name of the class whose main

# method is to be called to stop the application. The stop class name

# is followed by a flag which controls whether or not the Wrapper should

# wait for all non daemon threads to complete before exiting the JVM.

# The flag is followed by the number of parameters to be passed to the

# stop class's main method. Finally comes the actual parameters.

wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap

#wrapper.app.parameter.4=net.covalent.tomcat.wrapper.ThreadDumpWrapper

wrapper.app.parameter.5=true

wrapper.app.parameter.6=1

wrapper.app.parameter.7=stop

wrapper.request_thread_dump_on_failed_jvm_exit=TRUE

#********************************************************************

# Wrapper Logging Properties

#********************************************************************

# Format of output for the console. (See docs for formats)

wrapper.console.format=PM

# Log Level for console output. (See docs for log levels)

wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.

wrapper.logfile=../logs/wrapper.log

# Format of output for the log file. (See docs for formats)

wrapper.logfile.format=LPTM

# Log Level for log file output. (See docs for log levels)

wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before

# the log is rolled. Size is specified in bytes. The default value

# of 0, disables log rolling. May abbreviate with the 'k' (kb) or

# 'm' (mb) suffix. For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old

# files are deleted. The default value of 0 implies no limit.

wrapper.logfile.maxfiles=0

# Log Level for sys/event log output. (See docs for log levels)

wrapper.syslog.loglevel=NONE

#********************************************************************

# Wrapper Windows Properties

#********************************************************************

# Title to use when running as a console

wrapper.console.title=@app.long.name

#********************************************************************

# Wrapper Windows NT/2000/XP Service Properties

#********************************************************************

# WARNING - Do not modify any of these properties when an application

# using this configuration file has been installed as a service.

# Please uninstall the service before modifying this section. The

# service can then be reinstalled.

# Service dependencies. Add dependencies as needed starting from 1

wrapper.ntservice.dependency.1=

# Mode in which the service is installed. AUTO_START or DEMAND_START

wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.

wrapper.ntservice.interactive=false

wrapper.ntservice.name=Tomcat

wrapper.ntservice.displayname=Tomcat Application Server

wrapper.ntservice.description=Tomcat Application Server

wrapper.debug=true

Thanks,

Ranjani.A

carlosanchez-g2dHi

Hi Ranjaswin,

I'd say you're missing the bam.properties in some way like

But I haven't configured wrapper so it's just a guess. Look pg 34 in the deploy guide.

wrapper.java.additional.11="-Dbam.properties=/home/dmadmin/APPSERVER/APPHOST/bam/bam.properties"

aviv1

Hi Ahson,

On starting up the Bam-server with url http://localhost:6080/bam-server

Its giving windows Spring security pop-up(as in screen shot) asking for User name and Password any modification is recommended in Spring-security.xml in terms of authentication-manager guide on username and password What it looks like? Kindly suggest how to get rid of this popup.

Windows popup.bmp

aviv1

Hi Carlos,

Thanks indeed for the replay tha was very helpful.

I was wondering could you help me out resolving this one as well

On starting up the Bam-server with url http://localhost:6080/bam-server

Its giving windows Spring security pop-up asking for User name and Password any modification is recommended in Spring-security.xml in terms of authentication-manager guide on username and password What it looks like? Kindly suggest how to get rid of this popup.

Scree shot of pop-up

Windows popup.bmp

Chrisjen

Hi - the spring authentication is configured to use "documentumAuthenticationProvider"

so you login using a valid repository ID & Password

antey

Hello, everyone!

I tried to install xCP 2.0 and faced to some problems during BAM deployment.

I completed instructins and started Tomcat7 service and got this error:

[15:23:13] ERROR [BamContextLoaderListener] ##### BAM startup failed #####

org.springframework.beans.factory.BeanInitializationException: Could not load properties; nested exception is java.io.FileNotFoundException: class path resource [dfc.properties] cannot be opened because it does not exist

......

Caused by: java.io.FileNotFoundException: class path resource [dfc.properties] cannot be opened because it does not exist

What can cause the error?

And also I have a question about wrapper.conf. Do I need to create it, if I use Tomcat 7 as an application server? And what should this file contain?

manikhambire

Hi,

We have set up the environment successfully, however when I try to deploy the application from xCPDesigner it fails.

I think there is error in URL used for deployment by manager.

Please find attached runapp.log

Error looks like this:

[INFO]The tcserver manager URL is http://WSV000909:8080/manager/text
[INFO] The tapp-TestApp-1.0.0.war is deploying.
[INFO] Connecting to:http://WSV000909:8080/manager/text/deploy
[INFO] Unable to connect to app server using URL:http://WSV000909:8080/manager/text/deploy http response code:404
[INFO] Connection to:http://WSV000909:8080/manager/text/deploy was false
[ERROR] Error deploying to application server, app not deployed

[ERROR] java.lang.Exception

[ERROR] at internal.com.emc.xcp.builder.deployment.deployers.WarDeployer.deploy(WarDeployer.java:115)

[ERROR] at com.emc.xcp.builder.deployment.AppDeploymentManager.runDeployPhase(AppDeploymentManager.java:164)

[ERROR] at com.emc.xcp.builder.deployment.AppDeploymentManager.deployApp(AppDeploymentManager.java:110)

[ERROR] at com.emc.xms.commands.ApplicationDeploymentCommand.deploy(ApplicationDeploymentCommand.java:328)

[ERROR] at com.emc.xms.commands.ApplicationDeploymentCommand.execute(ApplicationDeploymentCommand.java:223)

[ERROR] at com.emc.xms.execution.impl.ExecutionService$CommandExecutionTask.run(ExecutionService.java:295)

[ERROR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

[ERROR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

[ERROR] at java.lang.Thread.run(Thread.java:662)

Thanks

Dinakar_Sundar

Hi carlos,

I am also facing the Same problem , I am using Vfabric tc server , Please find my wrapper.conf file contents below,please help on this.

#********************************************************************
# Wrapper Properties
#********************************************************************
#set.CATALINA_HOME=..\..
set.CATALINA_HOME=E:\opt\vmware\vfabric-tc-server-standard-2.8.2.RELEASE\tomcat-7.0.35.B.RELEASE
#set.CATALINA_BASE=..\..
set.CATALINA_BASE=E:\opt\vmware\vfabric-tc-server-standard-2.8.2.RELEASE\tcserver1

# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

# Java Home
set.JAVA_HOME=C:\Program Files (x86)\Java\jdk1.6.0_17

# Java Additional Parameters
wrapper.java.additional.1="-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed"
wrapper.java.additional.2="-Dcatalina.base=%CATALINA_BASE%"
wrapper.java.additional.3="-Dcatalina.home=%CATALINA_HOME%"
wrapper.java.additional.4="-Djava.io.tmpdir=%CATALINA_BASE%\temp"
wrapper.java.additional.5="-Djava.util.logging.manager=com.springsource.tcserver.serviceability.logging.TcServerLogManager"
wrapper.java.additional.6="-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties"
wrapper.java.additional.7="-Dwrapper.dump.port=-1"
# commented By dinakar on 20 march 2013 beg
#wrapper.java.additional.8="-Xmx512M"
#wrapper.java.additional.9="-Xss256K"
# commented By dinakar on 20 march 2013 end

# Added by Dinakar on 20 march 2013 beg
wrapper.java.additional.8="-Xmx1024M"
wrapper.java.additional.9="-Xss512K"
wrapper.java.additional.10="-XX:MaxPermSize=512m"
# Added by Dinakar on 20 march 2013 end

# Java Library Path
wrapper.java.library.path.1=%CATALINA_BASE%\bin\win32
wrapper.java.library.path.2=C:\Program Files (x86)\Java\jdk1.6.0_17\lib\tools.jar
wrapper.java.library.path.3=%CATALINA_BASE%\lib\*.jar
# Java Classpath

wrapper.java.classpath.1=%CATALINA_BASE%\bin\win32\wrapper.jar
wrapper.java.classpath.2=%CATALINA_BASE%\bin\win32\threaddumpwrapper.jar
wrapper.java.classpath.3=%CATALINA_HOME%\bin\bootstrap.jar
wrapper.java.classpath.4=%CATALINA_HOME%\bin\tomcat-juli.jar
wrapper.java.classpath.5=%CATALINA_HOME%\*.jar
#Added By dinakar 0n 20 March 2013 Beg
wrapper.java.classpath.6=E:\opt\vmware\vfabric-tc-server-standard-2.8.2.RELEASE\tcserver1\Customconf\
#Added By dinakar 0n 20 March 2013 Beg

# Java Application
wrapper.java.command=%JAVA_HOME%\bin\java

# Application parameters. Add parameters as needed starting from 1
# The first application parameter is the name of the class whose main
# method is to be called when the application is launched. The class
# name is followed by the number of parameters to be passed to its main
# method. Then comes the actual parameters.
#wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
wrapper.app.parameter.1=net.covalent.tomcat.wrapper.ThreadDumpWrapper
wrapper.app.parameter.2=start

wrapper.cpu.timeout=5
wrapper.shutdown.timeout=60
wrapper.jvm_exit.timeout=60

wrapper.request_thread_dump_on_failed_jvm_exit=TRUE

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM

# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=%CATALINA_BASE%\logs\wrapper.log

# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=%CATALINA_BASE%

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.

# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

#wrapper.ntservice.id is set in the tcruntime-ctl.bat script
wrapper.ntservice.name=%wrapper.ntservice.id%
wrapper.ntservice.displayname=VMware vFabric tc Runtime instance - %wrapper.ntservice.id%
wrapper.ntservice.description=VMware vFabric tc Runtime instance at %wrapper.ntservice.id%

jtrellest

Add the path to the dfc.properties in Customconf in the common.loader or shared.loader in catalina.properties.

e.g. shared.loader=${catalina.base}/Customconf

Tomcat seems to not read the system classpath.

amit_kulkarni11

HI Ahson

I complete with all components installation which are required for xCP. When I am starting with new application in XCP. I am getting following errors.

==================================================

2013-10-21T15:38:25.951 INFO [TStart Level Event Dispatcher] [internal.com.emc.xcp.builder.workspace.Activator:213] Setting maven context root [C:\xCPDesigner]

2013-10-21T15:38:32.950 ERROR [TStart Level Event Dispatcher] [internal.com.emc.xcp.builder.workspace.Activator:180] Failed to refresh workspace

org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system.

at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923)

at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904)

at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951)

at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897)

at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1663)

at internal.com.emc.xcp.builder.workspace.Activator.scanOpenedProjects(Activator.java:178)

at internal.com.emc.xcp.builder.workspace.Activator.start(Activator.java:130)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)

at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

Contains: Exception occurred while synchronizing node: /project/NewApp/org.maven.ide.eclipse.

org.osgi.service.prefs.BackingStoreException: Exception loading preferences from: /NewApp/.settings/org.maven.ide.eclipse.prefs.

at org.eclipse.core.internal.resources.ProjectPreferences.loadProperties(ProjectPreferences.java:172)

at org.eclipse.core.internal.resources.ProjectPreferences.read(ProjectPreferences.java:195)

at org.eclipse.core.internal.resources.ProjectPreferences.updatePreferences(ProjectPreferences.java:274)

at org.eclipse.core.internal.resources.File.updateMetadataFiles(File.java:410)

at org.eclipse.core.internal.localstore.RefreshLocalVisitor.visit(RefreshLocalVisitor.java:309)

at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:110)

at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:920)