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

To Use Only SitePublisher (without Targeting Module)

Ugan

I wanted to know how effectively we can use SitePublisher (without targeting) and will SitePublisher will help to fit for making the page sections in the larger enterprise applications where the other part of the section is dynamically rendered using J2ee framework by running queries and xml's.

I have my current site built in J2EE framework where most the content is deployed using the datadeploy to DB , and from DB using the runtime queries each section is deployed with the required content wherever is necessary, in such kind of applications, where does SitePublisher plays a role to make the effective use of web page development, Will SitePublisher still support such sites atleast for interactive interface for design, do anyone have come across this kind of big changes in the architecture. Can give more light on this kind of thoughts if anyone has implemented such an activity.

Find more posts tagged with

Comments

Faizi

I wanted to know how effectively we can use SitePublisher (without targeting) and will SitePublisher will help to fit for making the page sections in the larger enterprise applications where the other part of the section is dynamically rendered using J2ee framework by running queries and xml's.

I have my current site built in J2EE framework where most the content is deployed using the datadeploy to DB , and from DB using the runtime queries each section is deployed with the required content wherever is necessary, in such kind of applications, where does SitePublisher plays a role to make the effective use of web page development, Will SitePublisher still support such sites atleast for interactive interface for design, do anyone have come across this kind of big changes in the architecture. Can give more light on this kind of thoughts if anyone has implemented such an activity.

Yes! you can use SitePublisher without Targeting module. Targeting is basically segmented the whole site according to site's user group.

SitePublisher is primarily support Java/J2ee framework (now .net support released). So you can implement J2EE application on SitePublisher. You have to define what are the areas need to be content management. The best solution is to divide each page in blocks now create develop component for each block and finally put all these on page.

If you go through the OOTB sites you will get complete idea of development on SitePublisher. I suggest you should also go through the SitePublisher Developer's Guide.

vpatel

... SitePublisher is primarily support Java/J2ee framework (now .net support released) ...

SP still operates in Java. It is the LS Runtime that has a version for .NET.

Back to original question, yes you can use SP without Targeting. You can also use SP without LiveSite Runtime all together. Using SP alone, you'll have to generate static HTML (or perhaps JSPs that'll fit into your Java environment) pages and deploy them. SP by itself provides your business users with the ability to assemble pages in a drag-n-drop fashion -- they have full control over the page layout. That is probably the biggest benefit.

In addition to SP, you can also have LiveSite. With LS, your business users can have access to dynamic components / functionality on the pages that they control. Examples: top 10 articles on your site, get external feeds, stock quotes, polls, etc.

In addition to SP and LS, you can also have Targeting. With Targeting, you can target content for specific set of users. For example: if the user is male and over 25 then show business content versus if the user is male and under 25 then show sports content.

There is also a Java tag library that is offered. For existing Java / J2EE shops, you could use the taglibs if you wanted LS .pages integrated within your JSPs.

HTH!

Faizi

SP still operates in Java. It is the LS Runtime that has a version for .NET.

Back to original question, yes you can use SP without Targeting. You can also use SP without LiveSite Runtime all together. Using SP alone, you'll have to generate static HTML (or perhaps JSPs that'll fit into your Java environment) pages and deploy them. SP by itself provides your business users with the ability to assemble pages in a drag-n-drop fashion -- they have full control over the page layout. That is probably the biggest benefit.

In addition to SP, you can also have LiveSite. With LS, your business users can have access to dynamic components / functionality on the pages that they control. Examples: top 10 articles on your site, get external feeds, stock quotes, polls, etc.

In addition to SP and LS, you can also have Targeting. With Targeting, you can target content for specific set of users. For example: if the user is male and over 25 then show business content versus if the user is male and under 25 then show sports content.

There is also a Java tag library that is offered. For existing Java / J2EE shops, you could use the taglibs if you wanted LS .pages integrated within your JSPs.

HTH!

Thanks 'Vpatel' for explaining in detail. I hope this will give 'Ugan' a good understanding to use SitePublisher with J2EE framework.

Thanks,

Synthese_commune.rptdesign

Ugan

Thanks Guys, That was very good input.

I need one clarification, When I use only SitePublisher (for giving the extra benefit of look and feel and control over a Page to business users) , I feel the drawback here is that we can create only Static pages (as patel mentioned). If i need to generate the dynamic runtime pages then i feel definitely it requires the Livesite runtime. But nevertheless today's site are completely customized and need the dynamic rendering on every page, So I feel it could not be possible in this scenario. The only solution i found was we can call the Controllers (servlets) in the components for handling the dynamic data.

One more doubt to the thread. Will the application handle all displays .pages,.jsp's,.html's ? if i start using the SitePublisher without the runtime.

vpatel

Thanks Guys, That was very good input.

I need one clarification, When I use only SitePublisher (for giving the extra benefit of look and feel and control over a Page to business users) , I feel the drawback here is that we can create only Static pages (as patel mentioned). If i need to generate the dynamic runtime pages then i feel definitely it requires the Livesite runtime. But nevertheless today's site are completely customized and need the dynamic rendering on every page, So I feel it could not be possible in this scenario. The only solution i found was we can call the Controllers (servlets) in the components for handling the dynamic data.

One more doubt to the thread. Will the application handle all displays .pages,.jsp's,.html's ? if i start using the SitePublisher without the runtime.

Again, SP by itself is an authoring environment. LS is the runtime J2EE app. In SP/LS Controllers and Externals provide a mechanism to build/retrieve your dynamic content from variety of sources. You don't always have to have Controllers.

LS is a J2EE application and only .page files are supported directly. However, you could easily fetch HTML files within your components. As far as JSPs go, if you really need co-existence of your existing JSPs and LS then there are various different options. It would all depend on what level of co-existense you need, what is integrating into what, etc. One of the options that I mentioned earlier is that there is a JSP tag library that is offered for such integrations. I would suggest get some professional help in getting that architecture hashed out. IMHO it'll be difficult to get the correct and right level of architectural assistance through the forums here.

Ugan

Thanks for the reply. Good to know upto here for beginners.

I was trying to analyse the level of effort of making the changes in the existing J2EE architecture without breaking the rules of MVC, taking the advantage of LiveSite giving the whole control of site to Business developers using only SitePublisher without the runtime and targetting modules.

mvusthipalli

I agree with VPatel's comments on it.

Ugandhar, here are my comments:

I don't see a reason why you are insisting to have SitePublisher only and not to have LivSite. Having LiveSite runtime on your application servers does not mean that you have to change the whole architecture of your web application. Also Having SitePublisher/LiveSite does not mean that your whole J2EE web application has to be migrated to this new model of SitePublisher/LiveSite.

You can design only certain portions of the pages or some pages only to be controlled by SitePublisher/LiveSite and render the content of .pages in your application's JSPs using the taglibs, as mentioned earliler by VPatel. But that is true if you have LiveSite runtime. If you still don't want to have LiveSite runtime, then you can generate HTML/JSP from .page in SitePublisher and deploy it to application server. This deployed HTML/JSP (generated by SitePublisher) can be included in your JSP pages.
To generate a JSP, you would need to change the configuration file: iw-home\httpd\webapps\content_center\WEB-INF\conf\livesite\ui_common.xml. Please refer to http://devnet.interwoven.com/forums_vb/showthread.php?t=25920&forumid=66&highlight=Generate

Rather than doing this kind of generating JSP/HTML, it's a good idea to use LiveSite when you are planning to have SitePublisher. It will give more options to you and your business team in future: segmentation and targeting etc., I believe I can explain you better if you can talk to me. Please give me a call.

Murali

Tables&ViewsInIDA(12Oct12).JPG

Ugan

Thanks for adding more Information Murali.

I would really think of having LiveSite Runtime atleast for future benefits as you said.

Stokes

Ugan,

I think you want the LiveSite JSP Tag Library. That's essentially a LiveSite runtime that you can embed in your existing JSP pages. So if you have an existing JSP app and you want some portions of the application that are going to stay managed that way, and new or converted sections of pages that are going to be authored in SitePublisher, then the tag library is the way to go. It will render .page files in whatever sections of your existing app you want them to go in.

Stokes.