Deploying one site to multiple environments

Aim:
Add pre-production (staging) environment.

I followed all the following procedure:

I - Define target nodes in the workflow model
II - Add DataDeploy configuration to livesite-database.xml for each new DB.
III- Add OD DeploymentTarget for each node that has a filesystem.
IV - Rebuild the toolkit.
V - Configure the workflow in TeamSite Administration

When I try to submit files to the new runtime I get the following error.
Could not invoke method: deployFiles, reason: null

Has anyone added the staging environment successfully?
If YES, please know the procedure.

Thank you advance...

Find more posts tagged with

Comments

nipper

I have done it several times.

The SP developers manual helps, there is a section on adding a runtime node.

That being said there are a bunch of moving parts and it typically takes a lot of digging and debugging.

The error you post provides zero value. There are likely other errors stuck in logs that may help. Start looking.

kaleemS

Thank you for your reply nipper.

I followed the same steps as per "Deploy Multiple Sites to Multiple Runtime Instances" in "SitePublisher Developer Guide".

and there is no error other than : Could not invoke method: deployFiles, reason: null

Could you please share how did you add staging environment?

nipper

Thank you for your reply nipper.

I followed the same steps as per "Deploy Multiple Sites to Multiple Runtime Instances" in "SitePublisher Developer Guide".

and there is no error other than : Could not invoke method: deployFiles, reason: null

Could you please share how did you add staging environment?

There are way too many variable and steps to post here.

There are logs, where did you find that entry? You need to start looking no one here can help with the information you provided. Maybe support can help. Unless you get someone who knows what they are doing with a webex, not much will happen.

kaleemS

There are way too many variable and steps to post here.

There are logs, where did you find that entry? You need to start looking no one here can help with the information you provided. Maybe support can help. Unless you get someone who knows what they are doing with a webex, not much will happen.

Yes, There are too many steps...

Here is my steps.... could you please check... if I am doing anything wrong here.. thank you for your time...

I Define target nodes in workflow model
1. Copy Publish LiveSite Content workflow to a new version e.g. {CustomerName} Publish LiveSite Content, including the following files:

iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/Publish LiveSite Content.ipm

iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Publish LiveSite Content_config ( just copy the whole directory contents )

Example:

iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/Ajuba Publish LiveSite Content.ipm

iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Ajuba Publish LiveSite Content_config

2. Open custom_instantiation.cfg in the newly created "config" directory:
iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Ajuba Publish LiveSite Content_config
3. Locate the {item name="TargetNodes"} ( around line 136 )
4. Add in the new environments as {option}s.
Here's mine for staging.

{item pathid="TargetNodes" name="TargetNodes"}
{label}Target Nodes{/label}
{radio required="t"}
{option label="Development" value="development" selected="t"/}

{option label="Staging" value="staging" selected="t"/}
{option label="Production" value="production"/}
{/radio}
{/item}

5. Save this file and submit it to the STAGING area using either iwsubmit CLT or the standard TS submit workflow.
* The following steps only need to be done once *
6. Using the Workflow Modeler, open the new workflow from TS ( Retrieve from TeamSite )
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)" )
• : ""
• );
•
•
•
9. Click Update button, then Click Ok.
10. Save the model to TeamSite and Publish it. This should submit it to STAGING area, but please make sure it actually does it. Alternatively you can use the iwsubmit CLT to submit the Config and Models directories from the iw-wa workarea.
II Add DataDeploy configuration to livesite-database.xml for each new DB
Only do this step if the environment has a target database.
1. Open odhome/etc/livesite-database.xml and add an entry for each new DB, see example below.
NOTE: Database name *must be* in the format "livesite-{node-name}" e.g. livesite-staging
Here's mine for SQL2005:
{database name="livesite-staging"
db="vm671shanon:1433;database=livesite_staging"
user="livesite"
password="livesite"
vendor = "rdbms"
jdbc-driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
protocol-url="jdbc:sqlserver"
max-id-length = "128"
update-type="standalone"
state-field="state"
commit-batch-size="1"
real-update="yes"
delete-tracker="yes" /}

