Java CAPS Technical Tips

CommandlineCodeGen Debugging Tricks

2008-10-29T18:33:00.002+13:00

If you need to get debugging level logging for the commandlinecodegen under both Windows or Linux, then change the log4j.properties in this file:

$CODEGEN_HOME/compile/lib/ext/log4jProperties.jar

Then modify the first line to be DEBUG instead of ERROR.

Activating the debug mode in eDesigner

2008-10-29T11:05:00.004+13:00

Edit the %EDESIGNER_HOME%/bin/runed.bat file and search for the line that contains

-J-Drun.mode=run

And change it to

-J-Drun.mode=debug

Also, in the same folder edit the log4j.properties rootLogger.
Change it from ERROR to DEBUG.

Restart your eDesigner.

You can find the log file in %EDESIGNER_HOME%/userdir/system/ide.log

SAP CommandLinceCodegen in Linux... Oh dear...

2008-09-30T20:59:00.008+13:00

Update: This problem has been fixed in Java CAPS 5.1.3 Update 3

I'm getting this error in the log when I'm trying to compile my project that makes use of the BAPI eWay:


[CODELET] com.stc.otd.codegen.OtdCodeGenException: javaClass: BapiOtdGenerator.validateSapJars(): The following .jar file(s) need to be part of the JVM environment before source code can be compiled:  sapjco.jar.  See documentation for more information.
[CODELET]     at com.stc.sapbapi.codegen.bapi.BapiOtdGenerator.validateSapJars(BapiOtdGenerator.java:233)
[CODELET]     at com.stc.sapbapi.codegen.bapi.BapiOtdGenerator.compile(BapiOtdGenerator.java:170)
[CODELET]     at com.stc.sapbapi.codegen.bapi.BapiOtdGenerator.generate(BapiOtdGenerator.java:312)
[CODELET]     at com.stc.otd.codegen.BaseGenerator.generate(BaseGenerator.java:255)
[CODELET]     at com.stc.sapbapi.codegen.SAPEWayCodeletBase$OutboundCodelet$SAPOutboundJCECodelet.generateOtdJarFile(SAPEWayCodeletBase.java:873)
[CODELET]     at com.stc.sapbapi.codegen.SAPEWayCodeletBase$OutboundCodelet$SAPOutboundJCECodelet.generateFiles(SAPEWayCodeletBase.java:924)
[CODELET]     at com.stc.codegen.anttaskImpl.driver.CodeletProcessor.execute(CodeletProcessor.java:89)
[CODELET]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[CODELET]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[CODELET]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[CODELET]     at java.lang.reflect.Method.invoke(Method.java:585)
[CODELET]     at com.stc.codegen.anttaskImpl.CodeGenAntTaskImpl.execute(CodeGenAntTaskImpl.java:117)
[CODELET]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[CODELET]     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
[CODELET]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[CODELET]     at java.lang.reflect.Method.invoke(Method.java:585)
[CODELET]     at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[CODELET]     at org.apache.tools.ant.Task.perform(Task.java:348)
[CODELET]     at org.apache.tools.ant.Target.execute(Target.java:357)
[CODELET]     at org.apache.tools.ant.Target.performTasks(Target.java:385)
[CODELET]     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[CODELET]     at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
[CODELET]     at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[CODELET]     at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
[CODELET]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[CODELET]     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
[CODELET]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[CODELET]     at java.lang.reflect.Method.invoke(Method.java:585)
[CODELET]     at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[CODELET]     at org.apache.tools.ant.Task.perform(Task.java:348)
[CODELET]     at org.apache.tools.ant.Target.execute(Target.java:357)
[CODELET]     at org.apache.tools.ant.Target.performTasks(Target.java:385)
[CODELET]     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[CODELET]     at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[CODELET]     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[CODELET]     at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[CODELET]     at org.apache.tools.ant.Main.runBuild(Main.java:698)
[CODELET]     at org.apache.tools.ant.Main.startAnt(Main.java:199)
[CODELET]     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[CODELET]     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

Whenever you have a classpath problem with ant, run the ant command with the -diagnostics flag.

