Testing chuiWeb on MAJIC server: 1. Create on your home directory the following structure: ~/testing /majic /build /lib /run /server /p2j /build /lib 2. Download the MAJIC jar files to ~/testing/majic/build/lib $ scp -P 2224 $USER@localhost:~/testing/majic/build/lib/*.jar ~/testing/majic/build/lib/ 3. Download MAJIC server configuration files from ~/testing/majic/run/server You may download the entire folder which take some time: $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/* ~/testing/majic/run/server/ Or you can download only some specific files $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/*-directory.xml ~/testing/majic/run/server/ $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/*_server.xml ~/testing/majic/run/server/ $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/*.store ~/testing/majic/run/server/ $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/*.sh ~/testing/majic/run/server/ $ scp -P 2224 $USER@localhost:~/testing/majic/run/server/*.properties ~/testing/majic/run/server/ 4. Build p2j project than the spawner and copy all the files from $P2J_HOME/build/lib to ~/testing/majic/p2j/build/lib $ ant all (jar) $ ant -Dhave.pam=yes -Dpost.build=yes native $ cp -r -v $P2J_HOME/build/lib/ ~/testing/majic/p2j/build/lib 5. Go to ~/testing/majic/run/server $ cd ~/testing/majic/run/server 6. Open the file gso-directory.xml using your preferred text editor and do the following changes: a.) Change PostgreSQL port number. Go to the following node. Replace the with 25432. You already have a ssh tunnel when you run the gcd_remote.sh script which allow you to access the remote postgres server using the local port 25432. You can check by trying to connect to the postgres server using the pgAdmin GUI tool using: Host: localhost Port: 25432. Username and Password are listed on gso-directory.xml. b.) Add gso server to the acl/admin/001300 node subjects list: ... ... NOTE: This settings are for gso server on which the tests has been done. For other servers you should add also the name of specified server. Example: ... ... ... c.) Add chuiWeb node. At least the chuiWeb node must contains the enabled attribute set to true. If enabled node is missing or it value is false the chuiWeb is not available. ... Default values are provided for missing attributes (see ClientBuilderOptions and TerminalOptions). The default values are suitable for testing purposes only and you are able to spawn web clients only for user account on which the P2J server is running. The values from directory override the default values. On production some files should be shared by all accounts. A complete node should looks as follow: d.) Add rights to access Spawn interface via RemoteObject protocol /server/security/acl/net/00240: ... ... ... ... e.) Save your changes and exit from editor. 7. From the same location start the server. $ ./server.sh 8. Wait until the sever is ready. Check the server.log file from time to time: $ tail server.log until you'll see the following message: [12/23/2013 11:06:50 EET] (SessionManager.listen():INFO) {00000000:00000001:gso} Server ready or an error message if the server cannot be started for some reasons. 9. When the server is ready open the following URL on your web browser (Firefox): https://localhost:/chui Where the is the GSO admin port usually 7673. The is also listed on the gso-directory.xml file.