Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

How do I upgrade from ES2 to ES4?

sashmore
Level 2
Level 2

I have a functioning ES2 development environment that I want to upgrade to ES4.  I am also moving to a new server (Windows 2008 R2 and SQL 2008 R2).

Currently, I'm running:

JBoss [EAP] 4.2.0.GA_CP01

MS SQL 2005

Java 1.6.0-14

I've read some docs, but am still confused.  I'm assuming out-of-place upgrade, but should I try to Upgrade from ES2 or just do a fresh install then copy GDS and database over?  Also, what configuration files can I copy over (if any)?

Any recommendations or links would be appreciated.

Thanks in advance.

1 Accepted Solution
Hina_Rastogi
Correct answer by
Level 3
Level 3

Hi,

Depending upon the supported application server, database and JDK versions in LiveCycle ES4 you can decide how you want to upgrade.

The link @ http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html lists all the supported versions of application server, database and JDK.

Once you have decided on your target environment, you might choose to stay on the same machine or move to a different machine. In both these cases your upgrade will be out-of-place since JBoss 4.2.0 is not supported in LiveCycle ES4.

If you decide to stay on the same machine, LiveCycle ES4 Installer and LCM would detect the presence of your existing LiveCycle ES2 installation and will guide you accordinly.

However, if you decide to move to another machine you might have to copy the following over to the new machine:

1) Global Document Storage (GDS) directory and it's contents

2) Content Storage (lccs_data) directory and it's contents if you are using Content Services

3) Watched Folder contents

4) Any custom fonts

5) Any other custom files/folders specific to your LiveCycle ES2 installation

You can go through the http://help.adobe.com/en_US/livecycle/11.0/UpgradeChecklist, http://help.adobe.com/en_US/livecycle/11.0/PrepareUpgrad and http://help.adobe.com/en_US/livecycle/11.0/UpgradeJBoss for reference.

Thanks,

Hina Rastogi

View solution in original post

10 Replies
Hina_Rastogi
Correct answer by
Level 3
Level 3

Hi,

Depending upon the supported application server, database and JDK versions in LiveCycle ES4 you can decide how you want to upgrade.

The link @ http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html lists all the supported versions of application server, database and JDK.

Once you have decided on your target environment, you might choose to stay on the same machine or move to a different machine. In both these cases your upgrade will be out-of-place since JBoss 4.2.0 is not supported in LiveCycle ES4.

If you decide to stay on the same machine, LiveCycle ES4 Installer and LCM would detect the presence of your existing LiveCycle ES2 installation and will guide you accordinly.

However, if you decide to move to another machine you might have to copy the following over to the new machine:

1) Global Document Storage (GDS) directory and it's contents

2) Content Storage (lccs_data) directory and it's contents if you are using Content Services

3) Watched Folder contents

4) Any custom fonts

5) Any other custom files/folders specific to your LiveCycle ES2 installation

You can go through the http://help.adobe.com/en_US/livecycle/11.0/UpgradeChecklist, http://help.adobe.com/en_US/livecycle/11.0/PrepareUpgrad and http://help.adobe.com/en_US/livecycle/11.0/UpgradeJBoss for reference.

Thanks,

Hina Rastogi

View solution in original post

sashmore
Level 2
Level 2

Thanks for your reply and instructions.  I will try them today and respond.

Thanks

sashmore
Level 2
Level 2

So far, no good:

I'm getting:

2013-05-13 16:18:24,283 ERROR [com.adobe.service.DataManagerService] (main) ALC-BMC-001-001: Unexpected exception while obtaining home interfaces

javax.naming.NameNotFoundException: com not bound

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

          at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

          at org.jnp.server.NamingServer.lookup(NamingServer.java:396)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)

          at javax.naming.InitialContext.lookup(InitialContext.java:392)

          at com.adobe.service.DataManagerService.onStartService1(DataManagerService.java:117)

          at com.adobe.service.DataManagerService.onStartService(DataManagerService.java:81)

          at com.adobe.service.Service.start(Service.java:145)

          at com.adobe.service.Service.initialize(Service.java:479)

          at com.adobe.service.ServerLifeCycleListener.contextInitialized(ServerLifeCycleListener.java:31)

          at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)

          at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)

          at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)

          at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)

          at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)

          at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)

          at org.jboss.web.deployers.WebModule.start(WebModule.java:97)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:597)

          at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

          at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

          at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

          at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

          at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)

          at $Proxy38.start(Unknown Source)

          at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)

          at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)

          at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)

          at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)

          at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

          at org.jboss.system.ServiceController.doChange(ServiceController.java:688)

          at org.jboss.system.ServiceController.start(ServiceController.java:460)

          at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)

          at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)

          at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)

          at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

          at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

          at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

          at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)

          at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

          at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

          at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

          at org.jboss.Main.boot(Main.java:221)

          at org.jboss.Main$1.run(Main.java:556)

          at java.lang.Thread.run(Thread.java:662)