Here is what I get ("." represents irrelevant stuff that I've removed):


$ /export/apache-ant-1.7.0/bin/ant -verbose -lib compile/lib/ext -Dcommandline.dir=. -propertyfile /export/scripts/buildProps/p2pd/build.SEP_CAS_FirstContDate.properties -diagnostics
.
.
.
-------------------------------------------
ANT_HOME/lib jar listing
-------------------------------------------
.
.
.
sapjco.jar (304078 bytes)
.
.
.
-------------------------------------------
USER_HOME/.ant/lib jar listing
-------------------------------------------
.
.
.
sapjco.jar (304078 bytes)
.
.
.
java.class.path : /export/apache-ant-1.7.0/lib/ant-launcher.jar:/export/commandlinecodegen/compile/lib/ext/ldap.jar:/export/commandlinecodegen/compile/lib/ext/com.stc.antlrimpl.jar:/export/commandlinecodegen/compile/lib/ext/sapjco.jar:/export/commandlinecodegen/compile/lib/ext/openide.jar:/export/commandlinecodegen/compile/lib/ext/log4jProperties.jar:/export/commandlinecodegen/compile/lib/ext/commons-logging.jar:/export/commandlinecodegen/compile/lib/ext/log4j.jar:/export/commandlinecodegen/compile/lib/ext:/home/eaiadmin/.ant/lib/sapjco.jar:/export/apache-ant-1.7.0/lib/ant-jai.jar:/export/apache-ant-1.7.0/lib/ant-antlr.jar:/export/apache-ant-1.7.0/lib/ant-starteam.jar:/export/apache-ant-1.7.0/lib/ant-jdepend.jar:/export/apache-ant-1.7.0/lib/ant-apache-oro.jar:/export/apache-ant-1.7.0/lib/ant-trax.jar:/export/apache-ant-1.7.0/lib/ant-apache-regexp.jar:/export/apache-ant-1.7.0/lib/ant-jmf.jar:/export/apache-ant-1.7.0/lib/ant-jsch.jar:/export/apache-ant-1.7.0/lib/ant-apache-bsf.jar:/export/apache-ant-1.7.0/lib/ant-netrexx.jar:/export/apache-ant-1.7.0/lib/ant-swing.jar:/export/apache-ant-1.7.0/lib/sapjco.jar:/export/apache-ant-1.7.0/lib/xercesImpl.jar:/export/apache-ant-1.7.0/lib/ant-apache-bcel.jar:/export/apache-ant-1.7.0/lib/ant-stylebook.jar:/export/apache-ant-1.7.0/lib/ant-javamail.jar:/export/apache-ant-1.7.0/lib/ant-junit.jar:/export/apache-ant-1.7.0/lib/ant-commons-net.jar:/export/apache-ant-1.7.0/lib/ant-commons-logging.jar:/export/apache-ant-1.7.0/lib/ant-weblogic.jar:/export/apache-ant-1.7.0/lib/ant-apache-log4j.jar:/export/apache-ant-1.7.0/lib/ant.jar:/export/apache-ant-1.7.0/lib/xml-apis.jar:/export/apache-ant-1.7.0/lib/ant-nodeps.jar:/export/apache-ant-1.7.0/lib/ant-testutil.jar:/export/apache-ant-1.7.0/lib/ant-launcher.jar:/export/apache-ant-1.7.0/lib/ant-apache-resolver.jar:/export/jdk1.5.0_15/lib/tools.jar
.
.
.

So the sapjco.jar is definitely on the classpath. But why are we getting this error then:


com.stc.otd.codegen.OtdCodeGenException: javaClass: BapiOtdGenerator.validateSapJars(): The following .jar file(s) need to be part of the JVM environment before source code can be compiled:  sapjco.jar.  See documentation for more information.

In this case we should have a look at the underlying validation mechanism. This is a bit naughty... don't tell your boss. ;)

I use this command to find the jar that contains the BapiOtdGenerator class.


for jar in $(find /export/commandlinecodegen -name "*jar"); do unzip -l $jar|grep BapiOtdGenerator; if [ $? == 0 ]; then echo $jar; fi; done

After that "jad" can be quite helpful.
http://www.kpdus.com/jad.html

Have a look at the validateSapJars method in the resulting BapiOtdGenerator.jad file.

A while back I posted about my frustration of not being able to use the eWay Development Kit under Linux. The reason I was not able to use is was that the developer of the eDK has hard coded all directory paths to use "\" instead of "/". Well, really he should have used java.io.File.pathSeparator. Here we have a very similar problem of developers never being exposed to the world of Linux.

The method in question uses the StringTokenizer class to split the classpatch by ";". Well, that will of course only work on Windows, because Linux uses ":". So no matter where I put the sapjco.jar the validation will never succeed. How unfortunate.

Since the commandlinecodegen is supported on Linux I have no doubt that this bug will be fixed. It's pretty easy to fix after all. In fact, java.lang.System.getProperties() will give you the right value that is needed.

The thing that annoys me the most is that Java was meant to be platform neutral.

So, no commandlinecodegen in Linux for BAPIs then I guess...

SAP Enabling the Commandline Codegen (Linux) (5.1.3)

2008-09-30T19:31:00.007+13:00

I had previously posted about debugging JCo problems with Java CAPS here:
http://jcapsblogger.blogspot.com/2007/11/what-to-do-if-you-have-issues-with-jco.html

Now I will extend this method to include the commandline codegen tool for Java CAPS.

First of all, a brief refresher on how to get the commandline codegen to work.
You MUST use a JDK that is version 5, otherwise your builds won't succeed.
Your ant version should be version 1.7.

A sample build.properties file looks like this:


commandline.rep.url=http://eaiutil4.ird.govt.nz:12000/rv2
commandline.rep.user=codegen
commandline.rep.pass=codegen
commandline.rep.dir=localrepository
commandline.rep.projectName=CORE/util/PingWebClient/dp
commandline.rep.projectDeployName=dpPingWebClient
commandline.rep.projectDeploymentTag=
commandline.rep.projectBranchName=
commandline.esr.select=
commandline.esr.ignore=

No let us install the JCo stuff.

Copy the sapjco.jar to ~/.ant/lib
Copy the librfccm.so and libsapjcorfc.so into $JDK_HOME/jre/lib/i386.

WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!!
DOES NOT WORK!!!
WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!!

Read next blog post to find out why.

Update from Mon, 27 October, 2008: This problem has been fixed in Java CAPS 5.1.3 Update 3, so the above instructions will now work.

stop_domain1.sh enhancement

2008-09-29T13:24:00.005+13:00

Sometimes it happens that the stop_domain1.sh script fails because some JVM setting was not done right.

It is then necessary to kill -9 all processes belonging to the Java CAPS Domain.

This script will automatically kill the domain if the default shutdown command fails.


#!/bin/sh

INSTALL_DIR=/home/syk4/JavaCAPS513/logicalhost/is
DOMAIN_NAME=domain1


"$INSTALL_DIR/bin/isadmin" stop-domain $* $DOMAIN_NAME

# Added by sebastian.krueger@ird.govt.nz
# 0 == ok
# 1 == broken

if [ $? == 1 ]; then
        echo
        echo "Killing the Domain by force!!"

        for job in `ps ax|egrep 'isprocmgr_domain1|is_domain1|domain1.*stcms.exe'|grep -v grep|awk '{print $1}'`; do kill -9 $job; done
fi

To install this script edit the $DOMAIN_HOME/lib/stopdomain.sh.template to look like this:


#!/bin/sh

INSTALL_DIR=$INSTALL_DIR$
DOMAIN_NAME=$DOMAIN_NAME$

"$INSTALL_DIR/bin/isadmin" stop-domain $* $DOMAIN_NAME

# 0 == ok
# 1 == broken

if [ $? == 1 ]; then
       echo
       echo "Killing the Domain by force!!"

       for job in `ps ax|egrep 'isprocmgr_$DOMAIN_NAME$|is_$DOMAIN_NAME$|$DOMAIN_NAME$.*stcms.exe'|grep -v grep|awk '{print $1}'`; do kill -9 $job; done
fi

Java CAPS TimeZone Update for JVM

2008-09-29T12:20:00.003+13:00

In New Zealand we changed to Summer Time yesterday.

After this change I found that several of our SUSE Linux Enterprise Servers had incorrect time (when using the "date" command).

After applying a patch from novell.com to fix this issue I found that the date command was now returning the correct time, but my Java CAPS logs were still on Winter Time.

I then found that this is a bug with the JVM.
For more info on this look here:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102836-1

You can fix it by downloading the Timezone Updater Tool from here:
http://java.sun.com/javase/tzupdater_README.html

Run the tzupdater.jar with the jre that is supplied with the domain. This will then update the timezone data for your domain and your logs will show the correct time.

Use the following one-liner in bash to apply the patch to all local jvm's:

for java in `find . -name java -type f -perm /+x`; do echo $java; $java -jar ~/tzupdater.jar -t; done

projectExport/Import Trap for young players

2008-09-10T20:10:00.002+12:00

In Linux, if you run the exportProject.sh script (tested in 5.1.3 and 6.0.0) you get the following documentation:

./exportProject.sh
Usage: To export Projects/Environments, type in

exportProject.sh {username} {password} {branch name} {export file} {project paths} {environment paths}

To export both projects and environments:
eg. exportProject.sh user pwd "" /usr/jcaps/export.zip "Project1+Project2/SubProject" "Env1+Env2"

To export only projects:
eg. exportProject.sh user pwd "" /usr/jcaps/export.exp "Project1+Project2/SubProject" ""

To export a project from a given version control branch:
eg. exportProject.sh user pwd "BranchName" /usr/jcaps/export.exp "Project1" "Env1"

So you would then expect that the following should work:

./exportProject.sh Administrator STC "" /export/backup.zip "Project1" ""

However, that will just return an error message. You need to specify the "Branch". If you want to use the default branch, then you need to specify "HEAD" as the branch name.

Like so:

./exportProject.sh Administrator STC "HEAD" /export/backup.zip "Project1" ""

Then it will work.

When you to the importProject.sh you don't need to specify the "HEAD" though. Strange.

Recurring tasks after installing a new logicalhost in 5.1.3

2008-09-08T19:07:00.000+12:00

Often I've found myself having to apply the same JVM settings to all my domains that I create. This I looked for a way to change the JMV settings via commandline tools. The solutions that I found was to use the isadmin command that is part of the Java CAPS 5.1 Logicalhost.

The script below takes care of my classpath settings, my JVM settings, changing my Administrator password to something less well known than "STC", and ensures that duplicate stack traces are printed in the server.log.

Maybe it's useful to you.

setupDomain.sh


#!/bin/bash

function displayHelp() {

        echo
        echo "Usage: setupDomain.sh -s <server> -p <basePort> -d <domainName>"
        echo

        echo "This script will setup a running domain. The following configurations will be made:"
        echo
        echo "  - set server.java-config.classpath-suffix=/some/directory:/some/directory/someFile.jar"
        echo "  - set server.log-service.property.print-dup-stack-trace=true"

        echo "  - delete-jvm-options -- -Xmx512m"
        echo "  - create-jvm-options -- -Xmx1536m"
        echo "  - create-jvm-options -- -Xmn256m"

        echo "  - create-jvm-options -XX:+UseParallelGC"
        echo "  - create-jvm-options -XX:PerfDataSamplingInterval=500"
        echo "  - create-jvm-options -XX:+DisableExplicitGC"

        echo "  - create-jvm-options -XX:MaxPermSize=512m"
        echo "  - update-file-user --userpassword foo --groups asadmin Administrator"
        echo "  - bounce the domain"

        echo
        exit
}

lhHome=/export/logicalhost

if [ "$1" == "" ]; then
        displayHelp

fi

while getopts ":s:d:p:" optname
do
        case "$optname" in

        s)
                server=$OPTARG
                ;;
        d)

                domainName=$OPTARG
                ;;
        p)
                port=$OPTARG

                ;;
        *)
                displayHelp
                ;;
        esac