III Add OD DeploymentTarget for each node that has a filesystem.
Only do this for each target node that has a target filesystem.
1. Open odhome/etc/odnodes.xml
2. Add a {node} for the staging filesystem ( if reusing an existing node, skip this step )
{node name="LiveSiteStagingRuntime"
host="VM671SHANON"
port="20014"
/}

3. Save this file.
NOTE: You must also configure the receiver on the runtime filesystem, specifically the {allowedDirectories}.

4. Open livesite_customer_src/etc/livesite_customer/resources/customer-teamsite-resource-config.xml
5. Add an extensible bean reference for the DeploymentTarget map.
Here's mine for the "staging" environment:
( this {bean} definition goes between the {beans} root node, already present in the file )
{bean id="customer.teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap"
parent="teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap"}

{property name="sourceMap"}
{map merge="true"}
{entry key="staging"}
{list merge="true"}
{bean class="com.interwoven.livesite.deployment.model.DeploymentTarget"}

{!-- define this node mapping in odhome/conf/odnodes.xml --}
{property name="targetNode" value="LiveSiteStagingRuntime"/}
{!-- the absolute path to the web root on the staging filesystem, must be in the allowedDirectories on the receiver --}
{property name="targetDirectory" value="c:/livesite/runtime/web"/}
{!-- define which files should be deployed using this target, defaults to all in the /default store --}

{property name="filterPatterns"}
{bean class="com.interwoven.livesite.common.util.PatternWrapper"
factory-method="createList"}
{constructor-arg}
{list}
{!-- this list of patterns allows everything in the /default branch, or a sub-branch. --}
{value}^(//[^/]+)?/default/.*{/value}
{!--
enter as many value patterns as you like
{value}/default/foo{/value}
--}
{/list}
{/constructor-arg}
{/bean}
{/property}
{/bean}
{/list}
{/entry}
{/map}
{/property}
{/bean}

IV Rebuild the toolkit
1. Open cmd to livesite_customer_src and run build.bat.
2. Stop and start the OpenDeploy service on the base and receiver.

V Configure the workflow in TeamSite Administration
1. Configure the Ajuba Publish LiveSite Content workflow to be used instead of the Publish LiveSite Content workflow where deployment to these new environments is required.

HKN1104

Yes, There are too many steps...

Here is my steps.... could you please check... if I am doing anything wrong here.. thank you for your time...

I Define target nodes in workflow model
1. Copy Publish LiveSite Content workflow to a new version e.g. {CustomerName} Publish LiveSite Content, including the following files:

iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/Publish LiveSite Content.ipm

iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Publish LiveSite Content_config ( just copy the whole directory contents )

Example:

iwadmin/main/workflowModels/WORKAREA/iw-wa/Models/Ajuba Publish LiveSite Content.ipm

iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Ajuba Publish LiveSite Content_config

2. Open custom_instantiation.cfg in the newly created "config" directory:
iwadmin/main/workflowModels/WORKAREA/iw-wa/Config/Ajuba Publish LiveSite Content_config
3. Locate the {item name="TargetNodes"} ( around line 136 )
4. Add in the new environments as {option}s.
Here's mine for staging.

{item pathid="TargetNodes" name="TargetNodes"}
{label}Target Nodes{/label}
{radio required="t"}
{option label="Development" value="development" selected="t"/}

{option label="Staging" value="staging" selected="t"/}
{option label="Production" value="production"/}
{/radio}
{/item}

5. Save this file and submit it to the STAGING area using either iwsubmit CLT or the standard TS submit workflow.
* The following steps only need to be done once *
6. Using the Workflow Modeler, open the new workflow from TS ( Retrieve from TeamSite )
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)" )
• : ""
• );
•
•
•
9. Click Update button, then Click Ok.
10. Save the model to TeamSite and Publish it. This should submit it to STAGING area, but please make sure it actually does it. Alternatively you can use the iwsubmit CLT to submit the Config and Models directories from the iw-wa workarea.
II Add DataDeploy configuration to livesite-database.xml for each new DB
Only do this step if the environment has a target database.
1. Open odhome/etc/livesite-database.xml and add an entry for each new DB, see example below.
NOTE: Database name *must be* in the format "livesite-{node-name}" e.g. livesite-staging
Here's mine for SQL2005:
{database name="livesite-staging"
db="vm671shanon:1433;database=livesite_staging"
user="livesite"
password="livesite"
vendor = "rdbms"
jdbc-driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
protocol-url="jdbc:sqlserver"
max-id-length = "128"
update-type="standalone"
state-field="state"
commit-batch-size="1"
real-update="yes"
delete-tracker="yes" /}

