Asset Promotion in CS 7.1

[brapacki]

Have any of you developed a good solution to promote web services between different instances of CentraSite 7.1? If I promote web service from dev instance to test instance it still points to wsdl file on dev IS. How to promote web service on CS without manually changing assets while promotion?

[iengca]

Hi brapacki,
Could you explain how you did the WS promotion? I have followed the Admin Guide, create a promotion policy for taxonomy, ws, xml schema, and attributes. It works well for taxonomies. But when I tried to promote WS, I got the error:

"Asset myws promotion failed".

Do you have any idea what went wrong?

Thanks for your help in advance.

[brapacki]

iengca,

This is a known issue, and is solved in SP1 for CS. However please make sure that:

in environment section both instances of CS "see" each other
wsdl file for ws is uploaded correctly to source CS
ws does not use any custom attributes which were not promoted to target instance of CS

Takes a while, but should work.

[iengca]

Hi brapacki,
I am trying to apply SP1 for CSGE7.1. Just wonder if you could give me some tips or share with your experience.

I have kind of gone thru the install guide for SP1. I have no problem doing stage 1 and 2. But not sure if I need/should stage 3 and stage 4 because I am just using the default setting. Here are the step for stg 3 and 4:

Stg3:
====
product-config verify
product-config configure
product-config undeploy-registry
product-config deploy-registry

Stg 4:
=====
product-config apply-sp-data

[brapacki]

It doesn't matter if you use default installation or custom to new app server or oracle. Before applying any fix or patch first run:

product-config undeploy-registry

apply fix and patches and then run

product-config verify
product-config configure
product-config diagnostics
product-config deploy-registry

If I missed any part or changed it's sequence there were some issue. So in my opinion the sequence should look like:

product-config undeploy-registry
product-config apply-sp-data
product-config verify
product-config configure
product-config diagnostics
product-config deploy-registry

[iengca]

Hi brapacki,
Not sure if jboss should be runnig for any of the steps?

Do you mean:

shut down CS
product-config undeploy-registry
product-config apply-sp
start JBOSS (run.bat) ??
product-config apply-sp-data
shut down jboss??
product-config verify
product-config configure
product-config diagnostics
product-config deploy-registry
start jboss for use?

I followed the upgrade guide sequence and failed at the very last step: apply-sp-data. Any clues?

Thanks for all your help.

[brapacki]

If you are using default installation, then shutting down CS shuts down also jboss (at least that's how it looks like). So for none of these steps JBoss must be on.

Please check fixes and SP readmes, but I think that shutting it down was a prerequirement.