- Q. Will it work
on Linux?
- Q. Is it possible
to run two frameworks on the same computer?
Q. Will it work
on Linux?
Q.
Will it work on Linux?
A. It will work on Linux, although with restricted
features.
Version
1.0ß was targeted for users of Windows, rather than
Linux. However, as most of
the coding is in Java,
those sections will run on
Linux. Unfortunately though, the sections with coding
native to Windows will not work.
The restricted features
are as follows:
- Voice & video
component applications
- Web
browser component applications (Internet Explorer)
- Resource
management component applications
- Device manager
The
version to be released after 1.0ß will be fully compatible
with Linux.
The following are instructions to
enable use on Linux (with some functions restricted).
Instructions for Use on Linux (with
some functions restricted)
The following assumes the root directory
of the source tree to be SOBASRC.
1. Necessary software
- JDK 1.4.0 or above
- ant (http://ant.apache.org/)
- xerces (check http://xml.apache.org/xerces-j/index.html
to confirm operationality with xerces-1.4.4)
2. Preparations
Install xerces.jar to $(SOBASRC)/lib/xerces.jar 3. Build
- Building the Java source code
% cd $(SOBASRC)
% ant
and a Java class file set is built
in $(SOBASRC)/build
- Building the application
% ant applications.archive
and the applications under $(SOBASRC)/applications
are created
4. Creating Install Images
After the above 3 steps, run the following
in $(SOBASRC)
% ant install
When this is run, a directory is created
under ${install.dir} the same as when an installer
is used. (The default is dest).
5. Creating Key Tools
- Copy and paste the shell script
given below, saving it as ${SOBASRC}/dest/createkey.sh
- Use the following to enable execution.
% chmod +x createkey.sh
- Activate the module saved in 1.
in the ${SOBASRC}/dest directory. Give it the following
parameters and execute.
%
./createkey.sh <user name> <password> ./home/user/config/default "CN=<user>"
An example of execution with user name: user and password: password
% ./createkey.sh user password ./home/user/config/default "CN=user"
The password must be more than 6 characters.
Script to create a keystore (createkey.sh)
#! /bin/sh
# $1=alias
# $2=password
# $3=keystore file base name
# $4=DN (CN=<name>, OU=<type of organization>, O=<name of organization>, L=<city>, ST=<area name>, C=<country>)
# create key
keytool -genkey -keyalg RSA -alias $1 -keypass $2 -storepass $2 -keystore $3.session.ksr -validity 9999 -dname $4
# create session key
cp $3.session.ksr $3.user.ksr
# export key
keytool -export -rfc -alias $1 -file $3.certificate -storepass $2 -keystore $3.session.ksr
# import trust storekey
echo yes | keytool -import -alias $1 -file $3.certificate -keypass $2 -storepass $2 -keystore $3.session.tks
# create session trust store
cp $3.session.tks $3.user.tks
rm $3.certificate |
6. Creating a Peer ID
Executing the following 3 steps will create
an appropriate Peer ID and overwrite it into
{SOBASRC}/dest/system/config/{network.xml,
soba.xml}.
The user name will also be set in ${SOBASRC}/dest/user/config/user-context.xml
- Copy and paste the shell script
given below, saving it as ${SOBASRC}/dest/create_peerid.sh
- Use the following to enable execution.
% chmod +x create_peerid.sh
- Activate the module saved in 1.
in the ${SOBASRC}/dest directory. Give it the following
parameters and execute.
%
./create_peerid.sh <user
name>
An example of execution with user name: user
Peer ID creation script (create_peerid.sh)
#! /bin/sh
# $1=user name
PROJECT_HOME=.
XML_PARSER=./lib/xerces.jar
SOBA_CLASSPATH=${PROJECT_HOME}/soba.jar:${XML_PARSER}
SOBA_HOME=./home/system
USER_HOME=./home/user
SOBA_ARGS="-Dsoba.home=$SOBA_HOME -Duser.home=$USER_HOME -Djava.library.path=${PROJECT_HOME}/lib/win32"
java -classpath ${SOBA_CLASSPATH} ${SOBA_ARGS} org.soba_project.ri.session.EditConfiguration $1
|
7. Disabling the Device Manager
Comment-out the part as shown in the following
location for ${SOBASRC}/dest/home/system/config/soba.xml
Before the change
<object name="Device Manager"
class="org.soba_project.ri.resource.util.win32.DeviceManagerWin32"
initializer="start"
finalizer="end"/>
|
After the change
<!--
<object name="Device Manager"
class="org.soba_project.ri.resource.util.win32.DeviceManagerWin32"
initializer="start"
finalizer="end"/>
-->
|
8.
Activation
- Copy and paste the shell script
given below, saving it as ${SOBASRC}/dest/startpeerApp.sh
- Use the following to enable execution.
% chmod +x startpeerApp.sh
- Activate the module saved in step
1 in the ${SOBASRC}/dest directory.
% ./startpeerApp.sh
Execution script (startpeerApp.sh)
#! /bin/sh
PROJECT_HOME=.
TMPPATH=$PATH
PATH=$PROJECT_HOME}/lib:${PROJECT_HOME}/lib/win32:${PATH}
XML_PARSER=${PROJECT_HOME}/lib/xerces.jar
JACOB_CLASSPATH=${PROJECT_HOME}/lib/jacob.jar
SOBA_CLASSPATH=${PROJECT_HOME}/soba.jar:${PROJECT_HOME}/sessionapl.jar:${PROJECT_HOME}/apps/browser/compappbrowser.jar:
${PROJECT_HOME}/apps/chat/compappchat.jar:${PROJECT_HOME}/apps/rsmgr/compapprsmgr.jar:${PROJECT_HOME}/apps/vv/compappvv.jar:
${PROJECT_HOME}/apps/whiteboard/whiteboard.jar:${PROJECT_HOME}/apps/sobachi/sobachi.jar:${XML_PARSER}:${JACOB_CLASSPATH}
SOBA_HOME=./home/system
USER_HOME=./home/user
SOBA_LOGGING=${SOBA_HOME}/config/logging.properties
SOBA_ARGS="-Dsoba.home=${SOBA_HOME} -Duser.home=${USER_HOME} -Djava.util.logging.config.file=${SOBA_LOGGING} -Djava.library.path=${PROJECT_HOME}/lib/win32"
SOBA_MAIN=org.soba_project.ri.Soba
echo PROJECT_HOME = ${PROJECT_HOME}
echo SOBA_CLASSPATH = ${SOBA_CLASSPATH}
# echo XML_PARSER = ${XML_PARSER}
# echo PATH = ${PATH}
# echo SOBA_ARGS = ${SOBA_ARGS}
# echo SOBA_MAIN = ${SOBA_MAIN}
java -classpath ${SOBA_CLASSPATH} ${SOBA_ARGS} ${SOBA_MAIN}
|
Q. Is it possible
to run two frameworks on the same computer?
Q.
Is it possible to run two frameworks on the same
computer?
A. Yes, it is.
The following are instructions to
enable the activation of two frameworks on the same
computer.
Instructions for the Activation of
two Frameworks on the Same Computer
To enable the use of two frameworks on
the same computer, changes in the user ID, peer ID, and
wait port are necessary. The following assumes the installed
directory as SOBA.
1. Creating User ID
The keystore must be changed as the user
ID is created from the public key on the certification
form inside the keystore.
The easiest way is to install
it twice, thus creating two keystores. The instructions
for that are as follows:
- Install as usual.
- The keystore will be created as
${SOBA}\home\user\config\default.{user,session}.{ksr,tks}.
Copy this and set aside.
- Uninstall.
- Install it again, and this time,
change the user name. Also, there should be no
need to reinstall JRE or Active-X. You should also
not have to reboot.
- Copy the setting file.
% copy ${SOBA}\home ${SOBA}\home2
/S
- Overwrite the keystore copied in
step 2 onto ${SOBA}\home\user\config
Next, the security and permissions need be changed in
${SOBA}\home\user\config\security.xml
Before this change, the current user name should be that
from the 2nd install.
This needs to be changed to the first user name as in
the following example.
Before the change (the user name from
the 2nd install is sobauser2)
<assign-resource-role role="resource-owner">
<user keyalias="sobauser2"/>
</assign-resource-role>
|
After the change (the user name from
the 1st install is sobauser1)
<assign-resource-role role="resource-owner">
<user keyalias="sobauser1"/>
</assign-resource-role>
|
For
an additional information, add the name from the
1st install between <name></name> in
${SOBA}\home\user\config\user-context.xml
This makes the name easily distinguishable. 2.
Changing the Peer ID
The
peer ID in ${SOBA}\home2\system\config\{soba.xml,
network.xml} also needs to be changed. After this
change, the values for soba.xml and network.xml must
be the same.
As the values to be changed are those after Soba:PeerID,
it is often a good idea to change the last character
to a capital letter as in the following example.
Before the change
network.xml
<my-peer id="Soba:PeerID:9BeMGbGW5dHnBGak" port="10240"/>
soba.xml
<peer id="Soba:PeerID:9BeMGbGW5dHnBGak"/>
|
After the change
network.xml
<my-peer id="Soba:PeerID:9BeMGbGW5dHnBGaK" port="11240"/>
soba.xml
<peer id="Soba:PeerID:9BeMGbGW5dHnBGaK"/>
|
3. Changing Ports
- The port number in ${SOBA}\home2\system\config\network.xml
needs to be changed. Change it to an appropriate
number as in the following example.
Before the change
<my-peer id="Soba:PeerID:9BeMGbGW5dHnBGak" port="10240"/>
|
After the change
<my-peer id="Soba:PeerID:9BeMGbGW5dHnBGaK" port="11240"/>
|
- The port number in ${SOBA}\home2\system\config\resource.xml
also needs to be changed.
The port number is defined by the value of the "port" attribute
in the name attribute for the porpertydef tag. Change
it to an appropriate number as in the following example.
Before the change
<propertydef name="port" type="integer" value="5010"/>
<propertydef name="port" type="integer" value="5020"/>
<propertydef name="port" type="integer" value="5100"/>
<propertydef name="port" type="integer" value="5110"/>
<propertydef name="port" type="integer" value="5120"/>
|
After the change
<propertydef name="port" type="integer" value="6010"/>
<propertydef name="port" type="integer" value="6020"/>
<propertydef name="port" type="integer" value="6100"/>
<propertydef name="port" type="integer" value="6110"/>
<propertydef name="port" type="integer" value="6120"/>
|
4. Changing Activation Files
The following changes will change the
specified position of these setting files.
- % copy ${SOBA}\startpeerApp.bat
${SOBA}\startpeerApp2.bat
- The copied ${SOBA}\startpeerApp2.bat
should be changed as follows.
Before the change
@set SOBA_HOME=.\home\system
@set USER_HOME=.\home\user |
After the change
@set SOBA_HOME=.\home2\system
@set USER_HOME=.\home2\user |
5. Activation
Activate the two frameworks with
these:
% ${SOBA}\startpeerApp.bat
% ${SOBA}\startpeerApp2.bat
|
User Support