done
shift $(($OPTIND -1))

echo

echo "Setting CLASSPATH-SUFFIX for $server $domainName on port $port"
$lhHome/is/bin/isadmin set --host $server --port $port server.java-config.classpath-suffix=/some/directory:/some/directory/someFile.jar

echo
echo "Setting print-dup-stack-trace for $server $domainName on port $port"
$lhHome/is/bin/isadmin set --host $server --port $port server.log-service.property.print-dup-stack-trace=true

echo
echo "Setting jvm options"
$lhHome/is/bin/isadmin delete-jvm-options --host $server --port $port -- -Xmx512m

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -- -Xmx1536m

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -- -Xmn256m

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -XX\\:+UseParallelGC

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -XX\\:PerfDataSamplingInterval=500

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -XX\\:+DisableExplicitGC

$lhHome/is/bin/isadmin create-jvm-options --host $server --port $port -XX\\:MaxPermSize=512m

echo
echo "Changeing Administrator password"
$lhHome/is/bin/isadmin update-file-user --host $server --port $port --userpassword foo --groups asadmin Administrator

echo
echo "Bouncing $server $domainName"
ssh $server "/export/entlh/logicalhost/stop_${domainName}.sh && /export/entlh/logicalhost/start_${domainName}.sh"

Why is there no deleteDomain.sh in a 5.1.3 Linux Logicalhost?

