Creating and configuring a WebLogic domain for Studio

Studio must be installed in its own WebLogic domain. To avoid any conflicts, the domain cannot contain any other applications. Even if you are installing Studio on the same instance of WebLogic Server as Endeca Server, you must create a separate domain for Studio.

1. From a command prompt, change to the directory that contains the Configuration Wizard start-up program.

   For example, for Windows:

   C:\Oracle\Middleware\wlserver_10.3\common\bin

   For Linux:

   $MW_HOME/wlserver_10.3/common/bin

2. To start the Configuration Wizard , run the following command:

   For Windows:

   config.cmd

   For Linux:

   ./config.sh

   The Configuration Wizard Welcome page is displayed.

   
   
   
3. On the Welcome page, click the Create a new WebLogic domain radio button, then click Next.
4. On the Select Domain Source page, the Basic WebLogic Server Domain checkbox is checked by default. Click Next.
   
5. On the Specify Domain Name and Location page:
   1. Set the domain name to endeca_studio_domain
   2. Keep the default domain location.
   3. Click Next.
   
6. On the Configure Administrator User Name and Password page, to create the administrator credentials for starting the Studio domain:
   1. In the Name field, type the name for the administrator user.
   2. In the User password field, type the user password.

      The password must be at least eight characters long.

   3. In the Confirm user password field, retype the password.
   4. Optionally, in the Description field, type a description for the user account.
   5. Click Next.
   
7. On the Configure Server Start Mode and JDK page:
   1. Under WebLogic Domain Startup Mode, click the Production Mode radio button.
   2. Under JDK Selection, click the Available JDKs radio button.
   3. In the JDK list, click the Sun Java JDK that you installed earlier. If the JDK is not displayed, click the Other JDK button, and then browse to it.
   4. Click Next.
   
8. On the Select Optional Configuration page, check the Administration Server checkbox, then click Next.
   
9. On the Configure the Administration Server page:
   1. Use the default values for the Name and Listen address fields.
   2. In the Listen port field, type 8101.
      
   3. If you want to enable SSL, then check the SSL enabled checkbox, and in the SSL listen port field, type 8102.
   4. Click Next.
10. On the Configuration Summary page, to create the domain, click Create.
    
    
    

    On the Creating Domain page, the message "Domain Created Successfully!" signifies the end of the domain creation process.

    
    
    
11. To exit the Configuration Wizard, click Done.
12. Update the setDomainEnv script file (setDomainEnv.cmd for Windows and setDomainEnv.sh for Linux).

    The file is located in the bin subdirectory of the domain directory (<MiddlewareHomeDirectory>/user_projects/domains/endeca_studio_domain/bin/) .

    1. Add the JAVA_OPTIONS argument close to the top of the file.

       For setDomainEnv.cmd (Windows):

       set JAVA_OPTIONS=-DUseSunHttpHandler=true -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl

       For setDomainEnv.sh (Linux):

       JAVA_OPTIONS="-DUseSunHttpHandler=true -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl"
       export JAVA_OPTIONS

       Note that if you're copying and pasting out of this guide, make sure to remove any line breaks after pasting the text into the file.

    2. Update all of the Java perm size arguments in the file to replace all occurrences of -XX:MaxPermSize=128m and -XX:MaxPermSize=256m with -XX:MaxPermSize=512m.
    3. Update all of the memory arguments in the file to replace all occurrences of -Xmx512m with -Xmx1024m.
13. To verify that there are no conflicting applications on the domain's root context:
    1. Start the domain.

       In <MiddlwareHomeDirectory>\user_projects\domains\endeca_studio_domain, run startWebLogic.cmd (for Windows) or startWebLogic.sh (for Linux).

    2. When prompted, enter the domain user name and password.
    3. After the domain is started, in a Web browser, go to http://<serverName>:<portNumber>.

    If you get a "page not found" (404) error, then there are no applications on the domain's root context, and you can continue the Studio installation process.

    If you see the login page for a previously deployed Studio application, then you should un-deploy this application.

    If you see another application, then you should log in to the WebLogic Console, and then either remove the application or untarget it from the WebLogic Server instance.

    For example, one common conflicting application is Oracle Enterprise Manager, which deploys an application to /em, but also installs the FMW Welcome Page Application to the root context.