1. Does Siebel CRM support 64-bit processes?
Siebel fully supports all 64 bit Operating Systems. Though some server processes still use 32 bit binaries, many of the processes used for integration and security and rendering of user interfaces use 64 bit. Siebel Gateway and Siebel Application interface, which replaces Siebel Web Server Extension fully leverage native 64 bit binaries, in addition to delivering a host of new features. Keep in mind that regardless of 64 bit compilation, Siebel has its own memory management meaning it easily scales to large memory configurations.
2. Is there no longer a requirement for the 8080 port?
Port 8080 is still used for the Mobile Web Client. With future development from 17.x being performed more with Siebel Composer, there would be less of a requirement for Mobile Web Clients using this port.
3. Please verify that the EAI is now fully REST compliant
Yes, there are many new updates for REST in 17.x and above with respect to outbound REST - and some tweaks to inbound.
4. Is the Siebel gateway still active/passive or can it be active/active cluster natively?
The Gateway is essentially the same architecture overall as before, and you can consider operating system clustering for active/ passive – which is supported through your OS vendor, and we will introduce application level clustering to allow 3 or 5 node redundancies in the future. The two methods are complementary and recommended for High Availability (HA). We strongly recommend OS clustering before placing in production to make sure it meets your operational requirements. When application gateway becomes available it will not be a default.
5. Is there any improvement with the elasticity of the Gateway? With the changes to the gateway are we able to have more than one active gateway for a single enterprise to scale wide?
More than one active Gateway is unnecessary now because the Gateway is now a stateless REST service.
7. Is SAML supported?
SAML2 support is already provided as of 16.x. We also continue to support header based SSO. Keep in mind that with 17 OAM webgates sit in front of the Application interface as a proxy – on any webserver of your choice and this makes integration a lot easier. There are also solutions that allow plug ins for the Tomcat based AI and those are supported by respective vendors. Contact your vendor to see if Siebel is validated with their plug-in.
8. Do you still support WIA based SSO?
No. It is proprietary and cannot be supported in a standards based solution like Siebel Directly. However, Microsoft provides solutions to integrate WIA to SSO/SAML via federation.
9. I don’t see the web servers supported such as IIS ? Which Web server is provided out of box?
Siebel integrates a new web server Out of box. This makes it much easier to manage. You can continue to use the existing web servers as front end to the Application interface to authenticate web users for SSO.
10. Is the SISNAPI layer removed?
No, SISNAPI is still used.
11. Do we have the docker image for 2017?
We are working on docker support for our cloud offering and we think it will work well with Siebel’s deployment features. Stay tuned!
14. Will there be any change in the load balancing of requests by the SR broker to components in different servers?
Nope it continues to work well!
15. How do load balancing requests know which web server to hit if there is no lbconfig?
Requests go to the Gateway - which returns to the AI a load-balanced connect string - the AI can then connect the request to the final node
16. Can IP16 and IP17 on the same machine?
It is possible if the ports are not conflicting, however this isn't necessarily a recommended architecture.
17. What third parties are certified?
All supported 3rd parties are listed on My Oracle Support (MOS) certify. A more manageable list of the same is available as attachment to the Open UI Deployment Guide on MOS https://support.oracle.com/epmos/faces/DocumentDisplay?id=1944467.1
18. Is Oracle 11 database supported?
We are not supporting Oracle 11g database version for IP2017. The only database version for Oracle supported for IP2017 is Oracle 12c. Oracle 11g database is out of premier support.
19. Which version of DB2 is supported by IP2017?
DB2 version supported in IP2017 is DB2 UDB LUW 10.5
20. Can we expect a ready to go server installed image for IP17 server, for developer practice/self-study?
Yes, You can provision IP17 on Oracle Public Cloud (OPC) rapidly. at the current moment - you can get a free trial.
21. Does Siebel CRM IP16 / 17 support dual-factor authentication? How do I enable dual-factor authentication?
Dual factor authentication infrastructure would be external to Siebel CRM, just as SSO infrastructure is but many authentication solutions support it and can dovetail into SSO. Once authenticated, a User Id and token will be passed onto Siebel CRM.
22. What version of J2EE will be deployed with IP2017?
The built-in version is Tomcat, which is very J2EE. It is the only one certified today, but we encourage customers to experiment and let us know their experience with other J2EE servers like Weblogic, which we anticipate will work.
23. Today we use Veritas Clustering Service (VCS) to make the Gateway server HA. Will that solution will work for us in IP2017 or do I need to look at other options?
Veritas has been working hard to update their Siebel CRM clustering agents for Siebel CRM 17 and above. Please contact Veritas for availability of those agents.
24. Does the Siebel CRM RESTful API support OAuth?
From IP16 onward, Siebel support OAuth 2 for authentication. Here’s the relevant documentation.