2008-09-08T18:22:00.000+12:00

Put this script in the same directory where the createdomain.sh script is (ie, the folder where you have untarred the logicalhost.tar.gz).

deleteDomain.sh


#!/bin/bash

help() {

        echo
        echo "Usage: $(basename $0) [--dname <domain_name>] [--help]"
        echo
        echo "where:"

        echo "  --dname         domain name, default \"domain1\""
        echo "  --help          prints this help message"
        echo

        exit
}

if [ "$1" == "--help" ]; then

        help
fi

if [ "$1" == "--dname" ]; then

        if [ "$2" == "" ]; then
                help

        else
                domainName=$2
        fi
fi

if [ "$1" == "" ]; then

        domainName=domain1
fi

$(ps ax|grep -E "[i]sprocmgr_$domainName|[i]s_$domainName|$domainName.*[s]tcms.exe">/dev/null)

if [ $? == 0 ]; then
        echo "Please shutdown the Domain first."

        echo
        exit
fi

dir=$(dirname $0)

echo "Removing start_$domainName.sh"
rm $dir/start_$domainName.sh > /dev/null

echo "Removing stop_$domainName.sh"
rm $dir/stop_$domainName.sh > /dev/null

echo "Removing is/domains/$domainName directory"
rm -r $dir/is/domains/$domainName > /dev/null

when was that ear file built?

2008-08-28T16:25:00.000+12:00

I often ask myself when a particular deployed ear file was build, ie what version of code has been deployed. Luckily, every EAR file that is build in JavaCAPS 5.1.3/6 contains various useful details.

Here an example of the MANIFEST.MF:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 1.5.0_15-b04 (Sun Microsystems Inc.)
CAPS-Version: 5.1.3

Name: Application Information
CAPS-Build-Time: 2008-08-26T02:09:23 +1200
CAPS-Deployment-Profile-Name: dpPingWebClient, Version 1.4
CAPS-Project-Name: CORE/util/PingWebClient/dp
CAPS-Integration-Server-Name: is192.168.1.1
CAPS-Logical-Host-Name: lh192.168.1.1

The CAPS-Build-Time is particularly useful and I wrote a script which will extract these values for me. I use ssh-keys so that I am not prompted for passwords when I log onto any server via ssh.


#!/bin/bash

function displayHelp() {

        echo
        echo "Usage: checkManifest.sh -s <server> [-d <domainName>] [-p <dpName>]"
        echo

        echo "This script will disply the manifest files for deployed projects."
        echo "if only -s <server> is provided, ever deployed manifest file is displayed"
        exit
}

# modify if you didn't install the logicalhost in the default locations
basePath=/export/entlh/logicalhost
deploycli=/export/deploycli/deploycli.sh

sshkey=id_rsa
JAVA_HOME=/export/jdk1.5.0_15

export JAVA_HOME

# if no arguments, print help
if [ "$1" == "" ]; then

        displayHelp
fi

while getopts ":s:d:p:" optname
do
        case "$optname" in

        s)
                server=$OPTARG
                ;;
        d)

                domainName=$OPTARG
                ;;
        p)
                dpName=$OPTARG

                ;;
        *)
                displayHelp
                ;;
        esac

done
shift $(($OPTIND -1))

# if domain name is empty, use default domain name

if [ "$domainName" == "" ]; then
        domainName=domain1

fi

if [ "$dpName" == "" ]; then

        for dpName in `$deploycli -host $server list|grep ^EAR|awk '{print $2}'`
        do

                echo "----------------------------------------------------------"
                echo "Manifest for deployment profile $dpName"
                echo
                ssh -i ~/.ssh/$sshkey $server "cat $basePath/is/domains/$domainName/applications/j2ee-apps/$dpName/META-INF/MANIFEST.MF"

                #echo -n "Press <ENTER> to continue, <CTRL-C> to quit"
                #read
                echo
        done

else
        echo "----------------------------------------------------------"
        echo "Manifest for deployment profile $dpName"
        echo
        ssh -i ~/.ssh/$sshkey $server "cat $basePath/is/domains/$domainName/applications/j2ee-apps/$dpName/META-INF/MANIFEST.MF"

fi

Maintaining a Java CAPS Repository Server

2008-08-02T14:29:00.000+12:00

As Java CAPS repositories grow in size, they become more unstable and are prone to corruptions.

It is best practice to do regular backups of your repository.

JavaCAPS provides several useful tools in order to automate a regular backup regime.

$REPOSITORY_HOME/repository/util/backup.sh

This script will make a complete backup of your repository. This includes all your source history as well. However, if you do a restore, then you need to restore the entire repository.

$REPOSITORY_HOME/repository/util/exportProject.sh

This script will make a shallow backup of the latest source code for selected projects only. If you do a restore, you loose all your source history, but for that you do not have to rollback the entire repository.

I recommend a combination of both the backup.sh as well as the exportProject.sh.

Here is a script that I use to backup several repositories ever midnight via cron.


#!/bin/bash

date2stamp () {

    date --utc --date "$1" +%s

}