III Add OD DeploymentTarget for each node that has a filesystem.
Only do this for each target node that has a target filesystem.
1. Open odhome/etc/odnodes.xml
2. Add a {node} for the staging filesystem ( if reusing an existing node, skip this step )
{node name="LiveSiteStagingRuntime"
host="VM671SHANON"
port="20014"
/}

3. Save this file.
NOTE: You must also configure the receiver on the runtime filesystem, specifically the {allowedDirectories}.

4. Open livesite_customer_src/etc/livesite_customer/resources/customer-teamsite-resource-config.xml
5. Add an extensible bean reference for the DeploymentTarget map.
Here's mine for the "staging" environment:
( this {bean} definition goes between the {beans} root node, already present in the file )
{bean id="customer.teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap"
parent="teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap"}

{property name="sourceMap"}
{map merge="true"}
{entry key="staging"}
{list merge="true"}
{bean class="com.interwoven.livesite.deployment.model.DeploymentTarget"}

{!-- define this node mapping in odhome/conf/odnodes.xml --}
{property name="targetNode" value="LiveSiteStagingRuntime"/}
{!-- the absolute path to the web root on the staging filesystem, must be in the allowedDirectories on the receiver --}
{property name="targetDirectory" value="c:/livesite/runtime/web"/}
{!-- define which files should be deployed using this target, defaults to all in the /default store --}

