nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployment to multiple LSCS servers using PLC workflow

TeamsiteDev

Hi,

I am using PLC workflow to deploy content to Livesite & LSCS. Right now I have one LSCS server & 3 livesite riuntime. I have configured the node name "uat" in customer-teamsite-resource-config.xml . I have defined the same node in lscs-authoring.xml as below :

In the deployment descriptors in OD_HOME/conf/lscs , I have added the LSCS servers uat1.domain.com in replication farm.

This works fine, I select UAT from workflow instantiation screen which point to uat node in customer-teamsite-resource-config.xml & deployemnt works fine for livesite runtime & LSCS.

Now I want to add one more LSCS server uat2.domain.com into UAT deployment. MySql Database for Both LSCS servers is same as defined in lscs-conf.properties. To deploy content in new server , I added the server in LSCS replication farm in commit-deploy-pl.xml , teamsite-areadiff.xml & rollback.xml. But deployment to new LSCS server is failing. The import task is failing. Also when deployment starts for uat2.domain.com , the import URL is that of uat1.domain.com , which I think comes from lscs-authoring.xml. Even if I use only the new LSCS server uat2 in replication farms & lscs-authoring.xml , still deployment is failing . Below is the error in deployment log :

2014-06-17 07:18:04,508 DEBUG Start connecting to LSCS runtime server ...
2014-06-17 07:18:06,033 INFO {"contexts":[]}
2014-06-17 07:18:06,033 INFO No pending context found.
2014-06-17 07:18:06,033 DEBUG Request method = POST
2014-06-17 07:18:06,033 DEBUG data=manifestURL=FILE%3A%2F%2Flocalhost%2F%2Fopt%2Fwebhost%2Fwebdev%2FInterwoven%2FLSCSRT-Store%2F11b%2Ffe5%2F11bfe5c47e10d9765
8af8879baf4b676%2Fmanifest%2Flscs_manifest.xml
2014-06-17 07:18:06,033 DEBUG url=http://uat2.domain.com:1876/lscs/v1/import/
2014-06-17 07:18:06,033 INFO ODHOME = /opt/webhost/webdev/Interwoven/OpenDeployNG
2014-06-17 07:18:06,033 DEBUG Start connecting to LSCS runtime server ...
2014-06-17 07:18:08,794 ERROR Exception in import delivery adapter execution
java.io.IOException: Server returned HTTP response code: 500 for URL: http://uat2.domain.com:1876/lscs/v1/import/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1290)
at com.interwoven.wcm.iwrr.deployment.adapter.delivery.LSCSDeliveryAdapterBase.processRequest(LSCSDeliveryAdapterBase.java:309)
at com.interwoven.wcm.iwrr.deployment.adapter.delivery.ImportDeliveryAdapter.deploy(ImportDeliveryAdapter.java:126)
at com.interwoven.deploy.engine.TMicroDeployRx.invokeDeliveryAdapters(TMicroDeployRx.java:3769)
at com.interwoven.deploy.engine.TMicroDeployRx.commit(TMicroDeployRx.java:2487)
at com.interwoven.deploy.engine.TMicroDeployRx.run(TMicroDeployRx.java:1363)
at java.lang.Thread.run(Thread.java:619)

Since the new LSCS server points to same old database , it shows all the projects which are deployed on uat1 in this query http://uat2.domain.com:1876/lscs/v1/projects. But content related queries give error, since there is no content in LSCS-Store.

Please can somebody suggest how I can achieve deployment to multiple LSCS servers in same job.

Teamsite 741 on Windows

LSCS 732 on Linux

LSDS 732 on Linux

Thanks!

Regards,

Ankit

Find more posts tagged with

Comments

Rick Poulin

LSDS/LSCS are really designed to work in pairs. This would be a lot simpler if you had 3 LSCS instances, each hosted on its LSDS server.

The way you've got it now can potentially work, but you're not making it easy for yourself. You'll probably have to do some work on the OD configs -- AFAIK your infrastructure design can't be accommodated with just ootb configuration. The Sitepub dev guide contains (at least the 7.2 version) some detail of how you could potentially modify the odadapter to add an additional LSCS node, but that approach doesn't scale, nor does it replicate easily to other environments.

nipper

