Table of contents:
Notes for MS Windows users: With the installation of JSDK, two copies of JRE are installed:
one in JSDK directory, another in c:\Program Files\JavaSoft\jre\1.4.1\ directory.
Automatic JSDAITM installation procedures detect both copies of the JRE
and suggest to install the programs in the JSDK runtime directory or JRE directory. For the software development
JSDAI is to be installed in JSDK runtime directory.
PATH variable is to be changed in such a way, that the path to JSDK directory were the
first one in the
Only JSDAI kernel, constituting of JSDAI runtime and JSDAI environment
can be installed manually. All applications such as SdaiEdit and STEP-Book
can only be installed through the automatic installation procedure.
Before JSDAI installation, Java 2 SDK need to be installed on the target computer.
JSDAI API consists of the following JSDAI jar-files:
The JSDAI EXPRESS compiler converts one or several EXPRESS schemas into the corresponding Java classes and interfaces. The EXPRESS compiler itself is not included into this release.
jsdai_runtime.jar- file containing the basic JSDAI API code;
jsdai_library.jar- for all Integrated Resources, AICs and APs (STEP part 4x, 6x, 1xx, 2xx, 5xx, ARM only), also PLIB.
The Java classes and interfaces which the EXPRESS compiler generates, needs to be further compiled into the Java byte code by using a default Java compiler. The resulting class-files are then packed into jar files. Because this is a lengthy and complicated process the work is already done for the EXPRESS schemas of the STEP standard. This can be done either for long form schemas or for short form schemas. In STEP, short form schemas have references to other schemas (use from, reference from). Long form schemas are created from the related short form schemas by resolving all the external references to other schemas into local objects. Traditionally, only the long form schemas are used. The advantage of the short form schemas is that they support AP interoperability. This means that application instances may belong to several AP populations simultaneously.
jsdai.propertiesfile of the
extdirectory. For an application to find schema entity instances the property
jsdai.propertiesfile should be adjusted accordingly, e.g.
repositories=c:\\LKSoft-JSDAI\sdaireposin Windows or
repositories=/home/<user_directory>/LKSoft-JSDAI/sdaireposfor Unix systems.
repositoriesis the only mandatory property, other properties are optional.
Below is an example
jsdai.properties file. It needs to be configured
for a given installation as described above. Use a simple text editor to do this.
# properties file for JSDAI, LKSoftWare GmbH # # This properties file is loaded by jsdai.lang.SdaiSession class # during openSession(). # # The jsdai.properties file is searched in the following order # 1) If system property "jsdai.properties" is set to some directory, # jsdai.properties file is being searched in this directory # 2) otherwise, if system property "java.ext.dirs" is set to some directory, # jsdai.properties file is being searched in this directory # 3) otherwise jsdai.properties file is being searched in the directory, # specified by the system property "java.home". # If the file jsdai.properties cannot be located in any of these directories, # a SY_ERR exception is thrown during openSession(). # # These properties are needed: # repositories=directory-path # specifies an existing directory for persistent data storage. # For every SdaiRepository a subdirectory is created there # Example: # repositories=c:\\Program Files\\LKSoft-JSDAI\\sdairepos # # here goes the directory where repositories are located # repositories=/home/<user_directory>/LKSoft-JSDAI/sdairepos # # Schema alias can be specified as follows: # jsdai.SXxx=ALIAS[;ALIAS1] ... [;ALIASn] # Example: # jsdai.SAutomotive_design=AUTOMOTIVE_DESIGN;AUTOMOTIVE_DESIGN_CC2 # # ALIAS[1...n] give the names of other EXPRESS schemas which are represented by # this SdaiModel. Alternatively, each of these names may be an alias of the EXPRESS # schema described by the model. Also, the model may represent a combination of # two or more EXPRESS schemas. # # Aliases: # jsdai.SAutomotive_design=AUTOMOTIVE_DESIGN;AUTOMOTIVE_DESIGN_CC2 # # JSDAI trace log output. System.out - directs log output to the screen. # Optionally log file name can be set. #log=System.out # # If the value of "toStringUnicode" is TRUE, then strings as values of # entity attributes are returned by toString methods in unicode; # if FALSE - in ASCII. This property is optional. (FALSE by default). # #toStringUnicode=FALSE # # Mapping of APs # mapping.schema.AIM_SCHEMA=MAPPING_DATA # If AIM schema is mapped to ARM schema then a dictionary model that contains #mapping data must be specified. # There can be several different mappings for one AIM schema and one mapping #model can specify mapping for several AIM schemas to one ARM schema. # Examples: # mapping.schema.ELECTRONIC_ASSEMBLY_INTERCONNECT_AND_PACKAGING_DESIGN=AP210_ARM_MAPPING_DATA # mapping.schema.ELECTROTECHNICAL_DESIGN=AP212_ARM_MAPPING_DATA # mapping.schema.AUTOMOTIVE_DESIGN=AP214_ARM_MAPPING_DATA # mapping.schema.ELECTRONIC_ASSEMBLY_INTERCONNECT_AND_PACKAGING_DESIGN=AP210_ARM_MAPPING_DATA mapping.schema.ELECTROTECHNICAL_DESIGN=AP212_ARM_MAPPING_DATA mapping.schema.AUTOMOTIVE_DESIGN=AP214_ARM_MAPPING_DATA
repositoriesproperty as persistent data storage. Every
SdaiRepositoryis stored in its own sub-directory which includes several binary files.
During the opening a JSDAI session, all repository sub-directories within the specified repositories directory are made available as "known servers". This repositories directory is also the default place where new repository directories are created.
Create the directory with the full name as configured by
jsdai.properties file, where the persistent repositories files will be placed, e.g.
c:\Program Files\LKSoft-JSDAI\sdairepos in Windows or
/home/<user_directory>/LKSoft-JSDAI/sdairepos for Unix systems.
The default class path is the current directory. In order to gain access to different directories,
CLASSPATH variable or the
-classpath command-line option
should be used.
java jsdai.util.SdaiTerm.You will see a prompt
jsdai.util.SdaiTerm: Documentation, SourceIt is the best to start this application after the installation has been finished to verify that all is installed correctly.
xxx.javausing JSDAI with