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; } } }

Adding new target node

mart2001

Hi,

Is there a well define document that list the steps needed to add a new target node?

Thanks,

Find more posts tagged with

Comments

nipper

Sure. Read the SP Developers manual. It is in one of the appendixes.

If you run TS 721 then you must load the patch associated with it & the patch is for TS as well as the runtime LSDS/LSCS servers as well.

mart2001

1. Install additional runtime instances. (Done)
2. Add OpenDeploy deployment target (Done)
a. Open od-home/etc/odnodes.xml
b. Add for new runtime instane
c. Save file
d. Open iw-home/local/config/lib/content--center/ livesite_customer_src/etc/livesite_customer/resources/customer-teamsite-resource-config.xml file. (Which does not exist, do they ever proofread their documentation?).
Had to look in iw-home\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\resources to actually find the file.
e. Add an extensible bean reference for the DeploymentTarget map. Ensure that LiveSiteProduction2 (see below) matches LiveSiteProduction2 in the odnodes.xml. Similarly, ensure that production2 matches livesite-production2 in livesite-database.xml file and production2 in the custom_instantiation.cfg file. (Updated livesite-database.xml in od-home/etc/livesite-database.xml), (Updated custom_instantiation.cfg in iwadmin store to include the new node). (Added new “entry key” for new node, and added property name=”targetNode” to the customer-teamsite-resource-config.xml file.)
f. Ran build.bat and it updated successfully. Restarted OD on both server.
g. When testing deployment, it said deployment completed successfully. But checking on the destination, the files were not deployed. Am I missing something?

Thanks

nipper

What Version of TS ?

What do your logs say ?

Are you using LSCS ?

Rick Poulin

iw-home/local/config/lib/content--center/ livesite_customer_src/etc/livesite_customer/resources/customer-teamsite-resource-config.xml file. (Which does not exist, do they ever proofread their documentation?).

This file should be there in TS7.2+ except
iw-home/local/config/lib/content-center/livesite_customer_src/etc/conf/livesite_customer/resources/customer-teamsite-resource-config.xml

Adam Stoller

e. [...] Similarly, ensure that production2 matches livesite-production2 in livesite-database.xml file and production2 in the custom_instantiation.cfg file. ([...]), (Updated custom_instantiation.cfg in iwadmin store to include the new node). ([...])

Did you also modify the Script Variable within the WFM to reference the new targetNode?

mart2001

TS 7.3.1

Couldn't find the logs that does the deployment.

Yes, using LSCS.

What Version of TS ?

What do your logs say ?

Are you using LSCS ?

mart2001

Yes, you need the conf directory in there. Wish iwov would of proofread their documents before publishing it.

This file should be there in TS7.2+ except
iw-home/local/config/lib/content-center/livesite_customer_src/etc/conf/livesite_customer/resources/customer-teamsite-resource-config.xml

mart2001

No, didn't see any documents that says to modify the variable. Still waiting to find a time to run build.bat again.

Did you also modify the Script Variable within the WFM to reference the new targetNode?

nipper

No, didn't see any documents that says to modify the variable. Still waiting to find a time to run build.bat again.

That may be necessary, the SP Admin doc talks about it. Edit the TargetNodes script variable to include the new target. This is required if you are doing something like adding Staging in between Dev & Prod.

mart2001

According to the Site Developer Guide, it looks like I have to add an entry key for the new node in customer-teamsite-resource-config.xml. I added a new entry key for new target. In the same document, it mention to modify custom_instantiation.cfg which I did to include the new target. Then restarted both base and receiver od servers. Still no dice... Is this SP Admin doc different than the Site Developer Guide?

Thanks

That may be necessary, the SP Admin doc talks about it. Edit the TargetNodes script variable to include the new target. This is required if you are doing something like adding Staging in between Dev & Prod.

nipper

According to the Site Developer Guide, it looks like I have to add an entry key for the new node in customer-teamsite-resource-config.xml. I added a new entry key for new target. In the same document, it mention to modify custom_instantiation.cfg which I did to include the new target. Then restarted both base and receiver od servers. Still no dice... Is this SP Admin doc different than the Site Developer Guide?

Thanks

Sorry mean Developers guide, not admin

If you are using LSCS you need to change this file:

LiveSiteCSAuth/authoring/etc/deployment/config/lscs-authoring.xml

Add a new node for your new target (staging)

mart2001

Thanks

I was looking through this kb article:
https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/60255.html

It seems the Developer Guide left out this step:

7. Click on Workflow Model in the upper-left frame, then in the lower-left frame, click on Global Variables

8. Scroll down and select SCRIPT(DeployFilesTargetNodes) and click the Edit button.

You should see something like this:

"development" +
(
/** if production is true and there's no review, all in one step! */
( "$IW_CV(ProductionFlag)" == "true"
&& "$IW_CV(ReviewFlag)" == "false" )
? ",production"
: ""
);

Change this to the following snippet:

"development" +
(
/** if not development and there's no review, all in one step! */
( "$IW_CV(TargetNodes)" != "development"
&& "$IW_CV(ReviewFlag)" == "false" )
? ("," + "$IW_CV(TargetNodes)" )
: ""
);

After completing that step, at least I am getting an error about the new target not being in lscs-authoring.xml. Hopefully, I will be able to deploy to the new target node after this.

Thanks!

Sorry mean Developers guide, not admin

If you are using LSCS you need to change this file:

LiveSiteCSAuth/authoring/etc/deployment/config/lscs-authoring.xml

Add a new node for your new target (staging)

mart2001

Ok, so I added the node to the lscs-authoring.xml file.

But I am getting this error in lscs.log:

04-16-13 @ 11:56:53 [ERROR] MainController - error.no_such_resource
com.interwoven.wcm.iwrr.core.UnsupportedResourceException: util-command/pending-context/project///TEAMSITE/default/main/branch1/sub-branch1/

And in the OD log, I am getting this:
2013-04-16 11:56:53,735 ERROR Exception in import delivery adapter execution
java.io.FileNotFoundException: http://localhost:8080/lscs/v1/util-command/pending-context/project///TEAMSITE/default/main/branch1/sub-branch1/?format=json

Tried to run the curl command which did not help.

Tried the following link:
http://localhost:8080/lscs/v1/admin/status
takes awhile, but eventually shows that the TeamSite Repository as being up.

Tried the following link:
http://localhost:8080/lscs/admin/debugpanel/
does bring up the debugpanel

Tried the following link:
http://localhost:8080/lscs/v1/projects
gives a 404.