Generate ASP Pages in Site Publsiher

Has anyone used this funtionality ?

Simpler HTML pages can be converted to ASP pages just by renaming them, but has anyone utilized a more complex implementation ?

I am currently using Teamsite 7.2.1 Site Publsiher 7.1 with LSDS without targeting and am thinking of doing away with using LSDS at all. I know that in older version of LiveSite that is 2.x you could get the Generate ASP option in the SitePublisher menu by adding the following code to the ui_common.xml in
iw-home\httpd\webapps\content_center\WEB-INF\conf\livesite.
[PHP]
resourceBundle="com.interwoven.livesite.common"
label="livesite.generate_ASP.label"
commandID="iw.livesite.ccpro.generate_ASP"/>[/PHP]

Has anyone implemented this in newer version of Teamsite which has the implementation steps as
1.Identify the feature being customized and the relevant file(s) to edit.

2.Edit the corresponding file(s) in the customer_src directories.

3.Generate the output files, placing them in the customer_out directory, and rebuild the ContentCenter web application by:

a.changing to iw-home/local/config/lib/content_center/customer_src/etc/conf/customer/ui_common.xml
b.and issuing iw-home/iw-perl/bin/iwperl iw-home/bin/make_toolkit.ipl

Comments reveiw criticism harsh critism name calling everything is welcome :-)

Find more posts tagged with

Comments

Rick Poulin

<link id="iw.livesite.ccpro.generate_ASP.link"
resourceBundle="com.interwoven.livesite.common"
label="livesite.generate_ASP.label"
commandID="iw.livesite.ccpro.generate_ASP"/>

I've seen this in the command descriptors as recently as 7.3.1. I haven't used it myself, so I don't know if you can still call it by commandID, but the URL command is still there for you to use similar to the default generate_HTML.

AakarshC

I've seen this in the command descriptors as recently as 7.3.1. I haven't used it myself, so I don't know if you can still call it by commandID, but the URL command is still there for you to use similar to the default generate_HTML.

I got the Generate ASP option and placed it in the Action menu by the following code in

[PHP]

[/PHP]
in the ui_custom.xml, built the toolkit through make_toolkit.ipl
Generated the .asp file which doesn't seem to render right or at all for that matter. Anyone aware of what this command actually does ?

Adam Stoller

When you say it "doesn't seem to render right or at all for that matter" - how are you viewing it? Are you sure the web/app server being used to render it is configured for ASP?

EnableInteractivity.png

Rick Poulin

Anyone aware of what this command actually does ?

Exactly the same as the default "Generate HTML" except it saves files (and generates links) with .asp extensions instead of .html. That's all it is.

shameem

Hi, I am not sure whether any resolution was made out of this thread. However, we observed that "Generate ASP" can be introduced by uncommenting chunk of code in

ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/conf/livesite/ui_filesys.xml

It works fine. However I was wondering whether we have any file which we can edit it outside the application container and during restart teamsite takes up this changes.

Rick Poulin

Well the supported way is to modify the ui_custom.xml as shown above. Are you getting the same issue on your system?

shameem

There were no issues in our dev environment. But when we do the same changes to IT environment, after couple of mins it wipes of the changes and reset the file to default.

During site publisher logging I didn't have the log4j for SP outside the application container. I created the directory structure manually under liveiste src folder which was taken inside the appcontainer during the build.

I agree, ui_custom is one more way, but ui_filesys.xml, makes the menu items comes under "sitepublisher" menu under Generate HTML which looks right place for content author.

We added the changes under appcontainer, is this is the right way to do it. If we have to place the ui_filsys.xml similar to ui_custom.xml outside the app container, where exactly I have to place the file.

For e.g. for ui_custom.xml
./iw-home/ApplicationContainer/server/default/deploy/iw-preview.war/WEB-INF/conf/customer/ui_custom.xml
./iw-home/ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/conf/customer/ui_custom.xml

after build which file from above two replaces the below

./iw-home/TeamSite/local/config/lib/content_center/customer_src/etc/conf/customer/ui_custom.xml

Similarly where I have to put the ui_filesys.xml in order to replace the following file in application container.
./iw-home/ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/conf/livesite/ui_filesys.xml

I dont see any instance of this file under httpd or local/config.

Appreciate any help on this. To do any R&D I am afraid overwriting a wrong file.

Rick Poulin

There were no issues in our dev environment. But when we do the same changes to IT environment, after couple of mins it wipes of the changes and reset the file to default.

This should worry you more than it appears to, depending on which file we're talking about.

During site publisher logging I didn't have the log4j for SP outside the application container. I created the directory structure manually under liveiste src folder which was taken inside the appcontainer during the build.

This is a CCPro UI change. The change should therefore be made in customer_src, not in livesite_customer_src.

I agree, ui_custom is one more way, but ui_filesys.xml, makes the menu items comes under "sitepublisher" menu under Generate HTML which looks right place for content author.

You can make that happen if you use the right ID for the <menu> tag. You can also decide insert it at a specific place in the menu rather than append it to the end if you use one of <iwov-insert-before> or <iwov-insert-after>.

We added the changes under appcontainer, is this is the right way to do it.

Very much no. Changes made directly in AppContainer are subject to be undone under very many scenarios.

For e.g. for ui_custom.xml
./iw-home/ApplicationContainer/server/default/deploy/iw-preview.war/WEB-INF/conf/customer/ui_custom.xml
./iw-home/ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/conf/customer/ui_custom.xml

after build which file from above two replaces the below

./iw-home/TeamSite/local/config/lib/content_center/customer_src/etc/conf/customer/ui_custom.xml

You have it backwards. The file in customer_src is the one that overwrites the above two, during a build.