Oracle® Communications Design Studio Concepts
Release 7.2.2
E35787-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

3 Design Studio Projects

This chapter provides information about Oracle Communications Design Studio projects.

About Projects

Design Studio projects contain all of the solution artifacts that you model and configure in Design Studio. Design Studio projects contain entities that you use to model and deploy Design Studio cartridges. Your solution uses various types of projects. You use these projects to build cartridges that can be deployed to a server, for version management, for sharing, and for resource organization.

You can create various types of projects and you can extend cartridges that you purchase with your own solution-specific cartridges. Oracle Communications supports a library of extensible cartridges that are fully compatible with Design Studio and provide a basis from which to assemble solutions.

The most common types of projects you use in Design Studio are:

In each project, you can model the data necessary to achieve your solution (and share that data across all projects in the workspace) build and package the projects, and test them in run-time environments.

Application integration and cross-product modeling and data sharing reduce the effort and time to deploy solutions. Design Studio supports the design-time configuration for integrated (or standalone) service fulfillment solutions and for network resource management solutions.

Importing Projects

One way to start working in Design Studio is by importing domain-specific and vendor cartridges into Design Studio and using these cartridges as the foundation for your new solutions. For example, if you have obtained cartridges from Oracle, you can import them into Design Studio and reuse their components to create your own cartridge projects.

When you import a cartridge, it becomes a project in the current workspace. Some cartridges are sealed, meaning that they are read-only. Sealed cartridges cannot be modified without first being unsealed.

If you import a cartridge project that has dependencies on other cartridge projects that are not in the current workspace, Design Studio displays an error. Import all dependent cartridges, then clean all projects to remove the errors. See "Working with Project Dependencies" for more information.

Upgrading Projects

When working in a new version of Design Studio, you must upgrade projects from the previous Design Studio version to the latest Design Studio version. Additionally, you must obtain and import the latest versions of all sealed productized versions if you want to use the cartridge in the updated version. During the upgrade process, Design Studio automatically detects old project versions and completes all necessary project upgrades in the workspace.

See Design Studio Installation Guide for more information about upgrading projects.

Working with Model Projects

Model projects are collections of data elements intended to be referenced by other projects in a workspace to fulfill a solution. Model projects include simple data elements and structured data elements that are not specific to any one Oracle Communications application and that enable you to share that data across a solution.

Entities in Design Studio application projects can reference data in a model project. You can model these data elements once, then configure different applications to reference these data elements, as appropriate. This modeling strategy enables you to identify which entities in a solution share the data elements in the solution.

Figure 3-1 illustrates how Activation project, OSM project, and Inventory project entities can all share data elements (the Call Features structured data element and the child data elements Caller ID, Call Waiting, and Call Forwarding) created and saved in a model project.

Figure 3-1 Leveraging Data in a Model Project


Working with Cartridge Projects

Cartridge projects contain collections of entities that you can deploy to a run-time environment to support your business processes (for example, cartridges deployed to Oracle Communications Order and Service Management run-time environments provision services requested on incoming sales orders). When modeling application-specific entities in Design Studio, you configure all entities in a cartridge project.

Cartridge projects can have design-time dependencies on other cartridge and model projects. During builds, Design Studio adds the necessary design artifacts from any dependent projects to your cartridge project.

Cartridge projects can be built and packaged into deployable cartridges. A cartridge is a collection of entities packaged into an archive file, which you can deploy to a run-time environment.

You can create the following cartridge projects in Design Studio:

See the Design Studio Help for more information about these cartridge projects.

Working with Environment Projects

Environment projects enable you to manage the attributes associated with your run-time environments, including connection attributes, projects ready to be deployed, projects previously deployed, and associated project attributes such as the version and build numbers.

You must create at least one environment project. Environment projects can be shared among all team members who use the same test environment. You work with environment projects and their entities in the Environment perspective.

Working with Project Dependencies

Projects have dependencies on other projects when entities in one project reference entities in another project. For example, an application project might reference data elements defined in a model project.

Project dependencies enable you to share data elements and entities across application and model project boundaries. Defining dependencies among projects helps eliminate circular dependencies and duplicate data elements from your data solution, and enables you to better understand how projects are related. Defining project dependencies ensures that all of the data a cartridge project requires is available when you deploy the cartridge project to a run-time environment.

When you build the project, Design Studio ensures that all entities referenced in but defined outside of the project are declared. Design Studio saves the project dependency information and uses this information to validate dependencies at deployment.


Note:

Oracle recommends that you plan relationships between projects and configure project dependencies early in your development cycle.

Project Dependencies and Data Modeling

The project dependencies control the selections that are available when you model cartridge projects. Design Studio restricts the data that is available (in data selection dialog boxes and in views) to data defined in the project and in dependent projects only. This configuration prevents circular dependencies and unintended model reuse by filtering the data available for selection.

Project Dependency Warnings and Errors

If you configure a cartridge project to reference content in other cartridge projects without declaring project dependencies, Design Studio creates an error or a warning. You control this level of severity, based on how you define the diagnostic level in the Cartridge editor Dependency tab.

You define the level of severity in the Dependency Violation Diagnostic Level field. Oracle recommends that you define this field with the value Error. If you are working with cartridges that were designed with cyclic or mutual dependencies, you can reduce the diagnostic level to Warning (to allow the use of the cartridge project) until you are able to restructure the cartridge project.

Project Dependency and Cartridge Deployment

The dependencies defined for a project impact the order in which you deploy cartridge projects. You must deploy all dependent cartridges first. For example, if project A depends on project B and project C, and project B depends on project C, when you deploy project A, Design Studio determines that projects C and B must be deployed first (and in that order).