Skip to main content

About Your Solution: What Is Not Documented

This page briefly mentions some solution-specific information that cannot be included in this documentation.

Environments and URLs

For your solution, InterSystems (or other solution partner) sets up and maintains multiple parallel environments so that development and testing activities can safely occur without disturbing mission-critical activities. This means that there is a development environment, one or more testing environments, and the production environment. Your solution partner makes changes in the development environment, promotes those to the testing environments when they are ready, and then, if appropriate, promotes them to the production environment.

The features that are enabled may vary from environment to environment. For example, the production environment may be somewhat locked down compared to the development environment. The details depend upon your business needs.

Your solution partner will provide you with all the URLs for each of the environments, including JDBC connection URLs.

The Back End

In addition to the user interfaces that are provided to you, your solution has back end user interfaces via which the following kinds of activities occur:

  • Creation and modification of the target table definitions (the tables in the solution to which the data is promoted)

  • Customizations that cannot be accomplished in the user interfaces provided to you

  • System management, including backups and (depending on your Terms and Conditions) mirroring for high availability

  • Monitoring of the system and correction of issues

Your solution partner will use these back end interfaces, which are not documented here.

Data Model

The phrase data model refers collectively to the tables within the database of InterSystems TotalView™ For Asset Management and the cube definitions based on those tables. Depending on your solution, this data model can be the canonical asset management data model provided by InterSystems or can be a custom model.

For a custom model, you may already have table definitions that can be reused. In this case, the process is to work with your solution partner to load the table definitions into the back end of the development environment, promote them to test environments as appropriate, and then promote to the production environment.

In other cases, you may need to work with your solution partner to create suitable table definitions and then add them into the system as described above.

With a custom model, it is also necessary to create new cube definitions based on the custom tables.

In either case, the data model is not documented here. To browse the tables, use third-party tools such as DBeaver (once you have the JDBC connection details). Similarly, use InterSystems IRIS® Advanced Analytics or your choice of analytics tool to browse the cube definitions.

FeedbackOpens in a new tab