Weblogic Server Startup issues after extending a domain with installation of Basic SIP template
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 9.2 and later
Information in this document applies to any platform.
WebLogic SIP Server is included in all editions of Oracle WebLogic Server; however, you must license Oracle Communications Converged Application Server (OCCAS) in order to have usage rights to SIP Server. See http://docs.oracle.com/cd/E23943_01/doc.1111/e14860/products.htm#BABCAFJD.
WLS has shipped with some kinds of SIP extensions since OCCAS was taken over from WLS development. Now OCCAS is developed by the CGBU development team, but there are still WLS installers available which ship some more or less runnable SIP packages.
When the first WLS installer containing SIP was released, there was an email announcement that even though this installer ships some SIP parts of OCCAS, the SIP stack is not supported at all: the SIP code was intended only for experimenting by developers. Hence, only a customer with a valid OCCAS support contract and installing OCCAS via a valid OCCAS installer can get support from CGBU.
There are several releases of WLS which contains SIP extensions. Hence, it is possible that a customer could install the SIP extensions by accident, which would cause a failure to start the WLS server.
For example, one can see that SIP was selected by accident by extending the WLS domain using the Fusion Middleware (FMw) configuration wizard like so:
The screen to extend the domain shows that "BASIC Weblogic SIP Server Domain" template is already selected, which indicates that SIP was chosen when the domain was originally created.
A domain with "Basic Weblogic SIP Server Domain" selected will fail to start with the following error in the server logs:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms