1 Configuring Deployment Settings

Setting Up Users for Design Studio Deployment

Before individual Design Studio users can deploy cartridges to run-time environments, you must create users (if necessary) and assign them to the WebLogic Cartridge_Management_WebService parent group. The run-time environment and the type of cartridges individual Design Studio users deploy determine to which additional parent groups users must be assigned.

To set up users for Design Studio deployment:

1. Log in to the WebLogic Administration Console.

2. Click Security Realms.

   The Summary of Security Realms page appears.

3. In the Realms table, click myrealm.

4. In Settings for myrealm, click the Users and Groups tab.

5. On the Users tab, click New.

   The Create a New User page appears.

6. In the Name field, enter the user name.

7. In the Description field, enter information about the user.

8. In the Password field, enter a password for the user.

9. Confirm the password, then click OK.

   The user appears in the Users table.

10. In the Users table Name column, click the user.

    The Settings page appears.

11. Click the Groups tab.

12. In the Parent Groups area, select Cartridge_Management_WebService from the Available column and move it to the Chosen column.

13. Click Save.

Enabling SSL Connections

Before individual Design Studio users deploy cartridges from Design Studio using an SSL connection, you must enable SSL in the WebLogic server to ensure that the Cartridge Management web service accepts the SSL connection. Additionally, you must define the environment connection parameters using HTTPS and include the correct SSL listening port.

The SSL keys must be made available to Design Studio and the keystore must include keys for any environment connection using SSL. See the Design Studio Help for information about defining SSL properties on the Studio Environment editor SSL tab.

To enable SSL connections:

1. Log in to the WebLogic Administration Console.

2. In the Environment area, click Servers.

   The Summary of Servers page Configuration tab appears.

3. In the Servers table, click the appropriate server.

   The Settings tabs appear.

4. On the Configuration tab General subtab, select SSL Listen Port Enabled.

5. In the SSL Listen Port field, enter the SSL port number.

6. Click Save.

7. Start Design Studio.

8. From the Studio menu, select Show Environment Perspective.

9. In the Environment tab, double-click an environment.

   The environment opens in the Studio Environment editor.

10. Click the Connection tab.

11. In the Address field, enter the following:

    https://Host:Port/cartridge/wsapi

    where:

    Host is the host name of the system and Port is the SSL listening port number.

12. Click the SSL tab.

13. In the Keystore field, enter the location of the target server keystore.

    For example, in a test environment, you can enter the location for the DemoTrust.jks keystore (from the server installation). Or, you can enter a replica.

    Note:

    If you are using a WebLogic Server DemoTrust keystore, and if the Java version installed on the client machine is version 1.7u40 or later, you must change the RSA key size. See "Changing the Keysize Value" for more information.

    For more information about configuring identity and trust for WebLogic Server, see "Configuring Identify and Trust" on the Oracle Help Center:

    http://docs.oracle.com/cd/E23943_01/web.1111/e13707/identity_trust.htm

    Do not use the DemoTrust.jks keystore in a production environment.

14. Click Save.

Configuring Deployment Messages

You use one of the available log levels to configure deployment message output for the Console view and for log files.

To configure deployment messages:

1. Navigate to Oracle software delivery website:

   https://edelivery.oracle.com

2. Download and extract the Oracle Communications Cartridge Management Tool archive file.

3. Navigate to and open the cartridge_management_tools/lib folder.

4. Unjar the cartridge_management_ws.ear file.

5. Unjar the CartridgeManagementWSPortImpl.war file.

6. Open the log4j.xml file.

7. Change the log level for output to the Console view:

   1. Search for the following line:

      <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">

   2. Change the parameter threshold to ERROR, WARN, INFO, or DEBUG.

      Note:

      When changing the log level to DEBUG, the priority value must be changed to DEBUG at the <root> level.

8. Change the log level for output to the WebLogic server log file:

   1. Search for the following line:

      <appender name="WEBLOGIC" class="org.apache.log4j.ConsoleAppender">

   2. Change the parameter threshold to ERROR, WARN, INFO, or DEBUG.

      Note:

      When changing the log level to DEBUG, the priority value must be changed to DEBUG at the <root> level.

9. Change the log level at the package level:

   1. Search for the following line:

      <category name="oracle.communications.sce.cartridgemanagement"> or <category name="com.oracle.xmlns.communications.sce.cartridgemanagement.ws">

   2. Change the priority value to ERROR, WARN, INFO, or DEBUG.

      Note:

      When changing the log level to DEBUG, the priority value must be changed to DEBUG at the <root> level.

10. Repackage the .war and .ear files.

11. Manually deploy the cartridge_management_ws.ear file to the WebLogic server.