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 Preview

System

Hi,

Iam working on Teamsite 6.5 (Solaris) and we generate JSPs using PTs, in our project we have 2 kinds of users i.e Teamsite users (Internal) and Business users(External- non-teamsite). When implementing preview for the internal and external users i can think of following approaches.

1.Install a new instance of application server in Teamsite and use iwproxy_preconnect_remap to redirect to the new instance of application server(This will serve internal users) and install another instance of application server outside Teamsite to serve external users.
2.Install a new instance of application server in Teamsite to serve both internal and external users.
3.Install a new instance of application server outside which can cater to both Teamsite users and external users.

Implementing first approach will have an overhead in syncing up application code in 2 different places.
In case of second approach can external users access application server which is in Teamsite without Teamsite authentication?
In case of third approach, is that feasible to implement this? will iwproxy_preconnect_remap can redirect the internal preview to an application server outside of Teamsite? Also can smart context be enabled with this appraoch?

Please let me know your thoughts on this. If you think of a better approach to serve our needs do let me know.

Thanks,
Arun

Find more posts tagged with

Comments

ISCBorisB

There is nothing conceptually wrong with these approaches, any of them can work.

For what it's worth, #1 is IMO just over-engineered #3. As long as you have external *Rehearsal* Environment for all, another
one in CMS *seems* to be redundant. You'd need resources (code, support, deployments, back-up, you name it) to keep environments
in synch without any obvious gain for this investment. Of course there might be other considerations for your particular business case.

can [...] iwproxy_preconnect_remap redirect the internal preview to an application server outside of Teamsite?

It's not trivial. You may start with this old article and perhaps contact support.

Out of three #2 may be the simplest one to implement. You can configure virtualization Web Server to accept unauthenticated requests.

madhug

Hi,

Install the application out of teamsite box and use the visualization's concept of temaiste. If the teamsite user generates the JSP page and clicks on the page since it's visualized it the JSP page will be rendered. Other user business user also can access the application from the application server.

I guess this will help you.

ISCBorisB

Install the application out of teamsite box...
teamsite user generates the JSP [...] and clicks on the page...

If target Application has been installed outside of Teamsite where exactly your user "Clicks on the Page"? Using what GUI?

...use the visualization's concept of temaiste

What "concept"? What does any of these mean?