To integrate ESRI ArcSDE with IBM WebSphere Application Server Community Edition (WAS CE) running on a legacy Windows Server 2003 Service Pack 2 (SP2) or Windows XP SP2 environment, you must establish connectivity using ArcSDE’s standalone Java API client.
Because WebSphere CE is based on Apache Geronimo (rather than the traditional IBM WAS stack), it relies heavily on custom Geronimo deployment plans (geronimo-web.xml) to manage external library dependencies and application scopes. Step 1: Gather the Required ArcSDE SDK Jars
The Java Application Development Framework (ADF) for ArcSDE requires specific client-side .jar binaries to establish connections. You must locate these within your ArcSDE SDK installation directory: jsde_sdk.jar (Core ArcSDE client functions)
jpe_sdk.jar (Projection engine / coordinate systems handling)
Database Drivers: Depending on your underlying DBMS (e.g., Oracle ojdbc14.jar or SQL Server sqljdbc.jar), you will also need the relevant JDBC driver package. Step 2: Install Jar Files into WebSphere CE Repository
WebSphere CE utilizes an internal Maven-like repository layout. To make the ArcSDE jars available to your web applications globally or during runtime, you need to add them to the server’s repository:
Open your browser and navigate to the WebSphere CE Administrative Console (typically http://localhost:8080/console). Log in using your administrative credentials.
In the left navigation panel, click on Common Libs or Repository.
Use the browse tool to upload jsde_sdk.jar and jpe_sdk.jar. Assign them an appropriate group/artifact framework (e.g., Group: com.esri, Artifact: jsde_sdk, Version: 9.x).
Alternatively, copy the files directly into the physical directory structure:
C:<WASCE_HOME>\repository\com\esri\jsde_sdk\9.x\jsde_sdk-9.x.jar Use code with caution. Step 3: Map TCP/IP Ports in Windows SP2
On Windows SP2, security updates enforce stricter firewall and networking layouts. ArcSDE application server routing requires explicit port definitions:
Open the file C:\Windows\System32\drivers\etc\services using notepad.
Append the standard ArcSDE entry at the bottom of the document: esri_sde 5151/tcp #ArcSDE Instance Connection Port Use code with caution.
Save the file. Ensure your local Windows Firewall or third-party security software permits inbound/outbound communication over TCP port 5151. Step 4: Configure the Web Application Deployment Plan
When constructing your WAR/EAR package, you must instruct WebSphere CE to link your application scope to the ArcSDE dependencies. This is handled in the geronimo-web.xml configuration file located in the application’s WEB-INF/ folder:
<?xml version=“1.0” encoding=“UTF-8”?> Use code with caution. Step 5: Establish the Java Connection
Within your servlets or backend Java beans, construct the connection explicitly using ArcSDE’s SeConnection object model.
Note: Since standard ArcSDE Java API libraries are generally not built as thread-safe JCA Data Sources, it is highly recommended to manage connections using a custom object factory or thread-local pooling framework to prevent resource exhaustion.
import com.esri.sde.sdk.client.SeConnection; import com.esri.sde.sdk.client.SeException; public class SdeConnectionManager { public static SeConnection getConnection() throws SeException { String server = “sde_server_name”; int instance = 5151; // TCP port configured in Windows services String database = “your_spatial_db”; String username = “sde_user”; String password = “sde_password”; // Establish direct socket connection to the ArcSDE service instance return new SeConnection(server, instance, database, username, password); } } Use code with caution. Troubleshooting Windows SP2 Environment Bottlenecks Deploying EAR files – IBM
Leave a Reply