Showing results for 
Search instead for 
Do you mean 

How to Perform List of Value (LOV) Updates without System Downtime

by Community Manager Community Manager on ‎08-13-2014 02:12 PM - edited (7,394 Views)

Most Teamcenter customers make use of extending the Teamcenter Data Model through new business objects and properties as well as building a pick List of Values (LOV) for their data. These tasks are performed using the BMIDE client which is the modeling environment for your Teamcenter configurations. The BMIDE allows you to store all of your configurations in a container called a “template” and then deploy that template to any Teamcenter environment.

 

 

 

 

 

Typically when you want to apply your latest changes in your BMIDE template to a Teamcenter environment, you couple this activity with a system downtime. As a best practice Teamcenter customers perform the template update with a system downtime because the template could contain schema changes along with the LOVS. However, the system downtime is sometimes seen as a limitation.

 

Many Teamcenter customers need to update LOV values more frequently and do not want to have to take the system down to perform a simple update to a list of values. Suitably there are other options for handling frequent updates to LOVS without having to bring the system down. Read on to learn about the three options: BMIDE Live Update, Batch LOVS, or Dynamic LOVs. 

 

 

BMIDE Live Update

This feature was added in Teamcenter in 8.3.2, 9.1 and 10.1. This feature allows you to install a separate BMIDE client for the sole purpose of performing live updates directly to your production environment. The separate client allows you to keep your ongoing BMIDE development work seperated from the live updates you need to perform. The separate BMIDE can download the latest data model from the production environment, allow you to safely edit the LOV values without impacting schema, and then save it back to Teamcenter without having to take the system down.

 

 

Batch LOVS 

This feature was added in Teamcenter 9.1 and provides the ability for you to use a command line utility to update LOV values without having to take down the system. LOV values can be entered into an XML file and then uploaded into the Teamcenter environment by executing the utility. One of the added bonuses of the command line utility approach is that you can automate LOV updates through scripting.

 

 

Dynamic LOVS

 

 

This feature was added in Teamcenter 10.1 and provides the ability for you to define an LOV that will query Teamcenter product data to build its list of values. In this case the LOV values are not pre-defined in a BMIDE template, only the LOV query definition is pre-defined. As an example the LOV can be configured to build a list of Item IDs from Items that are released. When a user clicks on the LOV button in the user client, the system will perform the query and get the latest set of Item IDs that are released from your product data. As the list of released data changes over time, the LOV stays in synch with this, thus you will not need to take the system down to update LOV values.

 

About the blogger:

Bob Donovan is the Teamcenter product manager focused on the BMIDE and List of Values (LOVS), among other things. If you have the need to perform frequent updates to your LOVS, take a look at Bob's recommended techniques.

 

 

Comments
by Valued Contributor
on ‎10-04-2016 10:26 AM

Hi,

 

Is it possible to achive below  interpendent use case using Dynamic LOV or batch LOV

 

We have established below use case with classic LOV and would like to move it to either bacth or Dynamic LOV to avoid System downtime .

 

 

Parent LOV1

          ParentValue1-----> Child LOV1

                                ChildValue1-------->GRand Child

 

 

  

by Siemens Enthusiast Siemens Enthusiast
on ‎10-06-2016 03:48 PM

It is not possible to use Dynamic LOVS in your use case for both the ParentLOV1 and hte ChildLOV1. You can use a classic LOV for the Parent LOV1, and add LOV values to this LOV. then create various Dynamic LOVs, and attach each Dynamic LOV to an LOV value of the ParentLOV1. The result is that only the Dynamic LOVS can be used as the Leaf nodes of your interdependent LOV.

 

Bob

by Valued Contributor
on ‎10-14-2016 08:42 AM

Thank you BOB,

 

If I keep 

  ParentValue1- as Batch and ChildLOV1 as Dynamic LOV. Then Is it possible to attach GRand Child to ChildLOV1?

 


MSFurleigh wrote:

BMIDE Client.pngMost Teamcenter customers make use of extending the Teamcenter Data Model through new business objects and properties as well as building a pick List of Values (LOV) for their data. These tasks are performed using the BMIDE client which is the modeling environment for your Teamcenter configurations. The BMIDE allows you to store all of your configurations in a container called a “template” and then deploy that template to any Teamcenter environment.

 

 

BMIDE LOV.png

 

 

 

Typically when you want to apply your latest changes in your BMIDE template to a Teamcenter environment, you couple this activity with a system downtime. As a best practice Teamcenter customers perform the template update with a system downtime because the template could contain schema changes along with the LOVS. However, the system downtime is sometimes seen as a limitation.

 

Many Teamcenter customers need to update LOV values more frequently and do not want to have to take the system down to perform a simple update to a list of values. Suitably there are other options for handling frequent updates to LOVS without having to bring the system down. Read on to learn about the three options: BMIDE Live Update, Batch LOVS, or Dynamic LOVs. 

 

 

BMIDE Live Update

BMIDE Live Update.png

This feature was added in Teamcenter in 8.3.2, 9.1 and 10.1. This feature allows you to install a separate BMIDE client for the sole purpose of performing live updates directly to your production environment. The separate client allows you to keep your ongoing BMIDE development work seperated from the live updates you need to perform. The separate BMIDE can download the latest data model from the production environment, allow you to safely edit the LOV values without impacting schema, and then save it back to Teamcenter without having to take the system down.

 

 

Batch LOVS 

Batch LOV File.png

This feature was added in Teamcenter 9.1 and provides the ability for you to use a command line utility to update LOV values without having to take down the system. LOV values can be entered into an XML file and then uploaded into the Teamcenter environment by executing the utility. One of the added bonuses of the command line utility approach is that you can automate LOV updates through scripting.

 

 

Dynamic LOVS

 

Dynamic LOV Wizard.png

 

This feature was added in Teamcenter 10.1 and provides the ability for you to define an LOV that will query Teamcenter product data to build its list of values. In this case the LOV values are not pre-defined in a BMIDE template, only the LOV query definition is pre-defined. As an example the LOV can be configured to build a list of Item IDs from Items that are released. When a user clicks on the LOV button in the user client, the system will perform the query and get the latest set of Item IDs that are released from your product data. As the list of released data changes over time, the LOV stays in synch with this, thus you will not need to take the system down to update LOV values.

 

About the blogger:

Donovan_cropped_2014.jpgBob Donovan is the Teamcenter product manager focused on the BMIDE and List of Values (LOVS), among other things. If you have the need to perform frequent updates to your LOVS, take a look at Bob's recommended techniques.

 

 


 

 

ChildValue1-------->GRand Child

by Siemens Enthusiast Siemens Enthusiast
on ‎10-18-2016 10:22 AM

It would not be possible to attach another LOV to the values of a Dynamic LOV.