Achieving Digital Transformation with Oracle's Siebel CRM

Siebel CRM now on Docker!

John Bedford
Director, Product Strategy

We are excited to share the details of a new development - a packaging and deployment methodology for the Siebel CRM application using Docker.

Following the tier separations implicit in Innovation Pack 2017, namely the split of Cloud Gateway (CGW), Siebel Application Interface (SAI) and the Siebel Enterprise Server (SES), we’ve provisioned a new packaging and deployment model using Docker.

Docker tooling helps simplify and streamline the complexities associated with full build-configure-and-push strategies. Our aim is to keep the Dockerfile content in the public domain as simple as possible in order to help the widest possible audience to understand and use this.

Why Docker?

  1. Docker provides a robust platform for Continuous Delivery, Continuous Integration and Continuous Deployment, facilitating delivery of innovation faster.
  2. Facilitates customers packaging their configured systems into images and containers
  3. Facilitates easy portability to virtual machines or bare metal servers, on-premise or in the cloud (IaaS)
  4. Docker provides a transparent mechanism that facilitates collaboration with customers and partners, facilitating rapid convergence on best practices for DevOps (build, functional/PSR test, demo, deploy).

For more information about Dockerfiles please see here.

Try it!

We have published our first set of Dockerfiles to facilitate container builds for Siebel CRM on Github. You can take a look here on the Siebel CRM Github repository.

Why we decided to publish the Dockerfiles on Github:-

  1. To accelerate quickly towards fully built containers
  2. Collaborative development with interested customers and partners
  3. Facilitate customers building their own images, once they comply to standard volumes
  4. We plan to roll out patching & persistence volumes, enabling customers to incrementally and continuously update – rather than reinstall/rebuild

We would love to hear about your experiences with Siebel CRM on Docker so we can continue to improve this offering.

You will also hear a lot more in the near future from us regarding this - and we plan to run a detailed Collaborative Learning session at OpenWorld.


Join the discussion

Comments ( 11 )
  • andros Friday, June 15, 2018
    It will be very convenient for testing something
  • Hugh Wheeler Monday, June 25, 2018
    Hi there,

    We are currently going through an 18.5 upgrade and are very interested in this. Do you have any further instructions, I have build an 18.5 docker environment based on the instructions, but there seems to be a bunch of things missing, ie start_ns is not present in the gateway, so i cant start it up.

    Some additional information would be awesome.
  • Suresh Friday, July 6, 2018
    Can this used for Siebel IP16? Is this required to have 12C oracle db installed?
  • Artur Tuesday, December 11, 2018
    I could successfully create IP 17.0 on docker. It works quite well. Now I tried to update to 18.11 (the newest one) and it does not work. You can confirue the enterprise with smc but cannot start the apps. Could you check if anything changed?
  • Funmi Faniyi Friday, February 1, 2019
    Any plans of publishing this container and others into Docker Hub?
  • rajani Tuesday, February 12, 2019
    Nice posting!! Thanks for sharing....
    Docker Online Training
  • John Tuesday, March 26, 2019
    Hi all,

    The best resource to answer these questions is directly on the GitHub portal for Siebel CRM on Docker.


    There are instructions there to set everything up. The Docker containers we have built are only available for our latest releases (not IP2016).

  • John Tuesday, March 26, 2019
    Hi Funmi,

    We have plans to publish on Docker but no eta for the date. Meanwhile, we are publishing the means to build your own container on our Github repository.

  • Filip Poverud Thursday, November 21, 2019
    This is really interesting, but now the question.

    Let's say I have a Load Balancer and 4 pairs of AA clustered tomcats in my org serving different parts of the Siebel infrastructure. Now I want to move this into a Kubernetes/Docker universe so I do not need to worry about having individual hosts for each container running a tomcat.

    Where do I set up this cluster ? I believe that at some point you are forced to connect point to point in order to setup the cluster, but I have yet to figure out where that is.

    I really want to test this out and measure the benefits of having our tomcats in the cloud without point to point connections vs our internal VMs where we unfortunately need to have an address to the LB making it vulnerable for network issues.
  • John Thursday, January 16, 2020
    Hi Filip,

    This would be no different than any other web based front end like Nginx, Apache etc

    In Kubernetes you create ingress controller which has a built in load balancer component. Of course there are many different ways you can arrange this, but this is the basic idea.

    Ingress controller has the https front end and this has to be connected with the SAI container back-end.

    Then internal Kubernetes load balancing and failover utilities are doing the cluster part.

    If the question is only about SAI Tomcat that should be it.

    For CGW clustering we still need to use classic Siebel clustering, that is we neeed to setup 3+ CGW containers and configure through SMC.

    There are currently two bugs pending on this (both with workarounds):



    Please contact support for more information.

  • Javier Tuesday, February 11, 2020
    Hi John, it is very good to hear about Siebel+Docker. I wanna ask you if it will be supported for Oracle.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.