{property name="filterPatterns"}
{bean class="com.interwoven.livesite.common.util.PatternWrapper"
factory-method="createList"}
{constructor-arg}
{list}
{!-- this list of patterns allows everything in the /default branch, or a sub-branch. --}
{value}^(//[^/]+)?/default/.*{/value}
{!--
enter as many value patterns as you like
{value}/default/foo{/value}
--}
{/list}
{/constructor-arg}
{/bean}
{/property}
{/bean}
{/list}
{/entry}
{/map}
{/property}
{/bean}

IV Rebuild the toolkit
1. Open cmd to livesite_customer_src and run build.bat.
2. Stop and start the OpenDeploy service on the base and receiver.

V Configure the workflow in TeamSite Administration
1. Configure the Ajuba Publish LiveSite Content workflow to be used instead of the Publish LiveSite Content workflow where deployment to these new environments is required.

Your Staging node is not configured to Deploy.

Livesite-database.xml is set to deploy to db.

When it say Deploy NULL....it was unable to deploy to LSCS. look at lscs-authoring.xml and make necessary changes to deploy to staging server.

Thanks

kaleemS

Your Staging node is not configured to Deploy.

Livesite-database.xml is set to deploy to db.

When it say Deploy NULL....it was unable to deploy to LSCS. look at lscs-authoring.xml and make necessary changes to deploy to staging server.

Thanks

I am adding staging env first time. so, sorry for my questions.

What do you mean by staging node is not configured to deploy, could you please elaborate it? can you upload an example . what it should be?

Can you upload your configured Livesite-database.xml ?

Waiting for your response , thank you.

HKN1104

I am adding staging env first time. so, sorry for my questions.

What do you mean by staging node is not configured to deploy, could you please elaborate it? can you upload an example . what it should be?

Can you upload your configured Livesite-database.xml ?

Waiting for your response , thank you.

In your case, Nothing to do with LiveSite-database.xml. It is correct.

Look for lscs-authoring.xml and make necessary changes.

Thanks

kaleemS

In your case, Nothing to do with LiveSite-database.xml. It is correct.

Look for lscs-authoring.xml and make necessary changes.

Thanks

I have added staging node in lscs-authoring.xml as follow..

{preview lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSAuth-Store" destinationNode="localhost"/{
{production lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSRT-Store" destinationNode="LSCSRuntime"/{
{staging lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSRT-Store" destinationNode="LSCSStagingRuntime"/}

Still showing same error message.

Is above configuration correct?

HKN1104

I have added staging node in lscs-authoring.xml as follow..

{preview lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSAuth-Store" destinationNode="localhost"/{
{production lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSRT-Store" destinationNode="LSCSRuntime"/{
{staging lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="8080" destinationArea="/opt/LSCSRT-Store" destinationNode="LSCSStagingRuntime"/}

Still showing same error message.

Is above configuration correct?

No, It is not correct.

Change your lscsRuntimeHostname from localhost to Staging Node.

Thanks

kaleemS

No, It is not correct.

Change your lscsRuntimeHostname from localhost to Staging Node.

Thanks

Thank you for your quick response...

I can publish to production.
the configuration for production node is on second line . where lscsRuntimeHostname="localhost" and destinationNode="LSCSRuntime".

On the other hand I configured the staging same way,
lscsRuntimeHostname="localhost" and destinationNode="LSCSStagingRuntime"
which was not working.
However, after your input I replaced "localhost" with "LSCSStagingRuntime" in staging node.

But it doesn't make any change and showing the same error message.

Could you please upload configuration file sample?

Thank you in advance.

HKN1104

Thank you for your quick response...

I can publish to production.
the configuration for production node is on second line . where lscsRuntimeHostname="localhost" and destinationNode="LSCSRuntime".

On the other hand I configured the staging same way,
lscsRuntimeHostname="localhost" and destinationNode="LSCSStagingRuntime"
which was not working.
However, after your input I replaced "localhost" with "LSCSStagingRuntime" in staging node.

But it doesn't make any change and showing the same error message.

Could you please upload configuration file sample?

Thank you in advance.

Ok, Please attach odnodes.xml and lscs-authoring.xml

I knew the problem, Please upload those 2 files
Thanks

kaleemS

Ok, Please attach odnodes.xml and lscs-authoring.xml

I knew the problem, Please upload those 2 files
Thanks

Please find the attachment

Thank you

HKN1104

Please find the attachment

Thank you

Change your destination node in lscs-authoring.xml file for staging node to LiveSiteStagingRuntime and restart your od and try deployment.

Thanks

kaleemS

Change your destination node in lscs-authoring.xml file for staging node to LiveSiteStagingRuntime and restart your od and try deployment.

Thanks

I am sorry to say, but it is showing the same error.
Is there any other file should I need to check?

Thank you

HKN1104

I am sorry to say, but it is showing the same error.
Is there any other file should I need to check?

Thank you

For Staging deployment, only these 2 files..

In Livesite-database.xml, It should be configured properly for staging DB. Please check that.

Thanks

kaleemS

For Staging deployment, only these 2 files..

In Livesite-database.xml, It should be configured properly for staging DB. Please check that.

Thanks

Yes, I had added staging node

{database name="livesite-staging"
db="runtime-staging/iwlsdisplay"
user="iwadmin"
password="mlsdfsdfdeeqghTz7BX+JQYfZm3Wk5Oo"
vendor="rdbms"
jdbc-driver="com.mysql.jdbc.Driver"
protocol-url="jdbc:mysql"
max-id-length="128"
update-type="standalone"
state-field="state"
enforce-ri="yes"
commit-batch-size="1"
real-update="yes"
delete-tracker="yes"
password-encoded="yes"/}

also updated SCRIPT(DeployFilesTargetNodes) of PLC workflow

OLD....

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

NEW .....

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

Am I missing anything else ?

Please help, thank you..

HKN1104

Yes, I had added staging node

{database name="livesite-staging"
db="runtime-staging/iwlsdisplay"
user="iwadmin"
password="mlsdfsdfdeeqghTz7BX+JQYfZm3Wk5Oo"
vendor="rdbms"
jdbc-driver="com.mysql.jdbc.Driver"
protocol-url="jdbc:mysql"
max-id-length="128"
update-type="standalone"
state-field="state"
enforce-ri="yes"
commit-batch-size="1"
real-update="yes"
delete-tracker="yes"
password-encoded="yes"/}

also updated SCRIPT(DeployFilesTargetNodes) of PLC workflow

OLD....

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

NEW .....

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

Am I missing anything else ?

Please help, thank you..

Ok, Looks correct.

Now, Look into your Opendeploy log files and see, Where it is throwing error, is it in lscs or LiveSite.

Thanks

kaleemS

Ok, Looks correct.

Now, Look into your Opendeploy log files and see, Where it is throwing error, is it in lscs or LiveSite.

Thanks

There is no error log has been created in OD/LSCS and OD/LiveSite for new deployment
it is only showing following error in workflow window and in content_center.log (please find the attachment )

Error during task execution: Could not invoke method: deployFiles, reason: null

HKN1104

There is no error log has been created in OD/LSCS and OD/LiveSite for new deployment
it is only showing following error in workflow window and in content_center.log (please find the attachment )

Error during task execution: Could not invoke method: deployFiles, reason: null

Then, It is not even triggering OD.

kaleemS

Then, It is not even triggering OD.

Is there any configuration file should I need to check?

I had configured in odnodes.xml.

kaleemS

Has any one added the multiple (pre-production) environments successfully. If you did, I was wondering if you wouldn't mind sharing the configuration , code or any ideas from experience?
Thank you..

kaleemS

Then, It is not even triggering OD.

I have disabled the lscs ( lscs.enabled=false ) property in the content.properties file.

Now , staging is working fine and deploying the content in to the staging LSDS server only.
However , we need to enable the lscs.

Any suggestion?

Thank you

nipper

Check the permissions on the od-home/conf/lscs folder

It needs to be writable by iwui.iwts

drwxrwxr-x 2 iwui iwts 12288 Aug 30 18:14 lscs

your should see files like this in lscs

rw-r--r-- 1 iwui nobody 4768 Aug 29 11:03 commit-deploy-plc_h68701f2h68701fh.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:03 commit-deploy-plc_h68701f2h68701fk.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g1.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g4.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g7.xml

kaleemS

Check the permissions on the od-home/conf/lscs folder

It needs to be writable by iwui.iwts

drwxrwxr-x 2 iwui iwts 12288 Aug 30 18:14 lscs

your should see files like this in lscs

rw-r--r-- 1 iwui nobody 4768 Aug 29 11:03 commit-deploy-plc_h68701f2h68701fh.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:03 commit-deploy-plc_h68701f2h68701fk.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g1.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g4.xml
-rw-r--r-- 1 iwui nobody 4768 Aug 29 11:20 commit-deploy-plc_h68701fph68701g7.xml

Hey that worked...

At least I am seeing some other errors.
I have enable lscs back ( lscs.enabled=true ). when I published a file into the staging environment. it is showing the following error in AUTH\log\deployment.log file. However it is still publishing file in to the staging LSDS but not in LSCS.

08-31-12 @ 11:18:13 [ERROR] LSCSServiceImpl - java.lang.NullPointerException
at com.interwoven.livesite.lscs.impl.LSCSServiceImpl.startDeployment(LSCSServiceImpl.java:244)
at com.interwoven.livesite.lscs.impl.LSCSDeploymentServiceAdapter.execute(LSCSDeploymentServiceAdapter.java:299)
at com.interwoven.livesite.deployment.model.AbstractExecutableDeployment.execute(AbstractExecutableDeployment.java:65)
at com.interwoven.livesite.deployment.impl.DeploymentRunner.runDeployments(DeploymentRunner.java:246)
at com.interwoven.livesite.deployment.impl.DeploymentRunner.run(DeploymentRunner.java:164)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

08-31-12 @ 11:18:13 [ERROR] DeploymentRunner - deployFiles: received failure result for deployment: StandardMetadata
08-31-12 @ 11:18:13 [ERROR] DeploymentRunner - deployFiles: serviceResponseMessage: LSCS StartDeployment: Error while deploying to LSCS.Please look for content center logs for more details.
08-31-12 @ 11:18:13 [ERROR] DeploymentRunner - deployFiles: failOnError is true; no other deployments will be executed.
08-31-12 @ 11:18:13 [ERROR] DeploymentTaskUtils - deployFiles: found one or more errors while processing target node(s): [staging]

FYI..
Deployment is also creating logs under the OD/LSCS and OD/Livesite.
but there is no error in it.

Also I found following log in OD/log/ServerIP_odbase.log after published to staging.

2012-08-31 11:33:06.087 GMT-0400 serverLog [Thread-75] - API: User: root, role: od-admin. Request app: APP_ODWEBSVC. Using shared key file
2012-08-31 11:33:06.087 GMT-0400 serverLog [Thread-75] - API: Requested start of deployment LiveSite/OpenDeployWebRooth6jf5fd6h6jf5fd8
2012-08-31 11:33:06.087 GMT-0400 serverLog [Thread-75] - API: Calling server to start deployment LiveSite/OpenDeployWebRooth6jf5fd6h6jf5fd8
2012-08-31 11:33:06.087 GMT-0400 serverLog [Thread-75] - ENG: Received request to start deployment LiveSite/OpenDeployWebRoot with instance name h6jf5fd6h6jf5fd8 (LiveSite/OpenDeployWebRooth6jf5fd6h6jf5fd8).
2012-08-31 11:33:06.092 GMT-0400 serverLog [Thread-75] - ENG: Starting job m17 for deployment LiveSite/OpenDeployWebRooth6jf5fd6h6jf5fd8 with parameters: {WFMODELFILENAME=, PAD3=null, WFJOBID=, PAD4=null, PAD5=null, PAD6=null, DEPLOYNAMEAPI=LiveSite/OpenDeployWebRoot, JOBID=m17, SYNCH=true, STARTDEPLOY=true, APPID=, OWNER=root, MINUTEINV=0, HOURINV=0, DEPLOYNAME=LiveSite/OpenDeployWebRoot, RECURSET=NO_RECUR, DAYINV=0, WFUSERSESSIONSTR=, CONFSUBDIR=, REPAIR=false, WEEKINV=0, WEEKDAY=null, DESCRIPTION=, YEARINV=0, DEPLOYSUFFIX=h6jf5fd6h6jf5fd8, STARTTIME=Fri Aug 31 11:33:06 EDT 2012, NO_RECUR=NO_RECUR, LOGLEVEL=VERBOSE, WFMODELDISPLAYNAME=, MONTHDAYS=null, SCHEDULEDDEPLOY=false, REPEAT=false, KEYVALUES=cacheArea=/opt/Interwoven/TeamSite/tmp/LiveSite/workflow/h6jf5fd6
targetArea=/opt/Interwoven/LiveSiteDisplayServices/runtime/web
targetNode=LiveSiteRuntime
areaFileSystemPath=/opt/iwmnt/default/main/test/WORKAREA/default
fileList=/opt/Interwoven/TeamSite/tmp/LiveSite/workflow/h6jf5fd6/WebRoot.h6jf5fd6h6jf5fd8.filelist
area=/default/main/test/WORKAREA/default
cacheFileList=/opt/Interwoven/TeamSite/tmp/LiveSite/workflow/h6jf5fd6/cache.WebRoot.h6jf5fd6h6jf5fd8.filelist
, ENDTIME=null, EXTERNALTASKID=2001, VERIFY=false, PAD2=null, PAD1=null}

Here the targetNode=LiveSiteRuntime is showing up instead of LiveSiteStagingRuntime . any idea?