Another (much more complex) option is to decouple the LSCS and LSDS deployments. I have done that before and you have a lot more granularity. You can use the LSCS deployment (think startdeploy.sh) and then manually push the LSDS content out (and also generate the cache file and push it).

TeamsiteDev

Thanks Andy & Rick for your replies. I just found this in LSCS Technical refereence guide :

Adding an LSCS instance
To add another LSCS instance to a farm of LSCS instances, perform the
following:
1. Make sure that no deployments take place while the steps are being
performed to add an LSCS instance to an LSCS farm.
2. Install the relevant LSCS software on the new LSCS instance.
3. Make sure that the IDOL instance (iwlscscontent service/daemon) is
shut down on the new LSCS instance.
4. Make sure that the LSCS Web application is shut down on the new LSCS
instance.
5. Stop the IDOL instance in a working LSCS instance before copying the
contents of IDOL (except IWLSCSContent.cfg) from a working LSCS
instance to the new LSCS instance.
6. Copy all the files/folders in the location pointed to by the content.root
property in the lscs-conf.properties configuration file of a working
LSCS instance in the farm to the location pointed to by the content.root
property in the lscs-conf.properties configuration file of the new LSCS
instance.
7. Using standard database tools (or other similar mechanisms), export all the
content in the database tables pointed to by the datasource.url property
in the lscs-conf.properties configuration file of a working LSCS
instance in the farm to the location pointed to by the datasource.url
property in the lscs-conf.properties configuration file of the new LSCS
instance.
8. Copy all the files/folders in the location <LSCS_HOME>/idol of a working
LSCS instance in the farm to the corresponding location of the new LSCS
instance (make sure that the file IWLSCSContent.cfg is not copied).
9. Change all the deployment configurations so that this new LSCS instance is
also included for subsequent deployments.
10. Start the IDOL instance (iwlscscontent service/daemon) on the new
LSCS instance.
11. Start the LSCS Web application on the new LSCS instance.

Has anybody tried these steps ?

Rick ,

You say that having 3 LSCS servers would have been easy . how do we deploy to each LSCS in that case ? For Every node in customer-teamsite-resource-config.xml, we can have only one <runtime> tag in lscs-authoring.xml , so how do we get different import URLs for each LSCS server ?

Thanks !

Rick Poulin

leoankitfid wrote:
Has anybody tried these steps ?

Rick ,
You say that having 3 LSCS servers would have been easy . how do we deploy to each LSCS in that case ? For Every node in customer-teamsite-resource-config.xml, we can have only one <runtime> tag in lscs-authoring.xml , so how do we get different import URLs for each LSCS server ?

Thanks !

Those steps are for cloning an existing LSCS instance. It doesn't say anything about deploying content into it after the fact.

It's easier because then you can change your ODconf to deploy to a replication farm rather than individual targets in a loop. You set your lscs-authoring.xml to say the LSCS runtime in on "localhost" (which is relative to the target ODrcvr) and voila, it just works and scales to any number of runtimes -- all you need to do when adding a new runtime instance is update your replication farm definition in odnodes.xml.

TeamsiteDev

Hi Rick,

I tried using "localhost" in <runtime> tag & deployment did work. Thanks for that .

Before deploying to multiple servers I have to first fix deployment to the new LSCS server. When I try to deploy only to new server , I am getting 500 error on the import URL . lscs.log error is as below :

