Difference between Bookmark in Jetstream Template and Jetstream Container

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • Answered
what is the difference between creating a book mark on Jetstream Template and creatign a book on Jetstream Container. In what situation, one should create book mark in JetStream Template and JetStream Container
Photo of Ramesh


  • 518 Points 500 badge 2x thumb

Posted 2 years ago

  • 0
  • 1
Photo of Adam Bowen

Adam Bowen, Official Rep

  • 17,418 Points 10k badge 2x thumb
Official Response
The Template is the source that the containers are modeled after, and the containers are the children that are modeled after the source (the Template).

i.e. dSources are to VDB's as Templates are to Containers

To use an easy analogy:
Creating a bookmark on a Template is a lot like creating a snapshot of a dSource. 
Creating a bookmark on a container is a lot like creating a snapshot of a VDB of that dSource.

You can refresh the VDB from the snapshot of the dSource.
You can refresh/restore the Container from the bookmark of the Template.

You can rewind the VDB from the snapshot of the VDB.
You can reset/restore the Container from the bookmark on the container, or any bookmark that is shared with that container (from other containers of that template).

You can create new VDBs from snapshots of dSources and VDB's.
You can create new Container branches from bookmarks of Templates and Containers.

Does this help?
Photo of Tim Gorman

Tim Gorman, Field Services

  • 2,754 Points 2k badge 2x thumb
Official Response

What Adam said... :)

In terms of use-cases, bookmarks on templates are always shared - that is, they are "available" to all of the containers created from the template.

So, if there is a point-in-time that you'd like to have named and available for everyone (i.e. all of the owners in all of the containers) based on the data within the dSource, then a bookmark on the template is the way to do this.

Mind you, a shared bookmark can be created available for every container from any one of the containers, but that would come from the timeflow of the container, which would contains changes from that container, and not from the dSource.

As an example, suppose you want to bookmark the exact end of each fiscal month?

In other words, as a final step of your organization's month-end processing, you create a bookmark that is available for everyone, showing the actual month-end state of the data.

Or perhaps you also want to bookmark the beginning of the month-end processing, so that anyone can easily create a JetStream branch from either point-in-time, for comparison or modification as "what-if" analysis?

Not to imply that use-cases for bookmarks on templates are limited to this, but consider using them to mark points-in-time in which anyone or everyone might have an interest, outside of activities that have taken place within any container.

Just some ideas...

Hope this helps!