2013-05-13 16:18:24,294 WARN  [com.adobe.csa.config.CoreConfigManager] (main) Could not obtain Core Preferences

2013-05-13 16:18:24,294 ERROR [com.adobe.idp.config.AdobePreferenceFactory] (Thread-19) UserM:GENERIC_ERROR: [Thread Hashcode: 1946166549] Problem with system rootjavax.naming.NameNotFoundException: com.adobe.idp.config.PreferencesSPIHome not bound

to start with, and  a few more, but I think they are related.

Is there a JNDI definition for COM and ADOBE??

Thanks

Hina_Rastogi
Level 3
Level 3

What environment did you select for you target LiveCycle ES4 environment?

Also, is your application server starting up fine if no EARs are deployed to it?

Please check that both the JBoss servers are not running while you are running the upgrade to ES4.

Thanks,

Hina Rastogi

sashmore
Level 2
Level 2

I'll be running:

Windows Server 2008 R2 Standard 64-bit

SQL Server 2008 R2

Java 6u31 64bit

Jboss-5.1.0.GA

The old server is disconnected. 

I'm fairly certain that it was running fine before deploying.  I will un-deploy and see what happens.

Thanks!

sashmore
Level 2
Level 2

Seems that I messed up my mssql-ds.xml file.  I goofed then DefaultDS section with a typo.  This led to a JDBC driver update. 

Foundationally, everything looks good now.  I'm going to re-deploy.

Thanks

sashmore
Level 2
Level 2

Success!!!  Everything seems to be working fine.  Thanks for the direction!

rajeshb97082039
Level 1
Level 1

Hi, I am planning for Out of box upgrade and have the same situation here.

My new System would be ;

Windows Server 2008 R2 Standard 64-bit

SQL Server 2008 R2

Java 6u31 64bit

Jboss-5.1.0.GA

Need calrification before I proceed,

1. Shall I copy all the resources first and then start the ES4 installation?

2. Shall I stop the old System and also the New System Jboss Server before insalling ES4?

3. At what stage War File and Ear file will be deployed?

Thanks for your support.

rajeshb97082039
Level 1
Level 1

Hi,

Can you please guide me the sequesnce you ahd followed for out of box upgrade?

Will copying the resources to new Machine be done prior of ES4 installation?

Please let me know the sequesnce.

Thanks,

raj

RoboAsh
Level 1
Level 1

Already answered by hina, I am just re-pasting that

Depending upon the supported application server, database and JDK versions in LiveCycle ES4 you can decide how you want to upgrade.

The link @ http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html lists all the supported versions of application server, database and JDK.

for ES SP1 LiveCycle Help | What's New in LiveCycle ES4 Service Pack 1

Once you have decided on your target environment, you might choose to stay on the same machine or move to a different machine. In both these cases your upgrade will be out-of-place since JBoss 4.2.0 is not supported in LiveCycle ES4.

If you decide to stay on the same machine, LiveCycle ES4 SP1 Installer and LCM would detect the presence of your existing LiveCycle ES2 installation and will guide you accordinly.

However, if you decide to move to another machine you might have to copy the following over to the new machine:

1) Global Document Storage (GDS) directory and it's contents

2) Content Storage (lccs_data) directory and it's contents if you are using Content Services

3) Watched Folder contents

4) Any custom fonts

5) Any other custom files/folders specific to your LiveCycle ES2 installation

Please note ES4 SP1 has Jboss 5.2 please use that with JDK 7 for upgrade

You can go through the http://help.adobe.com/en_US/livecycle/11.0/UpgradeChecklist, http://help.adobe.com/en_US/livecycle/11.0/PrepareUpgrad and http://help.adobe.com/en_US/livecycle/11.0/UpgradeJBoss for reference.