Generating page on another site (and branch)

OK, so I have 2 sites that are very different. No content is shared between the 2 until now. The customer wants homepageB content available on site A.

So I can get my homepage TPL to generate the new page. That is not tough. Then my question how do I get the content out. That is why this is posted under workflow.

My gut feeling is that in my build HTML step of the workflow (when the user send homepage B out), I will automatically build the page in the other branch and copy images over. Then I will build out an XML job spec and kick it off via iwjobc.

Another approach is to truly write a WF that can span multiple branches. Put a branch in, if a specific file is in the list (say after the 1st deployment) run a submit and deployment for the 2nd workarea.

Other ideas ?

Find more posts tagged with

Comments

ISCBorisB

OK, so I have 2 sites that are very different. No content is shared between the 2 until now. The customer wants homepageB content available on site A.

So I can get my homepage TPL to generate the new page. That is not tough. Then my question how do I get the content out. That is why this is posted under workflow.

My gut feeling is that in my build HTML step of the workflow (when the user send homepage B out), I will automatically build the page in the other branch and copy images over. Then I will build out an XML job spec and kick it off via iwjobc.

Another approach is to truly write a WF that can span multiple branches. Put a branch in, if a specific file is in the list (say after the 1st deployment) run a submit and deployment for the 2nd workarea.

Other ideas ?

It all depends on "what should happen when". For example, if "customer wants homepage B content available on site A"
you can still process B in the blissful ignorance, as if nothing had changed. Use iwat/iwatsubmit to intercept "B Home Page" submit
(or other suitable) Event and copy generated assets to some dedicated "A" Workarea, submit and *get latest* to other WAs of Branch A

Adam Stoller

OK, so I have 2 sites that are very different. No content is shared between the 2 until now. The customer wants homepageB content available on site A.

So I can get my homepage TPL to generate the new page. That is not tough. Then my question how do I get the content out. That is why this is posted under workflow.

My gut feeling is that in my build HTML step of the workflow (when the user send homepage B out), I will automatically build the page in the other branch and copy images over. Then I will build out an XML job spec and kick it off via iwjobc.

Another approach is to truly write a WF that can span multiple branches. Put a branch in, if a specific file is in the list (say after the 1st deployment) run a submit and deployment for the 2nd workarea.

Other ideas ?

If you go the workflow route - you either need to make sure that the owner of the task that runs iwjobc is a Master - or create a WFT and use iwwft_compile.ipl, which doesn't require Master privileges.

nipper

If you go the workflow route - you either need to make sure that the owner of the task that runs iwjobc is a Master - or create a WFT and use iwwft_compile.ipl, which doesn't require Master privileges.

Yea I figured that i could hardcode tsadmin as the owner of the external task that kicks off the iwjobc job

That should not be an issue