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

Teamsite and J2EE Portal

jkm

Hi All,
We have a portal where external user can log in, view their order details, Build new products etc .. typical J2EE architectcture and content of this portal is mantianed in TeamSite. I can easily mantain the news breifings, articles etc (static content) in TeamSite but if I want to preview the comeplete page in TeamSite and in the preview page I want, on click of Login button user should be able to login to portal and build his new products. Search for new product components etc which has to be supplied by portal server.

I think this can be acheived using double proxy, but I am not 100% sure. Can anyone assist me how this can be acheived in TS..

Any ideas are appreciated Smiley Happy

cheers!!
-Rocky
TS6.5 Solaris

Find more posts tagged with

Comments

jkm

Hi All,
Any ideas on this are really appreciated ..or if my requirements are not clear then I can provide more info on this

jkm

Is this really a tough thing to achieve in TS ..this is a Sales portal whose content we want to put in TS and business logic on portal .. but at the end would like to preview everything from Teamsite before deployment
does teamsite is only good for static content ( I belv NO )
Adam, Jeff, Andy, Greg, Johnny, Steph, Dave or Sunil or any other TS players ... any pointers on this please Smiley Happy

Adam Stoller

I think you need to consider setting up a "staging" server - which will run your portal software - to which you can deploy your content and preview it in the correct context.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jkm

Thanks Adams for replying, this means we need to deploy the pages to Staging app server and then user will preview there only .. isnt there anyway out by which user can preview from TeamSite the complete page and functionality.. because if user has to preview page on app server then it will add lot many steps to preview any page which user wont like at any point of time.
Cant we simply this with anyway ? Any thoughts

Adam Stoller

It can be simplified by providing a customized preview option that takes care of the deployment and then provides links - or just redirects to - the page on the staging server (since it's a portal app - I'm not sure the individual page has much meaning?)

Take all this with the proverbial grain of salt - I haven't done much work with portals - there might be an easier / better way to do it - my suggestion is just a simple, straight-forward approach.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jkm

Thanks Adams for your suggestions, It gives me now some options to think with new spectrums .. but I have seen (haven't done althought Smiley Wink

) some implementations of IWOV in news and magazine sites which are portal integration with TS and in those cases preview works from TS.

Cant we achieve this by making some kinda redirection thru iwproxy .. thts why I mentioned double proxy in my first post.
If anyone else has done similar thing please let me know or if IWOV engineers provide some comments on this will be definitely great.

thor

We aren't using any portal functionality, but what you are talking about sounds similar to what we're doing. We virtualize (preview) our content in ATG Dynamo. To do this, we need to send the DCR off to a separate application server where Dynamo is installed. We have the iwproxy handle this redirection from iw.cfg:

[iwproxy_preconnect_remap]
_regex=^(/iw-mount/default/main/IWDevelopment/SalesSource/WORKAREA/content)([^\?
]*.xml)$=http://lowe:8845/virtualization.jsp?atghost=lowe&atgport=8845&workarea=
$1&record=$2

This captures the path and name of the DCR that the user clicked on and send the request off to the Dynamo server.

Hope this helps.

Thor

smenon

Have you looked at the Sales Productivity Intranet - a new solution that is being shipped this month built on top of TeamSite and LiveSite? With LiveSite you can now create and manage dynamic web pages and websites as well.

--Sunil Menon
Sr. Product Manager
Interwoven, Inc.

gzevin

I have worked on a similar thing before - unfortunately I cannot see any other option but to have something like Ghoti has suggested - an instance, or, in fact 2+ instances of the portal (one or more for workarea preview, one for staging). The issue is that in many cases one needs to login as different users, in order to see how the content is rendered by the portal application...

what smenon is suggesting is Ok, but again this is a new implementation, that will make you buy new Interwoven products, and rethink your current implementation

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jkm

Thanks Sunil and Greg for your replies.

Sunil, As Greg already mentioned LiveSite and Sale Portal both are very new products of IWOV and our customer will not go for this at the moment and the time bandwidth its not permittable. We may look this as an option in our next release.

Yeps, we are planning to go by second approach as suggested by Adams to preview the pages from STAGING server. With this approach I need to build my pages in individual sections and then deploy those individual sections to STAGING server and on STAGING server we will have full page templates built in JSP and those templates will pick the individual sections and display the complete page. But the problem in this approach, how the page will come to know which are the tiles it has to pick ? Say my pages comprises of header, news, Promotions, events etc sections and all these sections are deployed to STAGING server but how does STAGING server will come to know which section has to place where in the page Smiley Sad

Any detailed thoughts are appreciated .. I m struggling hard to freeze the design becasue of these issues Smiley Sad