stamp2date (){
    date --utc --date "1970-01-01 $1 sec" "+%Y-%m-%d %T"

}

dateDiff (){
    case $1 in

        -s)   sec=1;      shift;;
        -m)   sec=60;     shift;;

        -h)   sec=3600;   shift;;
        -d)   sec=86400;  shift;;

        *)    sec=86400;;
    esac
    dte1=$(date2stamp $1)

    dte2=$(date2stamp $2)
    diffSec=$((dte2-dte1))

    if ((diffSec < 0)); then abs=-1; else abs=1; fi

    echo $((diffSec/sec*abs))
}

echo
echo "----------------------------------------------------------"
echo "Script started at: $(date)"
echo "----------------------------------------------------------"
start=$(date +%T)

echo

# run backups
echo "Starting backups"
/export/JavaCAPS513/p2p-repository/repository/util/backup.sh Administrator STC /export/JavaCAPS513/p2p-repository/backups/p2p-backup-$(date +%Y_%m_%d_%H_%M_%S).zip

/export/JavaCAPS513/rv2-repository/repository/util/backup.sh Administrator STC /export/JavaCAPS513/rv2-repository/backups/rv2-backup-$(date +%Y_%m_%d_%H_%M_%S).zip

/export/JavaCAPS6/repository/repository/util/backup.sh Administrator STC /export/JavaCAPS6/repository/backups/jcaps6-backup-$(date +%Y_%m_%d_%H_%M_%S).zip

echo

# run project exports
echo "Starting project exports"
/export/JavaCAPS513/rv2-repository/repository/util/exportProject.sh Administrator STC HEAD /export/JavaCAPS513/rv2-repository/backups/rv2ProjectExport-$(date +%Y_%m_%d_%H_%M_%S).zip CORE+EBP+EP envArchipelago

echo

# validate repositories
# Note by Sebastian: This appears not to be worth anything...
#echo "Starting Repository validation"
#/export/JavaCAPS513/p2p-repository/repository/util/validate.sh Administrator STC
#/export/JavaCAPS513/rv2-repository/repository/util/validate.sh Administrator STC
#/export/JavaCAPS6/repository/repository/util/validate.sh Administrator STC
#echo

# cleaup old backups
echo "Starting cleaup of old backups"
find /export/JavaCAPS513/p2p-repository/backups -name "p2p-backup-*.zip" -ctime 30|xargs rm 2>/dev/null

find /export/JavaCAPS513/rv2-repository/backups -name "rv2-backup-*.zip" -ctime 30|xargs rm 2>/dev/null

find /export/JavaCAPS513/rv2-repository/backups -name "rv2ProjectExport-*.zip" -ctime 30|xargs rm 2>/dev/null

find /export/JavaCAPS6/repository/backups -name "jcaps6-backup-*.zip" -ctime 30|xargs rm 2>/dev/null

echo
stop=$(date +%T)
echo "Elapsed total time is $(dateDiff -m $start $stop) in minutes"

echo

This script is then triggered every midnight via cron like so:

0 0 * * * /export/scripts/maintainServer.sh > /export/scripts/maintainServer.log

I hope to add some email functionality later to alert me of any failures.

Passed the Sun Certified JavaCAPS Integrator

2008-05-22T10:38:00.000+12:00

I just got back from taking the JavaCAPS Integrator Exam (yes, I passed. ;-).

60 Questions, 2 hours, passing score at 70%.

According to the exam results page, the exam covers the following topics:

- ICAN
- eGate (weighting: 40%)
- eInsight (weighting: 40%)
- eVision (weighting: 20%)
Note: I invented the weighting myself, based on the exam I just took. Your exam might be a little different.

I do not recall a single ICAN specific question, so am confused about what an ICAN question is.

Overall, everyone that has used Java CAPS for 6 months or more "full-time" and has used eGate and eInsight should be able to pass the exam.

What the exam does not cover:
- Worklist Manager
- eBAM
- JMS Grid
- Java CAPS security
- specific knowledge of WSDLs
- Java specific questions. Questions are on usage of JCDs.
- BPEL specific questions. Questions are on usage of eInsight.
- eInsight persistence
- performance tuning questions
- eWay specifics (just know that they are provided as OTDs). Only the JMS OTD is covered in the exam. General Database OTD questions are covered. But nothing specific to Oracle or SQL Server eWay.

There were particularly no particularly difficult questions on eVision. If you know what a Page Flow, Page Layout, and Page Link is then that is enough to get 100% for that topic. There were no questions on charts, dynamic tables, and eVision security.

My tip for passing this section is to create a few basic page layouts before the exam and you should have no trouble. Know how to link pages together with the event-based decision modeling component. Read the first half of the eVision User Guide and you'll be sorted.

There were several difficult questions in the eInsight topic. This topic covered:
- exception handling

Know the different types of exception handlers. How they are attached to scopes (Note: Process Level Exception Handlers are not!).

- compensation handling

Know how to create compensation handlers, and how to use the Compensate Activity.

- correlations

There were no detailed questions here, but an understanding of correlations and how to create them is important.

- business rules

Two different types. Inline, and as separate Business Rule Activity.

- timer events
- event-based decisions

Know when and how to use these in eInsight. How do you use these in combination with correlations?

Finally, the eGate topic required knowledge of all Java CAPS architectural components. That is:
- Repository
- eDesigner
- LogicalHost/Domain/JMS Server
- UDDI Server
- Enterprise Manager
- Various commandline tools such as em-cmdline-tool, deploycli, commandlinecodegen
- eGate API Kit (just know what it is used for, not necessarily "how" to use it)
- eWays specifics

