To set up your environment for the following sections, open a command prompt and execute the following commands under Microsoft Windows:

set WASP_HOME=d:\tmp\wasp50

set CLASSPATH=%WASP_HOME%\lib\wasp.jar;%WASP_HOME%\lib\security_providers_client.jar; %WASP_HOME%\lib\core_services_client.jar;%WASP_HOME%\src

cd %WASP_HOME%\src

set PATH=%PATH%;%WASP_HOME%\bin

Use these commands on UNIX-based systems:

export WASP_HOME=/tmp/wasp50

export CLASSPATH=$WASP_HOME/lib/wasp.jar:$WASP_HOME/lib/security_providers_client.jar: $WASP_HOME/lib/core_services_client.jar:$WASP_HOME/src

cd $WASP_HOME/src

export PATH=$PATH:$WASP_HOME/bin;

Next, create a security identity for the following sections. Start the WSO2 SOA Enablement Server and point a web browser to: http://localhost:6060/admin/console (assuming local installation on the default port).

	Caution
	Do not forget to include the java.security.auth.login.config Java property in your scripts. It should point to the file that contains the login module entries used by configured security providers. The java command should look like the following: java -Djava.security.auth.login.config="$WASP_HOME"/conf/jaas.config ... test.Test