Oracle Siebel CRM is moving to a 64-bit application architecture. This modernization builds on your existing investment, preserving business models, configuration assets and core user processes while aligning the application tier with current platforms and libraries. Its primary purpose is to support platform longevity and compliance readiness through continued security maintenance and reduced reliance on legacy compatibility packages.
A 64-bit architecture allows each Siebel process to address substantially more memory than a 32-bit process, giving memory-intensive operations room to grow. For Application Object Managers, this may support larger caches, more demanding transactions and more users or transactions per process. Actual benefits will depend on your configuration, customizations, workload and infrastructure. Early dependency assessment and representative testing will help you prepare for adoption and make informed sizing decisions.
Your 64-bit preparation checklist
Siebel CRM is moving to a 64-bit architecture, and monthly updates for Linux and Windows—which include security fixes, bug fixes and enhancements—will be available only in 64-bit.
Plan your adoption now so you are ready to keep receiving the Siebel CRM Release Updates after the move to 64-bit architecture. Backports containing critical bug fixes for older releases are limited under the Siebel CRM Error Correction Policy (PNEWS2743).
Most business configuration and Open UI assets need no conversion solely for 64-bit. So we suggest starting with the external components your customizations use, then work through this checklist with your teams and suppliers.
1. Siebel eScript
- Review all calls to external libraries and COM objects. Obtain compatible 64-bit libraries where they are loaded within Siebel; scripts do not need a blanket rewrite.
- Test the business flows that use these components.
2. Siebel VB and COM
- Review COM Data Control, COM Data Server, Mobile Web Client Automation Server, and all external library, COM and automation calls—including, for example, COMCreateObject in eScript and CreateObject in Siebel VB—along with their dependent applications. A DLL is a COM option only if it exposes a COM object.
- Use compatible 64-bit components when loaded within a Siebel process. Assess separately hosted COM/DCOM applications according to their interfaces and deployment model. Replace or rebuild affected components and regression-test the complete integration.
- Review Windows API calls and update declarations, pointer types and data structures where needed. External VBA code may require PtrSafe declarations; this is not Siebel VB syntax. Validate WScript and other automation in the target environment.
3. EAI DLL Transport
- Obtain 64-bit versions of custom transport DLLs and their dependent libraries.
- Check compatibility with the target interface, then test message processing and error handling.
4. CTI drivers
- Confirm a supported 64-bit telephony driver with your supplier.
- Test agent login, call controls, screen pops and reconnection.
5. Custom security adapters
- Replace or rebuild custom adapters and their dependencies for 64-bit.
- Test user and integration logins, including Gateway authentication where used, and administrative recovery.
6. Custom data quality integrations
- If your data quality integration uses a custom library not supplied with Siebel by Oracle, use a 64-bit version of that library.
7. Find custom and third party binaries
- Use Oracle’s discovery tool to review supported library references in Siebel eScript, Siebel VB, EAI DLL Transport and CTI driver configurations. It also compares selected files in the Siebel installation against the supplied manifest to highlight potential custom binaries.
- Treat the reports as a starting point. Review all custom integrations—including COM, Java integrations and dependencies outside the installation—and rebuild affected libraries and executables for 64-bit or obtain compatible versions from your suppliers.
8. Java integrations with Java 21
- For custom applications using Java Business Service (JBS), Java Data Bean (JDB) or Java Connector Architecture (JCA), use the Siebel JARs supplied with the target 64-bit release and validate with Java 21 in the supported configuration.
- Update application packages and test connections and service calls. Any native Java libraries also need compatible 64-bit versions.
9. Rolling updates
- Follow the latest rolling update instructions specific to the move from 32-bit to 64-bit Siebel CRM.
Before go-live
- Keep a short inventory with an owner and a readiness status for each integration. Include external data providers such as ADO or ODBC where used.
- Test complete business workflows and recovery in a representative environment. Check memory use and performance before changing sizing or parameters.
- Continue your established access controls, patching, monitoring and compliance checks.
- Agree the cutover window and recovery plan with your operations team, and let users know what to expect.
Working through these checks early will help your team make a controlled transition to 64 bit Siebel CRM.
For more information, refer to the Siebel Infoportal.