Of the top of my head, the following might be useful:
Understand the function of the Repository. All different ways to create and use OTDs. There are two different types of OTDs. How to access documentation. How use the marshall/unmarshall functions in JCDs and BPs. The function of the "Sun Seebeyond" folder in eDesigner. All means for monitoring a domain. The difference between an External Application and an External System. How to change configuration of a domain. Know the difference between Logicalhosts/Domains. What is the Product_List.sar used for? Understand the relationship between Connectivity Map and Deployment Profile. Know the the methods used for the JMS OTD and how to use them.

Hope this is of use to people. This exam is not very hard, but one should be prepared.

Disclaimer: I have taken this exam once, so there are probably 100s of questions that I did not see, so don't know about. I don't guarantee anything. Any information provided in this posting is at your own risk. Take the exam at your own risk.

Good luck. :)

eWay Development Kit Problems

2008-05-11T23:11:00.000+12:00

I was just trying to get the eWay Development Kit (version 5.1.1) going the other day. And was rather disappointed.

The GUI only saves the eWay configuration once, and after that any changes are lost, even if you hit save again and again. Somehow, they are not written to the xml configuration. Also, when choosing the data types for input and outputs of the eWay from the gui and navigate to a different tab in the gui, the data type is lost. I haven't been able to determine the reason for this, but if i try it repeatedly it will work at some point. But developing an eWay that you then can't save, is not much use.

If the XML configuration is not saved, then the method templates are not completed in the generated code.

Also, I use Linux as my primary OS and try to do as much as possible under it. The eWay Dev Kit is written in Java, so there should be no reason why it doesn't work under Linux. However, the developer of the GUI decided to hard code path strings like this: "foo\bar\baz.xml". Thereby totally removing any form of portability. Apart from the fact that Windows also works with "/" as a path separator (and not to mention the java.io.File.pathSeparator static field). Somehow the whole point of Java was missed somewhere along the lines.

I have a ticket open with support on the eWay dev kit, but was told that so far, no one has reported the bug of not being able to save to the xml configuration file. So I am left with two options:
1. My computer has something wrong. Although it can save the first time you hit the save button. Just not again.
2. The eway dev kit has a bug. And there are no other customer out there that use the eway dev kit version 5.1.1 (hence the bug is unknown to support).

We wrote a few connectors ourselves as jar files and I was curious to see if they could be converted to integrate better with eDesigner.

I would recommend writing your connector in Eclipse or Netbeans and exporting it as a jar file.

That jar file can then be imported into a JCD. That JCD could be triggered by a JMS message for example. You could also include this JCD into your business process (eInsight). This will work for outbound messages.

For inbound messages you may have to improvise. You could consider pooling on a specified interval (use the Java CAPS Scheduler as a trigger for a JCD or BP).
For more esoteric requirements, consider the eGate API Kit (Documentation here). Or consider receiving messages through the TCP/IP eWay and develop a custom protocol that suits your needs.

Screencast on Application Configuration in Java CAPS 6

2008-05-09T23:47:00.000+12:00

Excellent screencast by Frank Kieviet.

watch it here

A review of the configuration models in Java CAPS 5.1, EJB 3, pure JBI, and repository-based projects in Java CAPS 6.

Java CAPS book is available

2008-05-09T08:37:00.000+12:00

The Java CAPS book that Michael Czapski and friends wrote is now available for order/delivery.

by it on amazon

Some Tips on Following Java CAPS News

2008-04-14T14:29:00.000+12:00

I use Google Reader to follow Java CAPS related info on the web. I thought I might share a few feeds that I follow.

Blogs that mention Java CAPS:

http://blogs.sun.com/lerognon/
http://blogs.sun.com/jcapsuser/
http://blogs.sun.com/javacapsfieldtech/
http://camelcase.blogspot.com/
http://blogs.sun.com/cye/
http://vincentfazio.blogspot.com/
http://blogs.sun.com/fkieviet/
http://blogs.sun.com/fredaabedi/
http://blogs.sun.com/kkranz/
http://blogs.sun.com/gopalan/
http://blogs.sun.com/kevinschmidt/
http://blogs.sun.com/openmessagequeue/
http://blogs.sun.com/sweber/
http://soa4real.blogspot.com/
http://blogs.sun.com/toxophily/
http://blogs.sun.com/catalysts/
http://planets.sun.com/SOABI/group/blogs/

A while back Sun created project containers for some of the Java CAPS components. Not much happening on these sites really, but it doesn't harm to follow them in an rss reader.

https://jcaps-b2b.dev.java.net/servlets/ProjectNewsRSS
https://jcaps-rfid.dev.java.net/servlets/ProjectNewsRSS
https://open-b2b.dev.java.net/servlets/ProjectNewsRSS
https://jmsjca.dev.java.net/

A great way of knowing about good links is to follow del.icio.us tag feeds.

http://del.icio.us/tag/jcaps
http://del.icio.us/tag/seebeyond
http://del.icio.us/tag/suncaps

Any recommended Java CAPS related blog posts?

http://technorati.com/tag/Java+CAPS
http://technorati.com/tag/JCAPS

