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

Teamiste dCR

Asmita24

Hello All,

We have an specific requirement in project where, the content is stored in Teamsite as in DCR, but the presentation part is to be handled by external application(java).How can this be achieved?

Deploying the DCR through OpenDeploy/DataDeploy to DB/FS and then external application can pick it?

Please help?

Find more posts tagged with

Comments

Faizi

Hello All,

We have an specific requirement in project where, the content is stored in Teamsite as in DCR, but the presentation part is to be handled by external application(java).How can this be achieved?

Deploying the DCR through OpenDeploy/DataDeploy to DB/FS and then external application can pick it?

Please help?

I would suggest go through the existing DCT/DCR approach for capturing the content. However you can invoke the DCT using URL Commands from external application instead of developing UI in external application for capturing content.
You can use same workflow/OD script for deployment as well. Refer to CSSDK api docs and TeamSite customization guide as well.

kkumar

Hello All,

We have an specific requirement in project where, the content is stored in Teamsite as in DCR, but the presentation part is to be handled by external application(java).How can this be achieved?

Deploying the DCR through OpenDeploy/DataDeploy to DB/FS and then external application can pick it?

Please help?

In my view your DCR data will go to DB using DD and your external program will fetch the values from db.

Adam Stoller

I'm not sure what Faizi was trying to say - but the answer depends a lot on your front end application server.

If your front-end can process XML files and apply (presumably) XSL on-the-fly to render the content appropriately for your web servers - then deploying the DCRs directly to that server, as-is, should be sufficient.

If your front-end queries DB's for content that it then renders appropriately for your web servers - then deploying the content (and metadata) from your DCRs to a DB using DD (or similar) would be the way to go.

If your front-end does a combination of both XSL processing of XML and DB querying - then you want to do both, deploy the necessary information from the DCRs into a DB and deploy the entire DCR as a file to the front-end file system.

ImageURL.rptdesign

Asmita24

Hello All,

Thanks for the inputs.This is my first Teamsite project and I will be here with lots of queries.

If in case external application can pick XML from File Storage and DB as well.

What would be better approach to use Cssdk Client to connect Teamsite or to just deploy DCR and use them in external application.
I am sorry if ques is too generic.

Asmita

ISCBorisB

What would be better approach to use Cssdk Client to connect Teamsite or to just deploy DCR...

It completely, 100% depends on your Application which we know nothing about.

Other things being equal, I personally prefer Deployment. The reason is obvious, overall System has less interdependency.
It simply means that if CMS is down your main App *may* still be operational, you'll need CMS only to promote changes.
Once again, with your architecture this consideration might be not important, irrelevant or even impossible to implement.

Asmita24

thank you all Smiley Happy

ShashankJain

+1 to Boris, deploying DCR directly will eliminate the dependecy with the teamsite server, moreover this xml can be used by any other technology used at the front end.

REQUIRED-OUTPUT.png

ACheethayil

Let me add my 2 cents :-)

1) You can deploy content to DB and your custom java application(thru multiple layer , data/facade layer) can pull the content based on the section/label and content keys.

eg:

100

en_US

Product 100

......<

you can have a method (I am just adding a simple method here)

getProductContent(productkey, content label)
{
/// Implementation goes here
}

Same can be achived XML over http (by sending the DCRs to a repository. Same method can be used by changing the data layer.

Hope it helps.

Adam Stoller

If you're going to add 2 cents - try to make sure that formatting of the information is worth more than a plugged nickel ;-) Having fixed the formatting for you - I'm still not entirely sure what information you're trying to impart - there seem to be some gaps between what you've written and what you're trying to explain - but maybe that's just me.

Let me add my 2 cents :-)

1) You can deploy content to DB and your custom java application(thru multiple layer , data/facade layer) can pull the content based on the section/label and content keys.

eg: [html]

100

en_US

Product 100

......<[/html]you can have a method (I am just adding a simple method here)
getProductContent(productkey, content label)
{
 /// Implementation goes here
}
Same can be achived XML over http (by sending the DCRs to a repository. Same method can be used by changing the data layer.

Hope it helps.

claudiag

Gonna throw in my $0.02 CDN here too.

Even if the front end can handle the XML straight from the DCR, I never go that route unless I have absolutely no choice (this'd usually be a legacy system that doesn't have a mandate to change the way files are generated) because you have no way to massage the data unless you have a generate step.

I realise it's an extra step in the flow, but I cringe at not having that chance to manipulate the data in between the creation of a DCR and deploying it to the database, even if that's not required at this point in time. I consider it future proofing for later - I've just seen this blow up in too many faces over the years!

With regards to the rest, I fully agree with ISCBorisB - that would be my preferred pathway as well.

MD2016.jpg