when to use maketoolkit.ipl

I am on TS720, Windows Server 2008, WFM

Perl script is called from a link in TS UI. A java jar file is passed it to Perl code as cmd line argument. This java class processes business logic.

This java class is already existing.

I made some changes inn business logic and created exe jar file. This jar file is passed to perl script. It works fine without any issues. Here I did not have to use maketoolkit.ipl nor did I need to place java class file in a designated location in customer_src...

So, when do I need to use this designated path and use maketoolkit.ipl ?

I guess that when java class is to be called from some UI functionality, then this process has to be followed. In here, jar file is called by link UI, does not that mean its used within UI ?

Please give me some clarification on this with small example.

Thanks

Find more posts tagged with

Comments

santosh013

Any java class you create for Teamsite Customization and/or for Workflow(s) needs to go to customer_src. Once you do that or modify any other existing code in customer_src then you need to build it. Where is the confusion?

Adam Stoller

Generally speaking:

Customizations written in Java for workflow URL External Tasks or CGI Tasks, and for custom menu items (and probably for other aspects of UI customization) should go into IWHOME/local/config/lib/content_center/customer_src/src/.... and be built with make_toolkit.ipl

Customizations written in Java for SitePublisher / LiveSite should go into IWHOME/local/config/lib/content_center/livesite_customer_src/src/... and be built with build.bat / build.sh (I'm less sure about this part as I haven't done any such development in this regard)

Are there exceptions or ways to work around the above? Sure - but then you're basically going through "non-standard" / "unsupported" processes -- that is except for when you build your jar files outside of the above mentioned areas and instead place the jar file in ..../lib (instead of .../src), but then you still do the make_toolkit.ipl / build.sh piece to be in a "supported" process.

nirjari

Are there exceptions or ways to work around the above? Sure - but then you're basically going through "non-standard" / "unsupported" processes -- that is except for when you build your jar files outside of the above mentioned areas and instead place the jar file in ..../lib (instead of .../src), but then you still do the make_toolkit.ipl / build.sh piece to be in a "supported" process.

Not very clear with this reply
1) I have link under menu, which calls Perl script. (So this is not a workflow, its only a link in UI, which executes Perl script)
2) This Perl script executes java program using system("java -jar link.jar arg1 arg2 arg3")
3) Does link.jar need to be built using make_toolkit.ipl ? OR even if I make it outside (in eclipse IDE) ,copy it in some place and execute this jar file using system command, will it work ?
4) I am generating link.jar using eclipse IDE, putting it in same location where iwperl is and executing it. It works fine. I did not need to use make_toolkit.ipl
5) Is using make_toolkit.ipl optional ? Whats the difference between jar file created using make_toolkit.ipl and one created outside of TeamSite and then used in IWHOME/local/config/lib/content_center/customer_src/src/ location ?

Thanks

Adam Stoller

Not very clear with this reply
1) I have link under menu, which calls Perl script. (So this is not a workflow, its only a link in UI, which executes Perl script)
2) This Perl script executes java program using system("java -jar link.jar arg1 arg2 arg3")
3) Does link.jar need to be built using make_toolkit.ipl ? OR even if I make it outside (in eclipse IDE) ,copy it in some place and execute this jar file using system command, will it work ?
4) I am generating link.jar using eclipse IDE, putting it in same location where iwperl is and executing it. It works fine. I did not need to use make_toolkit.ipl
5) Is using make_toolkit.ipl optional ? Whats the difference between jar file created using make_toolkit.ipl and one created outside of TeamSite and then used in IWHOME/local/config/lib/content_center/customer_src/src/ location ?

Thanks

nirjari

but why go through the overhead of using Perl to invoke a system call to run java - why not create a Java / JSP CGI program and invoke it directly ( the JSP would [normally] go under .../web as opposed to .../src)

Perl script is already in use with link, I am adding some changes to business logic

Does your Java code actually do anything with the TeamSite toolkits / perform any interactions with TeamSite - or is it some completely external standalone kind of thing?

edition name and edition path is passed to jar file as arguments. Then files within this edition are checked. This code is invoked from link in TS UI, so does it qualify as interacting with TeamSite toolkit ? If no, then when does a code is considered to be interacting with TeamSite toolkit ?

You should not be putting anything into IWHOME/iw-perl/bin - that's a vendor location. You could put it any number of places that would be "ok", though putting it into .../lib and using make_toolkit.ipl would be the officially supported manner - so that it ends up within /iw-cc/...

I am putting code here just for the sake of convenience for now. I will move it to different dir, when code starts working without any issues

The jar file would never be used within customer_src/src - that would be a "source" location (and in this case, the jar would be in customer_src/lib). The make_toolkit.ipl would put that jar file into ApplicationContainer/server/default/deploy/iw-cc.war/... and restart the jboss application to make it "part of the toolkit" (older versions of TeamSite would put it into IWHOME/httpd/webapps/... and restart tomcat). Again, that's the officially supported way to go.

jar file is placed in customer_src/lib, which is then integrated into toolkit by make_toolkit.ipl. If jar file is placed in any other location, then make_toolkit.ipl will not find it and it will not become a part of TS toolkit. Stand alone Java classes are placed in customer_src/src location

Adam Stoller

Perl script is already in use with link, I am adding some changes to business logic

Ok - but it might make sense to rethink the implementation as a whole and do it completely within one language-type rather than mixing/matching - however, for expediency purposes, I can understand why you're doing it this way.

edition name and edition path is passed to jar file as arguments. Then files within this edition are checked. This code is invoked from link in TS UI, so does it qualify as interacting with TeamSite toolkit ? If no, then when does a code is considered to be interacting with TeamSite toolkit ?

If you're utilizing CSSDK then it is interacting with the TeamSite toolkit. If you are doing the things you say without using CSSDK then I'd say you were doing it incorrectly.

I am putting code here just for the sake of convenience for now. I will move it to different dir, when code starts working without any issues

That's a questionable process, but to each their own.

jar file is placed in customer_src/lib, which is then integrated into toolkit by make_toolkit.ipl.
If jar file is placed in any other location, then make_toolkit.ipl will not find it and it will not become a part of TS toolkit. Stand alone Java classes are placed in customer_src/src location

Generally yes, though I suppose it depends on what you mean by "Stand alone Java classes".