Implementation > EBICS > EBICS Server > EBICS Server tools > Specific application server configuration

Specific application server configuration

Configuration for WebSphere environments

Before you can use the API or any of the EBICS Server tools in a WebSphere or WebLogic environment, you must perform some additional configuration steps.

Configuration for WebSphere environments

Make sure you are using an IBM JRE.
Set the following properties in the JVM arguments of all your client scripts (tools, purge, supplier, injector, etc):
- -Djava.security.auth.login.config=<WAS_profile>/properties/wsjaas_client.conf
- -Dcom.ibm.CORBA.ConfigURL=<WAS_profile>/properties/sas.client.props
- -Dcom.ibm.SSL.ConfigURL=<WAS_profile>/properties/ssl.client.props
where:
- <WAS_profile> is the path to the WebSphere profile folder where you have deployed the EAR.
- wsjass_client.conf file contains the unchanged defaults shipped with WebSphere.
- ssl.client.props file has the following modifications:
  - If the API is on the same machine as the WebSphere server, the value of user.root is the profile repository.
  - If the API is not on the same machine, set the value of user.root to the directory that contains a folder named etc. The user must have write rights on this folder.
- sas.client.props file has the following modifications:
  - com.ibm.CORBA.loginSource=none
  - com.ibm.CORBA.securityServerHost=<hostname_of_WebSphere>
  - com.ibm.CORBA.securityServerPort=<port_of the BOOTSTRAP>
Add the following JAR files to the classpath of your scripts:
- com.ibm.ws.admin.client_x.x.x.jar
- ejb3exceptions.jar
- com.ibm.ws.webservices.thinclient_x.x.x.jar
where x.x.x depends on the version of your application server. You can find these JAR files in <WebSphere_Install_ROOT>/runtimes.

For Websphere 8: Do the following in the Administration Console:
- In "CSIv2 Inbound Communications" and "CSIv2 Outbound Communications", change Transport parameters from "SSL-required" (new default value in Websphere 8) to "SSL-supported"
- In Security -> Global Security -> Custom Properties, add the property: com.ibm.websphere.security.registry.propagateExceptionsToClient and set it to true.

Configuration for WebLogic environments

In a WebLogic environment, you must add the following JAR files to the classpath:

wlfullclient.jar
cryptoj.jar

By default, these files do not exist in the WebLogic installation. You must generate them (using a tool provided by WebLogic) as follows:

Change directory to the server/lib directory:
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar and cryptoj.jar in the server/lib directory:
java -jar wljarbuilder.jar
You can now copy and bundle the wlfullclient.jar along with cryptoj.jar in the lib directory along with the scripts.
Important: Keep the wlfullclient.jar and cryptoj.jar files in the same directory because wlfullcient.jar references cryptoj.jar in its manifest classpath.

UNIX script modification

On UNIX, modify the script by adding the following lines:

CP=$CP:$LIB_DIR/wlfullclient.jar
CP=$CP:$LIB_DIR/cryptoj.jar

Windows script modification

On Windows, modify the script by adding the following lines:

set CP=%CP%;%LIB_DIR%\wlfullclient.jar
set CP=%CP%;%LIB_DIR%\cryptoj.jar

VM arguments

You must also modify the script by adding the following VM arguments:

Dweblogic.jndi.enableDefaultUser=true -Dsun.lang.ClassLoader.allowArraySyntax=true