using .php / .jsp code in SP component

Hi Experts,

We recently installed TS7.3.1 + LS7.3.1 on Linux, which I understand is going to create output with .page extension. Recently I received another set of questionnaire, from our BU members asking about if other tech stacks (such as php, jsp, etc), can be used in component level, so to generate output out of it used in .page file.

So I would like to know if there is any possibility to make this happen. If yes, I would like all everyone to provide their inputs and pointers.

Regards,
AceZone

Find more posts tagged with

Comments

acezone

Hi Experts,

Could anyone, please shed their experience on this query?

Regards,
AceZone

Bowker

One of my mentors taught me that with enough time and money, anything is possible.

In your case I have A solution (I'm sure not the only solution and maybe not the best solution) that will work.

We were/are converting our "old" site over from a home grown JSP application into LiveSite. The BU didn't want to switch everything over at once so I created a "slurp" component that would, by using a custom built Page Token, go get the content of a URL passed in and write it out. LiveSite would open an HTTP connection to the given URL, get the content and paste it in where desired.

It worked 100% of the time every time. The nice thing is the URL it went could have been anything - .jsp, .asp, .... it could be modified to handle binary content (such as automatically generated images) but that's beyond our scope.

The Component looks like this:
[PHP]

[/PHP]

Custom Page Tokens are defined in the Interwoven install folder:
\ApplicationContainer\server\default\deploy\iw-preview.war\WEB-INF\conf\livesite_customer\resources\customer-resource-config.xml

within that file (I'm not at liberty to post the whole thing) will have in there something like:
[PHP]
com.xxxxx.livesite.page.PageInclude

[/PHP]

The source code for you PageInclude class will be in
Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\src\com\xxxxx\livesite\page\PageInclude.java

That class should extend "PageTokenVariable"
(Now it gets complicated and I'm near the end of my knowledge tree for this.) but from what I can tell in the code you need to override the methods:
public void init(final BaseRequestContext context) { // get parameters passed in}
public Element toElement(String elementName)
public void render(final PrintWriter writer, final BaseRequestContext context) throws Exception
private void reinitializeParams(final BaseRequestContext context)

In our code the logic to actually open the http connection and get the content is called from both the "toElement" and "render" methods. I'm not the author of this so I'm not sure exactly what's going on.

Basically we created this as a temporary bridge between our old system and our new one. It could be used to get content from anywhere.

Good luck

acezone

One of my mentors taught me that with enough time and money, anything is possible.

In your case I have A solution (I'm sure not the only solution and maybe not the best solution) that will work.

We were/are converting our "old" site over from a home grown JSP application into LiveSite. The BU didn't want to switch everything over at once so I created a "slurp" component that would, by using a custom built Page Token, go get the content of a URL passed in and write it out. LiveSite would open an HTTP connection to the given URL, get the content and paste it in where desired.

It worked 100% of the time every time. The nice thing is the URL it went could have been anything - .jsp, .asp, .... it could be modified to handle binary content (such as automatically generated images) but that's beyond our scope.

The Component looks like this:
[PHP]

[/PHP]

Custom Page Tokens are defined in the Interwoven install folder:
\ApplicationContainer\server\default\deploy\iw-preview.war\WEB-INF\conf\livesite_customer\resources\customer-resource-config.xml

within that file (I'm not at liberty to post the whole thing) will have in there something like:
[PHP]
com.xxxxx.livesite.page.PageInclude

[/PHP]

The source code for you PageInclude class will be in
Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\src\com\xxxxx\livesite\page\PageInclude.java

That class should extend "PageTokenVariable"
(Now it gets complicated and I'm near the end of my knowledge tree for this.) but from what I can tell in the code you need to override the methods:
public void init(final BaseRequestContext context) { // get parameters passed in}
public Element toElement(String elementName)
public void render(final PrintWriter writer, final BaseRequestContext context) throws Exception
private void reinitializeParams(final BaseRequestContext context)

In our code the logic to actually open the http connection and get the content is called from both the "toElement" and "render" methods. I'm not the author of this so I'm not sure exactly what's going on.

Basically we created this as a temporary bridge between our old system and our new one. It could be used to get content from anywhere.

Good luck

Hi Bowker,

Thanks for providing your feedback. As per going through your point, I understand here you're mapping old CMS with new CMS environment or in other words, old site to new home grown JSP application in LiveSite. But my query is "if other tech stacks (such as php, jsp, etc), can be used in component level, so to generate output as .page but content logic shall be rendered via php / jsp files?"

It would be great help if you may kindly elaborate more on this?

Regards,
AceZone

nipper

if other tech stacks (such as php, jsp, etc), can be used in component level, so to generate output as .page but content logic shall be rendered via php / jsp files?"

The "requirement" does not make a lot of sense. Components are code, developed with Java and XSL. They can render display technology (HTML, ASP, maybe PHP and JSP as well), but you are not developing in those languages.

.page files need to be rendered through Tomcat with the LiveSite jar files, that should handle JSP/PHP but I have never tried.

Bowker

My solution is used to "slurp" remote URLs and include their content within a component.

The system doesn't really care if the remote URL is written in COBOL, Assembler, Python, Perl, ASP, PHP, JSP, Java, ... The solution I provided is totally generic and can be used to get content from ANY environment and if your security/network/... allows it, from other applications anywhere in the world that supports what ever protocol you want to implement.

In my case we implemented a REST type interface. You can do whatever you want. (or not)

As I said - my solution is one of many possible options. We picked this one since it was totally generic and language independent.