Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DCT in JHTML
Jumjum
We have a particular situation where we want the user to build DCRs from their web page. So if the user is logged on to their web session, we want the user to create the DCR which is stored in their workarea and then deployed from their workarea to production. We don't want the user to leave their session to create small DCR's and then deploy them because of points of failure. Also, upon save can we invoke a deploy when the user saves the DCR.
Any help would be greatly appreciated.
Thank you,
jum
Find more posts tagged with
Comments
Migrateduser
A little more detail in what you are trying to accomplish would be helpful. Is the web session a TeamSite session, or is this another web site? Does each use have their own workarea? How are DCRs created?
That sounds a lot like what the TeamPortal integration does.
If the 'web session' you are refering to is a TeamSite session, then it would be quite easy. If this is an external web session, you will need to have a mechanism to pass the authentication to TeamSite. (Alternatively, you could use a default authentication that has rights to write to all available workarea.) You can look in to using OpenAPI, ContentServices SDK, or possibly even some simple perl CGI scripts to accomplish this.
With FormAPI in TS5.5.2+ you can easily trigger javascript or cgi scripts to occur when the user clicks save. This could be a script that triggers a deployment. Alternatively, a workflow could be launched on save-and-close of the DCR that also runs a deployment.
Jumjum
Thanks Jg,
Here is what I was thinking. we have an ATG instance and when the user logs into ATG they will have an link that takes them to a jhtml page that is designed to mimic the dct that would ordinarily reside in TS. When the user fills out the dct (on ATG), the dcr that is created is placed in workarea (not specific to the user but to the site). Also, upon creating the DCR which now resides in TS, deploy it to the ATG instance.
I hope I clarified it somewhat.
Thanks,
Jum
Migrateduser
Will these DCRs later be edited via TeamSite templating?
You may want to consider reversing the interaction:
1) User fills out jhtml form
2) form processor saves form in DCR format on Dynamo site
3) OpenDeploy called to deploy DCR back to TeamSite
4) OpenDeploy uses a DNR to set the templating extended attribute.
An alternative approach would be to have the TeamSite filesystem mounted on the same server as the ATG instance. That way the form processor can simply write the file there.
OpenAPI can then be called in the form processor to set the appropriate templating extended attribute.
Jumjum
Jg,
Hmmmm, that might work for us, but their might be a sync problem (we have 2 instances). The templates could be either edited again through TS or they could choose to create new content again via the Jhtml. Do you know if you can tie the submit button on the jhtml file to invoke the batch script that Iwov uses to save and create the dcr?
Migrateduser
Do the two instances have the same content or do they have different content? One posibility may be to set up an OpenDeploy base server on all boxes. Whenever a DCR is edited in one of the instances, or in TeamSite, it is deployed to the other locations. The deployments to TeamSite can run the DNR script to update the extended attributes.
You should be able to get the jhtml submit button to run a script to complete the deployments. If you are very zeolous, you could probably even use RMI to invoke some functionality, though I'm not sure what is officially supported in this arena.
-Jeremy
Jumjum
Thanks Jeremy,
I will give this a go!
-Jum
wsinlog.txt
INV9562.3100-DATA-VOIX.txt