gzevin

from what you are saying, I can tell that you have not started your design as yet. One needs to talk to both JSP developers and TeamSite architects/developers to work out how to achieve different content types being deployed and rendered properly.

I have designed a similar solution, based on metadata.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Solito

Greg tell us then how you used metadata for ?
thanks
M

gzevin

Well, I dealt with Weblogic Portal, so your details might be different. It has its own content types, so JSP developers can use the types to render portlets based on users' credentials/groups, etc, etc. In TeamSite we developed a number of templates for the content types (actually, we did have something like News, Quick Links, etc.. ), these templates were producing appropriate HTML files and corresponding .md.properties files, that were fed to the Portal Server via Bulkloader.

As I said above, it's not an easy excercise and takes multiple iterations to get everything right. I was lucky to be in a quite diverse team that had dedicated business analysts, JSP developers, TeamSite developers, that all participated in our joint sessions.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Solito

Impressive
did you use "iw_ostream" to generate at the same time the html files and the md properties ( extracting the applied metadata to a dcr i guess )
also you confirm that deletion scenario can be automated ...starting from a dcr deletion ..?
i always thought it was impossible to automate the deletion with bea bulkloader

many thanks Greg

gzevin

yes, I believe we did use iw_ostream, in many cases we produced just dummy html files, just for the sake of feeding .md.properties to the server (on paper, bulkloader *should* extract <meta> tags from HTML header, but it did not for some reason, so we made a decision to feed html-properties pairs all the time).

as for the deletion - it does work with bulkloader, I guarantee it Smiley Happy

With the deletion of content one should be carefyl - one might want to retain the content in CMS, but delete it on the server, so many scenarios are possible.

Actually, at the moment I am finalising a project that feeds LOM (learning objects') metadata to a Verity K2 search engine (metadata is attached in TeamSite as EAs, then a XSLT produces LOM XML, then we generate key-value pairs text files, that are fed to Verity). So, the users have opted not to delete the files in TeamSite, but rather stamp them with an extra metadata that indicates whether the cintent is in Verity or not.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Solito

precious informations thanks a lot Greg

Solito

yes, I believe we did use iw_ostream, in many cases we produced just dummy html files, just for the sake of feeding .md.properties to the server (on paper, bulkloader *should* extract <meta> tags from HTML header, but it did not for some reason, so we made a decision to feed html-properties pairs all the time).
// then you just deploy those dummy html files encapsulating your metadata and no jsp are generated and deployed
as for the deletion - it does work with bulkloader, I guarantee it Smiley Happy

With the deletion of content one should be carefyl - one might want to retain the content in CMS, but delete it on the server, so many scenarios are possible.
// and what if you've got thousands and thousands of dcrs in the cms affecting performances ..?
Actually, at the moment I am finalising a project that feeds LOM (learning objects') metadata to a Verity K2 search engine (metadata is attached in TeamSite as EAs, then a XSLT produces LOM XML, then we generate key-value pairs text files, that are fed to Verity). So, the users have opted not to delete the files in TeamSite, but rather stamp them with an extra metadata that indicates whether the cintent is in Verity or not.
// the metadata is king Smiley Happy

// your verity search engine is used in prod and acting as a search engine on portal side is it ..?
// don't you deploy also the content ( dcr in a db or jsp in some filesys ) ..?

Solito

Greg i guess you decided to avoid metatagger why ..?
thanks

MSU report.txt

Solito

read this somewhere :

The first solution has a limitation of not being able to delete content using the Bulkloader. So you would have to build a post-deployment script that deletes the files and associated metadata

don't you agree ..?

gzevin

then you just deploy those dummy html files encapsulating your metadata and no jsp are generated and deployed

I am talking about deploying CONTENT .. JSPs work on the server side to render the content appropriately
and what if you've got thousands and thousands of dcrs in the cms affecting performances ..?

TeamSite is an enterprise-class software, it should be ok... onless you are dealing with mass deployment.. but I doubt this cannot be avoided

your verity search engine is used in prod and acting as a search engine on portal side is it ..?
don't you deploy also the content ( dcr in a db or jsp in some filesys ) ..?

Verity is used in both prod and test. It has no connection to portal, I mentioned it in a completely separate context.

We do deploy content, in deifferent shapes and forms

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

gzevin

I do not agree. Yoy *can* delete both content in the CMS and the content in the Portal repository, using different means, incuding the bulkloader

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

gzevin

I don't know why you came up with metatagger here. It's about discovering metadata, I am talking about using metadata. Two separate issues

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Solito

then you should write send some comment to the guy who wrote this article .. Smiley Happy

gzevin

which article you are talking about?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU