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; } } }

How to build java externals on branch machines

MonkeyKing

I have read the tutorial regards to Java externals, but I found the programming environment is on the Server machine (to access iw-home directory), I'm not a system Admin and I want to build my Java program on my branch computer, but once I did that, I couldn't use build.dat file to deploy the program, unless I log in as a System Admin. So must I build Java externals on the Server machine? or there is some way to resolve this issue.

Find more posts tagged with

Comments

Stokes

If by "build my Java program" you mean compile the java source, then yes you can build the source on any machine you like and deploy a .jar file to content center if you like.

Stokes.

MonkeyKing

If by "build my Java program" you mean compile the java source, then yes you can build the source on any machine you like and deploy a .jar file to content center if you like.

Stokes.

Hi Stokes,

Thanks for replying, I don't think I described my issue clearly, it is not about compile java source code or deploy a jar file to content center, of course I can do that.

the problem is that once I build my java program in my branch machine, without runing make_toolkit.ipl and build.dat, I can't see my program's output, but to run make_toolkit.ipl and build.dat, I must log in as an admin. The java external programs are not normal java applications which contain 'main' method, so I can't see the output unless i run the build.dat.

Cheers
John

Migrateduser

You could build a test harness using JUnit to invoke the methods in your class with appropriate arguments. Of course, if you need to interact with iwserver, you will have to configure your tests to either use CSSDK to connect to the TeamSite server remotely, or you'll need to provide appropriate mock objects so that your attempts to run your test don't fail.