# Deployment Checklist

## Partner Runtime

Use this checklist after connector development is complete and before handing off to operations.

1. **Build a deployable artifact**
   1. Build the assembly JAR, which includes all connectors and their connector-specific dependencies (e.g., JDBC drivers). The runtime supplies shared components (csp-sdk-core, Spring, oe-core) to prevent version clashes and duplicate classes.
   2. Generate the assembly/target/csp-sdk-\<version>.jar using ./build-csp-sdk.sh or mvn clean install -pl assembly -am.
2. **Upload/copy JAR for OvalEdge pickup**
   1. Copy artifact(s) to the runtime-configured jar path used by OvalEdge for connector loading.  The exact folder is environment-specific and configured in OvalEdge system settings (ovaledge.jarpath).
3. **Ensure runtime prerequisites**
   1. Required shared dependencies must be available in the runtime classpath (for example, \`csp-sdk-core\` and platform-shared bundles used in your environment). Connector JAR should include \`release-{artifactId}.properties\` metadata.
4. **Restart Services**
   1. Restart OvalEdge services so the connectors are discovered.
5. **Verify Deployment**
   1. Confirm:
      1. Connector appears in the connectors page
      2. Connection validation works
      3. Metadata extraction works
      4. Query execution succeeds
6. **Rollback**
   1. If validation fails:
      1. Restore the previous JAR.
      2. Restart services.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.