JLink Deployment

[BrianKrieger]

I have a JLink general deployment and setup question or set of
questions. Any feedback would be most appreciated!



1) How do you handle the menu files? Do you use local or network
path or.......?

2) How do you assign the menu text file locations? Via Protk
settings, class variables, .......?

3) Do you use any files for configurations? I.e. xml (or other)
files that would set other temp file locations, check files, etc.

a. How do you handle those?

b. What format do you use (txt, xml, binaries, etc.)?



Our environment is shared here. We have xml files that set some file
creation locations, parameter setup, etc. The xml files and the JLink
menu files are all in a shared location (read only for users) as are the
class files, of course. We also use a specific path to a java
environment (jlink_java_path).



Just trying to get a feel for others out there and how we can improve
our installation.



Thanks all!

Brian Krieger

Peterbilt Motors


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[bfrandsen]

Hi Brian
Here is how we have our setup.
Everything is placed local for best performance and synchronizes at each
session start with batch jobs from a network repository.
We have a folder named jlink. Every jlink application is in its own
package. The package becomes a folder with class files on build. We add
this folder to the jlink folder, so each application is in is own
sub-folder.
In the jlink folder we add all .dat files, which is referenced from
individual protkdat config.pro options.
The jlink folder also holds a text folder, where we add all menu and
message files for all applications. The text_dir option in each .dat
references the jlink folder and thus the text folder.
If we are using external libraries, we but the .jar direct in the jlink
folder and add them to the java class. We have used add_java_class_path
config.pro option for this in the past, but it has a limitation on length,
which we exceeded. So from Creo we will start using the .psf file for
handling the classpath.
If applications need external setup files, we add those to a common misc
folder.
What we achieve by this is that everything related to Jlink is well
organized under one common folder, except what has to be in config.pro and
.psf.

Hope this was what you where looking for.

Bjarne





Brian Krieger <->
17-10-2011 17:29
Please respond to
Brian Krieger <->


To
<->
cc

Subject
[proecus] - JLink Deployment






I have a JLink general deployment and setup question or set of questions.
Any feedback would be most appreciated!

1) How do you handle the menu files? Do you use local or network path
or…….?
2) How do you assign the menu text file locations? Via Protk
settings, class variables, …….?
3) Do you use any files for configurations? I.e. xml (or other) files
that would set other temp file locations, check files, etc.
a. How do you handle those?
b. What format do you use (txt, xml, binaries, etc.)?

Our environment is shared here. We have xml files that set some file
creation locations, parameter setup, etc. The xml files and the JLink
menu files are all in a shared location (read only for users) as are the
class files, of course. We also use a specific path to a java environment
(jlink_java_path).

Just trying to get a feel for others out there and how we can improve our
installation.

Thanks all!
Brian Krieger
Peterbilt Motors

Site Links: View post online View mailing list online Send new post
via email Unsubscribe from this mailing list Manage your subscription
Use of this email content is governed by the terms of service at: