1 Using Oracle Communications Evolved Communications Application Server

This chapter describes how to access and use Oracle Communications Evolved Communications Application Server (OCECAS). Using OCECAS consists of using the Session Design Center to create and access subscriber services and using the subscriber data store to provision and access subscribers.

For an introduction to OCECAS and an overview of Session Design Center and the subscriber data store, see Oracle Communications Evolved Communications Application Server Concepts. For information on how to configure and administer OCECAS, see Oracle Communications Evolved Communications Application Server System Administrator's Guide.

For a description of scenarios and corresponding call-session flows that OCECAS supports, see Appendix B, "External References for Supported Interactions."

About the Session Design Center

Session Design Center runs in the OCECAS management domain. It is a graphical environment that enables you to create and manage application service logic without writing code.

Accessing Session Design Center

To log in to OCECAS and access Session Design Center:

  1. In your web browser, enter the URL to go to the Session Design Center.

    For example:

    https://hostname:port/sdc/login.html?target=
    

    The OCECAS login page displays.

  2. In the User Name field, enter the user name for your account.

  3. In the Password field, enter the password.

  4. Click Sign In.

Once you successfully log in, the Home page, which is also known as the landing page, displays.

If your interaction with Session Design Center is idle for 30 minutes, the application logs you out.

Using the Session Design Center Console

The Session Design Center Home page includes the following elements:

  • Header bar

    The bar at the top of the interface that includes the name of the application, a Help link, and a user drop-down menu, which allows you to log out.

  • Navigation panes

    Below the header bar, the following panes provide access to principal areas of functionality:

    • Application contains a View Application Configuration > link that provides access to application control flows and resources.

      The Application section contains the VoLTE and VoWiFi application, all of the control flows that have been created for the application, and all of the resources that are available to the application. The VoLTE and VoWiFi application is the core of OCECAS's capabilities. You tailor OCECAS to your customer's requirements by creating control flows to add subscriber services.

    • Projects, or Open Projects, provides access to change sets.

      If open projects exist, the title of the section becomes Open Projects and links to any open projects are listed below. A View All Projects > link takes you to a list of all change sets for the application.

      The Projects section contains all of the change sets, which are also known as projects, that have been created to make changes to the application. A change set is a group of related configuration and control flow changes.

    • Environments provides access to the deployment pipeline, which consists of Testing, Staging, and Production environments. Use the View Environment Configuration > link to view and access projects in their stages of deployment.

      You deploy change sets sequentially into environments to safely migrate them into production. Each environment also provides access to its service configuration.

To return to the Home page at any time, click the Home icon ( house icon for navigating to Home screen) displayed below the Header bar.

WARNING:

Do not open multiple instances of Session Design Center in different browser tabs or windows.

Using Control Flows, Resources and Change Sets

The remainder of the Session Design Center interface is dedicated to working with control flows, resources, and change sets. See the following chapters for more information on using the Session Design Center:

Provisioning and Accessing Subscriber Data

For information on working with the subscriber data store to provision and access subscriber data, see "Working with Subscriber Data".

For a detailed description of the subscriber data store schema, see Appendix A, "The Default ESS Subscriber Store Schema."