[ERROR] MainController - error.internal_server
java.lang.RuntimeException: com.interwoven.wcm.iwrr.core.SearchSrvException: Failed to index content : -4
at com.interwoven.wcm.iwrr.request.handler.ImportRequestHandler.handlePut(ImportRequestHandler.java:154)
at com.interwoven.wcm.iwrr.request.handler.ImportRequestHandler.handlePost(ImportRequestHandler.java:88)
at com.interwoven.wcm.iwrr.core.MainController.handleRequestInternal(MainController.java:208)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at com.interwoven.wcm.iwrr.diagnostic.DiagnosticLogger.timingAdvice(DiagnosticLogger.java:118)
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.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy7.handleRequest(Unknown Source)
at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.interwoven.wcm.iwrr.admin.AdminFilter.doFilter(AdminFilter.java:142)
at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.interwoven.wcm.iwrr.core.SearchSrvException: Failed to index content : -4
at com.interwoven.wcm.iwrr.dao.idol.IdolSearchDaoRuntimeImpl.waitForIndexer(IdolSearchDaoRuntimeImpl.java:751)
at com.interwoven.wcm.iwrr.dao.idol.IdolSearchDaoRuntimeImpl.handleDbSync(IdolSearchDaoRuntimeImpl.java:699)
at com.interwoven.wcm.iwrr.dao.idol.IdolSearchDaoRuntimeImpl.indexContent(IdolSearchDaoRuntimeImpl.java:369)
at com.interwoven.wcm.iwrr.request.handler.ImportRequestHandler$ManifestHandler.uploadIDX(ImportRequestHandler.java:665)
at com.interwoven.wcm.iwrr.request.handler.ImportRequestHandler$ManifestHandler.endDocument(ImportRequestHandler.java:638)
at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.interwoven.wcm.iwrr.request.handler.ImportRequestHandler.handlePut(ImportRequestHandler.java:127)
... 47 more

Seems idol not functioning properly on the new server. Any advice on that ?

Thanks!

nipper

500 error on the import is kind of a catch all.

Look at the idol logs, Interwoven/LiveSiteCSRT/idol/logs/

Probably the index.log, but see what gets updated.

Rick Poulin

REMOVED because same reply as nipper, who beat me to it by 17 seconds.

TeamsiteDev

Below is the error in logs :

index.log
19/06/2014 09:00:27 [0] Index connection granted to: 127.0.0.1
19/06/2014 09:00:27 [0] Index Queue Command: /DREDELDBASE?DREDbName=1360331220
19/06/2014 09:00:27 [1] Index Queue Command: DREDELDBASE?DREDbName=1360331220
19/06/2014 09:00:27 [1] Warning: DREDELDBASE database not found.
19/06/2014 09:00:27 [1] Index command finished. Took 0.00 s

application.log
19/06/2014 09:00:26 [16] Error - no databases19/06/2014 09:00:26 [16] Internal errorcode: 0x8000010B Internal error.
19/06/2014 09:00:27 [16] Error - no databases19/06/2014 09:00:27 [16] Internal errorcode: 0x8000010B Internal error.

query.log
19/06/2014 09:00:26 [16] Action=query&FieldText=%28STRING%7Bpage%7D%3ALSCS_STR_TeamSite__HSALS__LiveSite__HSALS__Type%29+AND+MATCH%7BResponsive%7D%3AprojectName+AND+EMPTY%7B%7D%3AisDeleted&Start=1&MaxResults=10&TotalResults=true&weighfieldtext=false&anylanguage=true&Print=Fields&PrintFields=id%2CcontextId&databasematch=1360331220_ (127.0.0.1)
19/06/2014 09:00:26 [16] Errorcode: Query returned error 599 (Unspecified error)
19/06/2014 09:00:26 [16] Query complete
19/06/2014 09:00:27 [16] Action=query&FieldText=GREATER%7B1403193143%7D%3AcontextDeployedDate&TotalResults=true&anylanguage=true&Print=noresults&Predict=false&databasematch=1360331220 (127.0.0.1)
19/06/2014 09:00:27 [16] Errorcode: Query returned error 599 (Unspecified error)
19/06/2014 09:00:27 [16] Query complete

I checked in IWLSCSContent.cfg, there are no IDOL Dbs defined under [DATABASES] .

I didn't create any IDOL DB manually on the old LSCS , I think it was created via deployment.

Thanks!

TeamsiteDev

The new LSCS server shares the MySQL DB with the old one. The new server was never used, it had LSCS 7.3.1 earlier, before attempting deployment I upgraded it to 732 as my Teamsite is 741

nipper

OK, that makes zero sense.

So this is a new server ?

How do you mean it "shares" the DB with the other server ? While that can be done, you *really* have to know what you are doing.

I would suggest setting up a new DB and use build.sh to populate the tables.

TeamsiteDev

Hi Andy,

I created a separate MySQL database for the new LSCS server & synced the content in LSCS store & IDOL indexes.

As suggested by Rick , in lscs-authoring.xml I added "localhost" in <runtime> tag & then added the new LSCS server node in replicationfarm. Now my deployment is working for both LSCS servers in one workflow job.

Thanks Andy & Rick !