Anyone twittering on Java CAPS? (You wouldn't believe it, but it does happen...)

http://tweetscan.com/rss.php?s=java+caps
http://tweetscan.com/rss.php?s=jcaps

Forums:

http://eai.ittoolbox.com/groups/technical-functional/seebeyond-l
http://forum.java.sun.com/forum.jspa?forumID=882

You can also configure Google Alerts if you are interested in specific topics.

http://www.google.co.nz/alerts

Update: I forgot to mention that there are is a Facebook group that is Java CAPS related.

http://www.facebook.com/group.php?gid=17757823536 (Sun CAPS Champions)

Java CAPS on Linux on VMWare and the Evil Timing Problems

2008-04-02T16:57:00.000+13:00

We use VMWare ESX 3.5 and Suse Linux Enterprise Server 10.1 x86 for the guests.

If you find that your clock is going way out of sync with reality, then you may want to consider the following as a solution.

Upgrade to SLES 10.2. I've tested a beta of this and found that the timing issue has been resolved. Novell backported some kernel code that resolves the VMWare timing issue. You'll have to wait until it gets released though. I think next month sometime?

If you are stuck on SLES 10.1, then do the following:
- ensure you have VMWare Tools installed and make sure you have VMWare Tools Host Clock Synchronization turned on.
- install NTP as well.
- if you are in New Zealand, you'll want the latest patches for the daylight-savings changes.
  https://secure-support.novell.com/KanisaPlatform/Publishing/931/3094409_f.SAL_Public.html
- You'll also have to set the following kernel parameters in your /boot/grub/menu.lst

The Geek Quiz

2008-03-28T16:31:00.000+13:00

Ha! How much do you have?

100% Geek

JavaCAPS 6 On Linux

2008-03-26T14:46:00.001+13:00

Finally we have a version of Java CAPS that will work under Linux.

See snapshots:

A note about log levels

2008-03-25T02:44:00.002+13:00

It is generally best practice to set development related log messages to a "debug" level.

Java CAPS as of version 5.1 has switched logging form log4j (from the old SeeBeyond ICAN days) to java.util.logging. This means that the following log level are available:

Finest, Finer, Fine, Config, Info, Warning, Severe, Off

However, the com.stc.codegen.logger.Logger class that is available in a JCD for logging still makes use of the old log4j levels which are:

debug, info, warn, error, fatal

The mappings are as follows:

debug -> Fine
info -> Info
warn -> Warning
fatal -> Severe

If you make use of the logger.debug method in a JCD, you would then have to add a log level like such:

STC.eGate.CMap.Collabs -> Fine
or
STC.eGate.CMap.Collabs.baseProjectFolderOfDeploymentProfile.svcNameFromCM -> Fine

The former being a generic definition, and the latter being a more specific definition.
So if your deployment project is in /Foo/Bar/Project1/dep then the "baseProjectFolderOfDeploymentProfile" would be "dep".

For BPEL, set the com.stc.bpms.bpelImpl.runtime.Interpreter level to Fine.

This can be set either by editing the log level in the domain.xml and then restarting the Domain, or you can set the log levels in the Domain Web Administration Interface (Default: http://localhost:18000)

Script to change JVM Flags for Java CAPS 5.1.2

2008-03-20T16:34:00.000+13:00

Here an extract from a Linux BASH script that will set up some JVM parameters from the commandline. I've found these flags work quite well for an Linux Intel box with 2 GB of RAM.

# append generated CLASSPATH to domain
for i in host01 host02 host03
do
   echo "Resetting CLASSPATH for domain $server"
   # Note: to find other configs available:
   # get server.java-config.*
   ssh $server "$logicalhostPath/is/bin/isadmin set server.java-config.server-classpath=$cpDefault$cpAppend"
   ssh $server "$logicalhostPath/is/bin/isadmin delete-jvm-options -- -Xmx512m"
   ssh $server "$logicalhostPath/is/bin/isadmin create-jvm-options -- -Xmx1536m"
   ssh $server "$logicalhostPath/is/bin/isadmin create-jvm-options -- -Xmn256m"
   # Note: This is bizarre.
   # isadmin needs to escape the : with a \, so -> \:
   # isadmin needs escaping for the \, so -> \\:
   # the shell that runns the isadmin command needs escaping as well, so -> \\\\:
   # the shell that runns the ssh command needs escaping as well, so -> \\\\\\:
   ssh $server "$logicalhostPath/is/bin/isadmin create-jvm-options -XX\\\\\\:+UseParallelGC"
   ssh $server "$logicalhostPath/is/bin/isadmin create-jvm-options -XX\\\\\\:PerfDataSamplingInterval=500"
   ssh $server "$logicalhostPath/is/bin/isadmin create-jvm-options -XX\\\\\\:+DisableExplicitGC"
done

eDesigner on Linux

2008-03-20T00:37:00.000+13:00

I spent several hours a few years back trying to get eDesigner working on Linux and found that it was either not possible, or exceedingly hard to achieve.

I've tried eDesigner in VMWare and found that it works, albeit a bit slow, but it works. However, I was never able to get used to running MS-Windows in a window of it's own, so I was much pleased to hear that VirtualBox (http://www.virtualbox.org/) has a "Seamless Integration" mode which lets you integrate MS-Windows with Linux as shown in the screenshot above.

I've been using this mode for a few weeks now and have had no problems at all.

If you're a Linux user, is something that I definitely recommend trying out.

JCAPS Log Server

2008-01-08T23:37:00.000+13:00

In JCAPS each project is packaged as an EAR file which then gets deployed to a JCAPS Domain (Sun Application Server). As these EAR files contain a full set of referenced jars they can be 10MB or more. This leads to a limitation on the number of EARs that can be run in a single Domain due to JVM memory restrictions. A team with a huge number of EAR files will have a large number of Domains running.

Often this problem is created also by configuring the JCAPS Domains in replicated clusters for increased throughput (scalability) or high availability.

As a message passes through the various stages in an application it may traverse multiple Domains, requiring the developer to search through many log files in order to piece back together a complete EAI transaction.

Searching through many log files is further complicated as they are scattered across many different directories and hosts.

It would be very handy to only have to look in a single well known directory on a well known host and find all logs from all Domains. However, JCAPS often generates vast amounts of logging and would easily saturate the network with non-critical logging messages.

Two approaches come to mind in order to get all log files into one well known location. Note: These are all Unix-based approaches. I can't imagine why anyone would want to run Windows on a server. ;-)

Use cron to periodically move log files to the Log Servers logging directory.
Use NFS to remotely mount the Domain's .....is/domains/domainName/logs directory into the Log Servers logging directory.

The second approach appears to be the best solutions as this generates the least network traffic and give a "near" real-time view of the log file, ie. "tail -f server.log" will work on the Log Server.

Having all files in a single directory tree we could use

tail -f server.log
less server.log
grep -r someRegEx *.log
Use a basic web application to view the log files similar to the way the JCAPS Enterprise Manager lets you brows log files. This would have to be custom built, but should not be very difficult to do.

If each application level log message would be prefixed with a unique transaction ID, then it should be trivial to do a "grep -r UUID *.log" and be able to track a transaction that spans multiple JCAPS Domains.

A "tail -f" over NFS will not be as fast as executed locally (not over the network), but one needs to ask the question why people are can't live with viewing production log files with a few seconds delay.

Such a Log Server, as described above, would be used for a production system only. Developers would deploy a single application's EAR files do a dedicated development Domain and can run a "tail -f server.log" locally.

What to do if you have issues with the JCo libs

2007-11-24T01:31:00.000+13:00

In eDesigner:

check that sapjcorfc.dll and librfc32.dll are in C:/WIN/SYSTEM32
check that sapjco.jar is in edesigner\lib\ext

In Domain:

check that the sapjco.jar is in logicalhost/is/domains/domainname/lib/ext/sapjco.jar or logicalhost/is/lib
check that libsapjcorfc.so and librfccm.so are in logicalhost/is/lib

If you find that you still can't connect, try the following:

Are you using the correct JCo for your architecture? Check your architecture and then make sure your JCo libraries conform to this architecture. You could do something like this:

$> uname -a
Linux b2b01vstk11 2.6.16.46-0.12-default #1 Thu May 17 14:00:09 UTC 2007 i686 i686 i386 GNU/Linux
$>file librfccm.so libsapjcorfc.so
librfccm.so:     ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
libsapjcorfc.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped

Ensure the JCo is installed correctly through the following command:

logicalhost/jre/bin/java -jar logicalhost/is/domains/domainname/lib/ext/sapjco.jar -stdout

If you get the following error on Unix when running the above command:

java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [/jre/lib/i386/libsapjcorfc.so: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory]. java.library.path [/jre/lib/i386/client://jre/lib/i386:/jre/../lib/i386]
  at com.sap.mw.jco.JCO.(JCO.java:776)
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(Class.java:164)
  at com.sap.mw.jco.About.(About.java:33)
  at com.sap.mw.jco.About.main(About.java:93)
--------------------------------------------------------------------------------------
|                              SAP Java Connector (JCo)                              |
|                Copyright (c) 2000-2005 SAP AG. All rights reserved.                |
|                                Version Information                                 |
--------------------------------------------------------------------------------------
Java Runtime:
Operating System:    Linux 2.6.18-5-686 for i386
Java VM:             1.5.0_06 Sun Microsystems Inc.
Java Codepage:       UTF8
Versions:
JCo API:             2.1.7 (2006-06-12)
JCo middleware:      Library not found
JCo library:         Library not found
RFC library:         Library not found
Paths:
JCo classes:         /home/username/sapjco.jar
JCo library:         Library not found
RFC library:         System-defined path

You know that the jco isn't installed correctly.

The problem lies here: libstdc++-libc6.2-2.so.3 is not found.

You can verify this with this command as well:

$ ldd librfccm.so
  linux-gate.so.1 =>  (0xffffe000)
  libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7a83000)
  librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7a7a000)
  libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7a68000)
  libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7937000)
  libstdc++-libc6.2-2.so.3 => not found
  libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7911000)
  /lib/ld-linux.so.2 (0x80000000)

