TeamSite instance

TS741, WS8

We are adding a tool to TeamSite. This is java coide and we are integratinmg it in TeamSite.

5 developers are working on it. Everytime, one developer makes a build, TeamSite has to go down and it takes 10 min to come back.

Is there a way, we can create a separate instance of TeamSite, so that different can work independently. By separate instance, I mean creating a separate server lijke we do with other softwares (I think we can create an instance of OpenDeploy).

If we can create separate instance of TS, does it cost anything ?

Thanks

Find more posts tagged with

Comments

nipper

It always costs more. A lot more.

Your model is wrong.

Compiles should not be done on the TS server (at least as part of the TS UI).

You have a few choices, use a tool like Eclipse check syntax

Then you can build the UI when you want, or if you really know what you are doign, bring the UI down, replace the jar in the right locations and bring the UI back up. Error prone but much faster.

anjanas

Spoiler

Then you can build the UI when you want, or if you really know what you are doign, bring the UI down, replace the jar in the right locations and bring the UI back up. Error prone but much faster

I create a branch in TS witht he customer_project_src layout and then you can run make_toolkit.ipl there, It will run as a user and not restart the UI. That lets you build a jar without restarting the UI. Then you can build the UI when you want, or if you really know what you are doign, bring the UI down, replace the jar in the right locations and bring the UI back up. Error prone but much faster

Craeting a branch in TeamSite is just simple. What is customer_project_src latout ? When do you require a layout for branch ? I have never used any layout for a branch. Can you please let me know, is this layout TeamSiinto TS. te provided ? are there any other layouts available ?

If I run a make_toolkit.ipl in a branch, is it not going to restart TS UI ? I think, I can create jar file outside TS in eclipse or other IDE, put that jar in TS and run make_toolkit.ipl. This integrates the jar file with TeamSIte.

If thats not the case, how do I build UI ?

Thanks

nipper

I create a branch in TeamSite with a folder structure like customer_src including all Java to be modified.

You can create mulitple ones customer_project1_src, customer_project2_src etc which will create only a JAR for that project.

If you run make_toolkit in that branch it will only compile the Java and build a jar (if you have customer_out folder). It will not restart the UI.

That you do before you are ready to restart.

You can either copy it into customer_src/lib and run make_toolkit which will restart the UI (but will not break beacuse of a compiler error). Or you can:

run iwreset -ui stop

cp customer.jar /opt/interwoven/ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/lib/

cp customer.jar /opt/iw-home/ApplicationContainer/server/default/deploy/iw-preview.war/WEB-INF/lib/

iwreset -ui start

That is faster but doesn't do a rebuild. UI still down for a couple minutes.

pratrix

It entirely depends on weather you are using integrating for TeamSite or LiveSite (Preview)

For TeamSite you don't have my option that build on server.

- It is not advisable to run TeamSite on anything other than proper dedicated server

- Each server costs license.

For LiveSite (preview) mechanism is lot simpler after LiveSite is not so complex web application based on Spring Framework.

- You can extract and move all resources of livesite form iw-runtime.war to centralized location

- Integrate it as part of local build.xml for your developers

- Create ant build script to be used with any standard java IDE

- Setup local tomcat server for each developer to which there own version of local jar is deployed.

- Merge / integrate code using Git / SVN

Once right version of file is created you can simply push/copy it to iw-cc.war and iw-preview.war. This should reduce your builds to as low as once or twice in one day and save lot of developer time.