14 Deploying, Testing, and Debugging Inline Services

14.1 Deploying Inline Services

After you have configured your Inline Service, you deploy it locally or to a test environment for testing. You can deploy an Inline Service in three different states: Development, QA, and Production.

You can deploy in the QA state during your testing cycle, and then, after testing, into Production state. When you deploy to Production state, select Release Inline Service locks. After the Inline Service is deployed to business users, they can also update and redeploy the Inline Service.

Deploy the Inline Service using the Project > Deploy menu item, or click the Deploy icon on the task bar:

The Deploy dialog box appears. The options in the Deploy dialog box are shown in Figure 14-1.

Figure 14-1 Deploy Dialog Box

Description of "Figure 14-1 Deploy Dialog Box"

Table 14-1 describes the options shown in the Deploy dialog box.

For general information on managing Inline Services, including how to remove an already deployed Inline Service, see "Post-Deployment Management of Inline Services" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.

14.2 Connecting to Real-Time Decision Server

When deploying or downloading Inline Services or importing data sources, you connect to Real-Time Decision Server. To connect, use the username and password you created on installation, or consult your Administrator for your username and password. To connect in a secure manner using https, select Secure connection.

Figure 14-2 shows the Connect to a Server dialog box.

Figure 14-2 Connect to a Server Dialog Box

Description of "Figure 14-2 Connect to a Server Dialog Box"

14.3 Redeploying Inline Services

If you are going to make changes to a deployed Inline Service, it is important to follow these practices in order to preserve both your changes and the potential changes that have been made by the business user. If you are making changes to a deployed Inline Service, you can download it from Real-Time Decision Server using the Download icon on the toolbar. Use the following method:

1. Make sure that no business users are editing the deployed Inline Service.

2. Always lock an Inline Service when you download it, so that additional changes cannot be made by business users while you are enhancing it.

3. Make enhancements in Decision Studio.

4. Redeploy the Inline Service, releasing the locks.

During the period that you have the Inline Service locked, business users will be able to view, but not edit, the deployed Inline Service.

14.4 Testing and Debugging Inline Services

To enable you to test and debug Inline Services, Oracle RTD provides the following facilities and features:

• Problems and Test Views in Decision Studio

• System Logs

• Load Generator

This section contains the following topics:

• Section 14.4.1, "About the Problems View"

• Section 14.4.2, "Using the Test View"

• Section 14.4.3, "Using System Logs for Testing and Debugging Inline Services"

Load Generator is a tool used for debugging and benchmarking Inline Services by simulating users. Load Generator is used both for testing the Inline Service, and for performance characterization.

For more information about Load Generator, see Chapter 15, "About the Load Generator."

logInfo("Installation date = " + DateUtil.toString(session().getCustomer().
getInstallationDate());

logInfo("Customer age = " + session().getCustomer().getAge() );

request.get$()

String request.getStringValue(fieldName)
SDStringArray request.getStringArrayValue(fieldName)
boolean request.isArgPresent(fieldName)

SDChoiceArray choices = null;

if (session().isControlGroup()) {
  choices = RandomChoice.execute();
} else {
  choices = SelectOffer.execute();
}

if (choices.size() > 0) {
  Choice ch = choices.get(0);
  ch.getSDOId();
}