Now install the missing package "libstdc++2.10-glibc2.2".
For example on Debian do:

$sudo apt-get install libstdc++2.10-glibc2.2

Then:

$ ldd librfccm.so
  linux-gate.so.1 =>  (0xffffe000)
  libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7a4e000)
  librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7a45000)
  libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7a33000)
  libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7902000)
  libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0xb78ba000)
  libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7895000)
  /lib/ld-linux.so.2 (0x80000000)

Problem solved. :-)

Still not working?

Check your network connectivity by pinging the SAP host from your logicalhost machine.

Still find you can't connect, then ensure that there are no firewalls blocking your traffic.

jar's in a JCD not being updated in eDesigner

2007-11-24T01:12:00.000+13:00

What to do if the jar file in eDesigner does not update:

Are you using the correct JDK for compiling your java files?

ensure the correct jdk is selected in your Java IDE (try C:\_jcaps\edesigner\jdk).
clean the workspace so that no old .class files are lying around.
export the eclipse project to a jar file.

Still not working? Maybe eDesigner has cached an old version of the jar in a local cache. Try this:

delete the temporary build directory in the C:\Documents and Settings\\Local Settings\Temp\builds directory.
delete the build directory in C:\_jcaps\edesigner\builds.
try to build the ear file in eDesigner.

Sill not working? Maybe eDesigner is using an old version from the repository. Try this:

remove the jar file from the jcd.
remove the jar file from the repository.
search in C:\_jcaps\edesigner for the jar file in question and remove the files in the search result.
reimport the jar into eDesigner.
add jar to jcd.
rebuild ear file.

Still broken?

Delete the C:\_jcaps\edesigner\userdir and reinstall the eDesigner.

Still broken??? Oh dear... Let's hope it doesn't get this far.