![]() ![]() Also, you can define a separate working set for the Solution view to control visibility of project entities at the root level.įor example, you can facilitate design modeling and workspace navigation by creating a working set that displays only those projects related to your present design work. The projects that a working set filters out exist in the workspace and remain open but do not appear in the Studio Projects view. ![]() You control which projects appear in your workspace by creating and applying a filter, called a working set. ![]() See "Working with Project Dependencies" for more information.Ĭontrolling Project Visibility in a Workspaceĭesign Studio solutions can contain large numbers of productized, sealed, and application-specific projects that are not directly related to your work. Import all dependent cartridges, then clean all projects to remove the errors. 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. Some projects reference entities in other projects, and these references create dependencies among the projects. Sealed cartridges cannot be modified without first being unsealed. Some cartridges are sealed, meaning that they are read-only. ![]() When you import a cartridge, it becomes a project in the current workspace. When importing Design Studio for Inventory cartridge projects that include changes to tool tips or characteristic display names, you must redeploy the Oracle Communications Unified Inventory Management (UIM) application server when you deploy the cartridge that contains the changes. Importing from ASAP run-time environments and from OSM XML models is intended for migration purposes only. Design Studio supports the design-time configuration for integrated (or standalone) service fulfillment solutions and for network resource management solutions. 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.Īpplication integration and cross-product modeling and data sharing reduce the effort and time to deploy solutions. Model projects, which contain data common to multiple cartridge projects.Ĭartridge projects, which contain collections of entities and supporting artifacts that represent a cartridge deployed to a run-time environment.Įnvironment projects, which you use to manage attributes associated with your run-time environments. The most common types of projects you use in Design Studio are: Oracle Communications supports a library of extensible cartridges that are fully compatible with Design Studio and provide a basis from which to assemble solutions. You can create various types of projects and you can extend cartridges that you purchase with your own projects. For example, you use projects to build cartridges that can be deployed to a server, for version management, for sharing, and for resource organization. Your solution uses various types of projects. Design Studio projects contain artifacts (entities, data, rules, code, and so forth) that you use to model and deploy Design Studio cartridges. ![]()
0 Comments
Leave a Reply. |