Classification and Library Management: One-Stop Guide - PDF Free Download (2022)

Transcription

1 Classification and Library Management: One-Stop Guide Document History Version Date Changes 1.0a November 28, 2016 Initial Draft 1.0b December 1, 2016 Ready for final review with Active Workspace c December 2, 2016 Final review comments added, made fonts and sizes consistent, added page breaks where needed, removed links to internal documentation builds locations (won t work for customers). Bruce Robinson 1.0d February 16, 2017 Fixed link in section 9 to point to Teamcenter MRL installation documentation on doc center. Bruce Robinson 2.0a July 7, 2017 Updated links to AW 3.3 and Tc 11.3 documentation on doc center. Bruce Robinson 2.0b September 27, 2017 Updated feature contents and links to AW 3.3. Abhi Aklujkar 2.0c February 7, 2018 Added a 3.4 tem issue in troubleshooting section 2.0d March 21, 2018 Added section Install Configuration Steps in Active Workspace 2.0e March 22, 2018 Added steps to perform when bulk importing in Classification Presentation Layer 3.0 January 17 th, 2019 Generated version of AW4.1 Release -no change 3.1 January 21, 2019 Added issue in troubleshooting section All Rights Reserved.

2 Table of Contents 1 Document Overview Overview of Teamcenter Classification Snapshot of sample Classification data Classification Teamcenter releases that support them Installation with TEM selections Supported scenarios in Active Workspace Search in Active Workspace Compare objects using their Classification properties Authoring in Active Workspace TEM deployment for Active Workspace Installation with TEM selections... Error! Bookmark not defined. 3.5 Supported scenarios in Active Workspace... Error! Bookmark not defined. 4 Classification Presentation Layer (a.k.a. Next Generation Classification) Teamcenter releases that support them Installation with TEM selections Data extension of Classification data into Classification Presentation Layer Extending existing Classification data into the Presentation layer (command examples) Automatic synchronization between Classification data and the corresponding Presentation layer Co-existence of Classification data with the Presentation layer by establishing linkages (recommendations) Supported scenarios in Active Workspace Search and Browse Classification hierarchy using Visual Navigation Cards (VNC) Libraries Management Teamcenter releases that support them

3 5.2 Installation with TEM selections Administering Libraries Create/Display/Publish/Retract Library objects Setup membership rules Evaluate membership rules Supported scenarios in Active Workspace Search and Browse Library contents using Visual Navigation Cards (VNCs) Extend the same example hierarchy from Next Generation Classification Specifications Management Teamcenter releases that support them Installation with TEM selections Supported scenarios in Active Workspace Classification and Library Management Apps in Active Workspace Deployment options Deploying via TEM Common use case examples: Indexing Classification Data for Active Workspace search Extending Classification data Classification Presentation layer Library Management Indexing Presentation layer data for Active Workspace search and browse Indexing Library data for Active Workspace search and browse Upgrade considerations Pre-upgrade considerations Post-upgrade considerations Sample Data Creation Using MRL library Importing MRL data from the CD Extending MRL hierarchy into Presentation layer Creating and populating Libraries from this MRL hierarchy Install Configuration Steps in Active Workspace Step by step

4 10.1 Traditional Classification Indexing Classification Presentation Layer or Next Gen Classification Indexing Library Management Indexing Bulk Import of Classification Data into Classification Presentation Layer (Next Generation Classification) Troubleshooting / Issues Catalogue Appendix A: List of Figures Appendix B: List of Tables

5 1 Document Overview The purpose of this document is to provide best guidance to Classification administrators and users. This document includes pointers and additional information to use Teamcenter classification in its maturity model. It also extends to the existing documentation in logical order and adds technical information for achieving the different phases being covered here. The scope of this document is to provide an overview of the application and help users get started with installation, deployment, sample data creation and using all the relevant utilities. It also points to the official online documentation in order to avoid duplication. This document will be updated with each release of Active Workspace and will be enriched by including new topics based on the feedbacks and frequently asked questions (FAQ s) from various forums. We hope this document will provide you help and guidance with Classification. Note: Please note that deploying the feature through deployment doesn t necessarily mean the data will start showing in Active Workspace Classification. The data needs to be created in the Storage Layer and then needs to be propagated in various layers of Classification to compliment the Classifications feature that are installed. Please refer Sample Data Creation section just to get the glimpse of the how the data needs to be propagated. Disclaimer: Don t try these commands or utilities in a production environment without knowing their implications. If you are using the utilities and commands for the first time, it is highly advisable to first try in sandbox or testing environment, gain the know-how, acquire the confidence, and then proceed with usage on stable platform. 4

6 2 Overview of Teamcenter Classification Classification is a process where you define objects by providing attributes to make an object easy to find for reuse. During the classification process, you enter attributes that help in the searching of the object, such as measurements, material, facets, and unit of measure. The more attributes you provide, the easier the object is found. Libraries are used to organize classified objects with similar characteristics or application in a hierarchy. For instance, if you were looking for a bolt, you would start by searching for the bolt library. Once you find the bolt library, then you can perform additional searches, use filters, or browse through the hierarchy to find the object that meets your criteria. Value path from Classification to Libraries is progressively shown in the order in the graphics. 5

7 6

8 2.1 Snapshot of sample Classification data Figure 1: Snapshot of Classification data extended from base Classification to Presentation layer to Libraries 7

(Video) How to use SharePoint Online for Knowledge Management - Microsoft 365

9 3 Classification Using a classification system helps you reduce costs by allowing you to reuse existing parts. This also helps in consolidating or eliminating duplicate or outdated parts. By classifying your company s data, such as, standard parts, technology data and manufacturing equipment, you save time because components are easier to find and retrieve. Classification is used to create and maintain a hierarchical classification structure based on the attribute values of your workspace objects that allow unique identification of individual objects. Using the Classification application, you can create a hierarchy of groups and classes to organize the groups of attributes that reflect your classification system. 3.1 Teamcenter releases that support them Classification is supported in all Teamcenter releases as an integral part of the Foundation feature. 3.2 Installation with TEM selections Classification will be deployed as an integral part of the Foundation feature 3.3 Supported scenarios in Active Workspace Search in Active Workspace Classification data has been exposed in Active Workspace beginning with AW 2.1, as part of following use cases: indexing classified objects will include the associated Classification data search by Classification Class ID or Name search by Classification Attribute values filter by Classification class or attribute values indexing multiple classification (new from AW 3.2) summary stylesheets for classified objects can be configured to display the associated Classification data (Class path and attributes) compare classified objects using their Classification attributes (new from AW 3.1.1) Search the classification information where Item rev is indexed but the item is Classified o Note: Classifying an Item is still not supported in Active Workspace 3.X Indexing of standalone classification is supported beginning with Teamcenter

10 9

11 Configuring Classification data for Indexing Classification Type (Class) and Attributes will have to be configured for indexing. To configure Classes for indexing: Classification Classes are configured for indexing, by addition of a Search Index type of View to these Classes. There are two ways to add Search Index View: 1. Manually adding a View individually under the desired Class(es) a. To enable this functionality in RAC, users must set the preference ICS_searchindex_view_visible = TRUE b. Create View operation will now list the Search Index type of View for creation Note: At this point The specified Class(es) are configured for Indexing and Filtering. Class Attributes for all these Class(es) are not yet configured for Indexing or Filtering 10

12 2. Mass setup for specified Class(es) a. smlutility now exposes a couple of switches to create ( -create_indexing_views ) and delete ( -delete_indexing_views ) Search Index views. For additional information, please refer to LMD section Note: At this point The specified Class(es) are configured for Indexing and Filtering Class Attributes for all these classes are also configured for Indexing and Filtering, without requiring any additional steps. To configure Classes for Filtering: By configuring Classes for Indexing, will automatically allow Filtering using Class values. There is no separate control over Filtering of Class values. To configure Attributes for Indexing: To configure Indexing, Class Attributes must be added to the underlying Search Index view. Note: If new Attributes are added for Indexing, SOLR schema will need to be regenerated as well as SOLR will need to be re-indexed so these Attribute values are searchable To configure Attributes for Filtering: To configure Filtering, View Attributes from the Search Index should have their Filter property set to TRUE. Note: If new Attributes are added for Filtering, SOLR schema will need to be regenerated as well as SOLR will need to be re-indexed so these Attribute values are searchable 11

13 3.3.2 Compare objects using their Classification properties Starting with release AW 3.2, users can compare objects using their Classification properties, in addition to their properties. More information can be found in Active Workspace documentation here Figure 2: Classification properties rendered when comparing objects Configure addition of Classification properties to Compare view This configuration is bundled with the Classification Server feature for Active Workspace for the default Search Results location. For other locations, refer to TBD for configuration instructions. Users should include following configuration: <ColumnDef objecttype="workspaceobject" propertyname="ics_subclass_name" width="250"/> 12

14 3.3.3 Authoring in Active Workspace Starting with Active Workspace 3.3, Authoring capabilities to classify objects is available as Productionready feature. More information on platform supported etc. can be found in Active Workspace documentation here. Current capabilities for classifying objects are exposed for following. Check configuration section in Active Workspace documentation here All Teamcenter Workspace object types as listed in the existing preference ICS_classifiable_types Following use cases are supported as a part of Classification authoring: Classify an object Reclassify an object Multiple Classification - Classify an object in multiple classes (one after another) Delete classification information TEM deployment for Active Workspace Starting with Active Workspace 3.2, Classification data can be configured directly via TEM deployed features. For this purpose, Classification features is exposed in TEM under the following feature branches: Active workspace > Server > Reuse and Standardization Active workspace > Client > Reuse and Standardization For comparison and deployment instructions, refer to Teamcenter releases that support them Specifications Management is supported from Teamcenter 11.2 Release onwards 3.4 Installation with TEM selections Specifications Management is included and deployed as part of the Library Management feature. For installation instructions of Library Management feature, refer section Installation with TEM selections. 3.5 Supported scenarios in Active Workspace Specifications Management is currently exposed via TC Programmatic Interface in RAC and other custom applications. Active Workspace does not currently expose the Specifications Management functionality. 13

15 Classification and Library Management Apps in Active Workspace 4 Classification Presentation Layer (a.k.a. Next Generation Classification) Based on the class hierarchy, you can additionally create a presentation hierarchy that provides more flexibility than the storage hierarchy. The presentation hierarchy serves as a platform for implementing new library management capabilities. It provides the ability to deal with legacy Classification features such as creating a class hierarchy, adding classification objects to a classification hierarchy, classifying workspace objects, searching for classification objects, and modifying and deleting objects from a classification hierarchy. Property values that are stored in a storage hierarchy are displayed in a presentation hierarchy 4.1 Teamcenter releases that support them Classification Presentation layer is supported from Teamcenter 11.2 Release onwards 14

16 4.2 Installation with TEM selections Classification Presentation layer is deployed as part of the Library Management feature. For installation instructions of Library Management feature, refer section Installation with TEM selections below. 4.3 Data extension of Classification data into Classification Presentation Layer Extending existing Classification data into the Presentation layer (command examples) Classification data can be extending into the Presentation layer by using following command line utility: clsutility cid=<group_or_class_id> This will extend the Classification sub-hierarchy under the specified Group or Class. a. For Classification Groups, this will create Presentation layer Group Nodes with the same ID as the associated Groups b. For Classification Classes, this will create Presentation layer Master Nodes with storage_class_type property same as their associated Classes Additional optional switches: a. For including ICOs in this sub-hierarchy, users can specify the include_instances switch b. For excluding the sub-hierarchy, and only extend the specified Group or Class, users can specify the exclude_children switch Automatic synchronization between Classification data and the corresponding Presentation layer Classification Presentation Layer supports automatic synchronization with the underlying Classification data (Class hierarchy and ICOs) by shadowing certain operations. Table 1: Mapping between Classification Class and Node hierarchy object types Object types from Classification (Class hierarchy) Group Abstract class Storage class Classification Object (ICO) Corresponding Object types from the Presentation layer (Node hierarchy) Group Node Master Node Master Node Classification Element 15

17 Table 2: Operations mapping between Classification Class and Node hierarchies Operation on Class hierarchy Add / Delete Group Add / Delete Class Add / Delete ICO Operation required on Node hierarchy Add / Delete Group Node Add / Delete Master Node Add / Delete Classification Element There are two conditions that need to be met for automatic synchronization to function: a. Master switch needs to be turned ON, by setting preference CLS_auto_sync_node_hierarchy = TRUE b. The source object (Classification Group / Class / ICO) that will trigger the Auto sync, will need to have a link established: a. A Group Node has the same ID as the Classification Group b. A Master Node has the storage_class_type property pointing to the associated Classification Class c. A Classification Element will refer to the associated ICO Once these conditions are met, then the changes to each of the source objects will be reflected on the corresponding objects in the Presentation layer 4.4 Co-existence of Classification data with the Presentation layer by establishing linkages (recommendations) Classification Class (storage) hierarchy and the Node (presentation) hierarchy can be kept in-sync by either of the following methods: a. Manual execution of clsustility [see Extending existing Classification data into the Presentation layer (command examples)] b. Enabling Automatic synchronization [see Automatic synchronization between Classification data and the corresponding Presentation layer] 4.5 Supported scenarios in Active Workspace Search and Browse Classification hierarchy using Visual Navigation Cards (VNC) Visual Navigation cards allows users to configure displaying of larger images while rendering the selected level in the Classification node hierarchy. More information can be found in Active Workspace documentation here 16

(Video) Websites H𐌀𐌂𐌊𐌉𐌍g for Beginners | Full Course | 2022

18 Figure 3: Visual Navigation Cards (VNC) shown for Classification filter after drilling down the hierarchy Configuration options Administrators can configure the properties displayed on the VNC using standard configuration mechanism used for Tiles. To achieve this, administrators will use following Teamcenter object types to configure the Classification hierarchy tiles: Cls0HierarchyNode 17

19 5 Libraries Management A library holds classification data that is filtered to suit a particular business need. Libraries present only a subset of classified data, hiding irrelevant or sensitive data and simplifying access to the data. Conceptually, you can consider a library as a layer on top of the presentation hierarchy exposing only data relevant to a particular domain or activity. You can expose the same data in multiple libraries and each library can contain multiple hierarchies. A hierarchy is composed of library nodes. A classifying library node references a node in the presentation hierarchy which, in turn, references a storage class. Additionally, you can store non-classified data in separate library nodes. For snapshot of the sample data please refer to the Sample Data Creation section below, 5.1 Teamcenter releases that support them Teamcenter Library Management is available from Teamcenter 11.x onwards 5.2 Installation with TEM selections A new category, Reuse and Standardization, is added to the Teamcenter installation menu. Under this category, you find the option to install Library Management. Library Management installs a data model and functionality that supports creating and configuring multiple libraries to meet the reuse needs of business processes and targeted sets of users. Library Management leverages Classification and includes a rules-based search capability for enforcing technical constraints in the context of a design process (known as Specifications, which is a distinct and separate feature from Specification Manager used to support the Consumer Packaged Goods industry). 18

20 The lbrmanager command line utility is also included with this feature. Note Deploying the Library Management feature automatically deploys the following prerequisite features: Advanced PLM Services for Applications Advanced PLM Services for Partitioning Advanced PLM Services for Realization Next Generation Classification foundation Library Management installation does not affect data dictionaries from a functionality or content perspective. Data dictionaries continue to be supported as an independent capability in Teamcenter. 5.3 Administering Libraries To administrator Libraries, currently Administrators have to use a command line interface Create/Display/Publish/Retract Library objects Create a Standalone Library lbrmanager -u=<userid> -p=<password> -g=<group> -create -library - id=mechanicalpartslibrary -name=mechanicalpartslibrary -descr=" Mechanical Parts Library " -type=domain -disciplines="mechanical,electrical" For more about above command: lbrmanager - u=<userid> -p=<password> -g=<group> -create -library -h For displaying a Library lbrmanager -u=<userid> -p=<password> -g=<group> -show -libraries - id=mechanicalpartslibrary 19

21 Create a Hierarchy lbrmanager -u=<userid> -p=<password> -g=<group> -create -hierarchy - id=fixtureshierarchy -name=fixtureshierarchy -descr="fixtures Hierarchy" - libraryid=mechanicalpartslibrary For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -create hierarchy h For displaying a Hierarchy lbrmanager -u=<userid> -p=<password> -g=<group> -show -hierarchies - libraryid=mechanicalpartslibrary -id=fixtureshierarchy Create a Library Node lbrmanager -u=<userid> -p=<password> -g=<group> -create -node -id=assemblies - name=assemblies -descr="all Assemblies" -libraryid=mechanicalpartslibrary - hierarchyid=fixtureshierarchy For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -create node h For displaying a Node lbrmanager -u=<userid> -p=<password> -g=<group> -show -nodes - libraryid=mechanicalpartslibrary -id=assemblies Create a child Library Node lbrmanager -u=<userid> -p=<password> -g=<group> -create -node -id=baseplate - name=baseplate -descr="base Plate" -libraryid=mechanicalpartslibrary - hierarchyid=fixtureshierarchy -parentnodeid=assemblies For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -create node h For displaying a Node lbrmanager -u=<userid> -p=<password> -g=<group> -show -nodes - libraryid=mechanicalpartslibrary -id=baseplate 20

22 Display the above created Library lbrmanager -u=<userid> -p=<password> -g=<group> -show -libraries - id=mechanicalpartslibrary [MechanicalPartsLibrary] MechanicalPartsLibrary Library created in command 1 -[FixturesHierarchy] FixturesHierarchy Hierarchy created in command 2 -[Assemblies] Assemblies Node created in command 3 -[BasePlate] BasePlate Child Node created in command Publish an Item to create a Library Element Prerequisite Data: Create two Item [ name, id] as BasePlateItem1, BasePlateItem Create a text file as BasePlate.txt Content of BasePlate.txt -type=item -mfkpropnames=item_id -item_id=baseplateitem1 -elempropnames=lbr0elementid -lbr0elementid=baseplatele01 -type=item -mfkpropnames=item_id -item_id=baseplateitem2 -elempropnames=lbr0elementid -lbr0elementid=baseplatele02 lbrmanager -u=<userid> -p=<password> -g=<group> -publish -objectsfromfile - libraryid=mechanicalpartslibrary -nodeid=baseplate -inputfile=baseplate.txt For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -publish h For displaying a Library with Library Element: lbrmanager -u=<userid> -p=<password> -g=<group> -show -nodes - libraryid=mechanicalpartslibrary -id=baseplate [MechanicalPartsLibrary] MechanicalPartsLibrary Library created in command 1 -[FixturesHierarchy] FixturesHierarchy Hierarchy created in command 2 -[Assemblies] Assemblies Node created in command 3 -[BasePlate] BasePlate Child Node created in command 4 ->[BasePlateLE01] BasePlateItem Element created in command 6 ->[BasePlateLE02] BasePlateItem Element created in command Retract an Item to remove a Library Element lbrmanager -u=<userid> -p=<password> -g=engineering -retract -byelementkey - libraryid=mechanicalpartslibrary -nodeid=baseplate -elementids=baseplatele01 For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -retract -h 21

23 Instantiate a Library Element into a Collaborative Design Prerequisite Data: Create Collaborative design, whose ID is DesignID01 lbrmanager -u=<userid> -p=<password> -g=<group> -instantiate -test - designid=designid01-libraryid=mechanicalpartslibrary -elementid=baseplatele02 For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -instantiate -h Setup membership rules lbrmanager -u=<userid> -p=<password> -g=<group> -create memberrule name=testrule nodeid=baseplate -libraryid=mechanicalpartslibrary propname=sml01001 sml01001= steel For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -create memberrule -h Evaluate membership rules lbrmanager -u=<userid> -p=<password> -g=<group> -evaluate -memberrules - libraryid=mechanicalpartslibrary For more about above command: lbrmanager -u=<userid> -p=<password> -g=<group> -evaluate memberrules -h 5.4 Supported scenarios in Active Workspace In addition to Teamcenter components, configuring Library Management on Active Workspace requires deploy of following additional feature templates using TEM a. Deploy Indexing and Configuration features on Server Select following from the Active Workspace > Server Extensions branch within the Feature tree This will ensure correct configuration of all the Indexing parameters for Classification and Library Management artifacts. 22

24 Additionally, all the necessary preferences and other configuration for display are also configured. b. Deploy Client features Select following from the Active Workspace > Client branch within the Feature tree This will ensure all the Client functionality relative to Classification and Library Management features is contributed to the Client deployment Deploying Library Management Server feature will configure Indexing of Libraries Indexing of Library Elements, which will include o Element ID, Name o Associated Classification Attributes o Associated Classification Node hierarchy Tile configuration for following object types o Library o Hierarchy o Hierarchy Nodes Style-sheets for following object types o Library Element with Classification Properties and the underlying Library Object section o Item Revisions will also include Library Element section For detailed comparison of indexing options, refer to the Deployment options section. 23

25 5.4.1 Search and Browse Library contents using Visual Navigation Cards (VNCs) Visual Navigation cards allows users to configure displaying of larger images while rendering the selected level in the Classification node hierarchy. More information can be found in Active Workspace documentation here Figure 4: Tools Library "location" shown in "Search and Browse" mode Configuration options Administrators can configure the properties displayed on the VNC using standard configuration mechanism used for Tiles. To achieve this, administrators will use following Teamcenter object types to configure the Classification hierarchy tiles: Lbr0Library (top level of a Library structure) Lbr0Hierarchy (2 nd level of a Library structure) Lbr0HierarchyNode (remaining levels of a Library structure) 24

26 5.5 Extend the same example hierarchy from Next Generation Classification # Create Library: "Resources Library" lbrmanager -u= -p= -g= -create library -id=mrm_lib -name="resources" - descr="resources Library" -administrators=infodba # Create Hierarchy: "Fixtures" lbrmanager -u= -p= -g= -create hierarchy -libraryid=mrm_lib -id=mrm_fixt_root -name=fixtures -descr="fixtures Hierarchy" # Create Library Nodes and Members lbrmanager -u= -p= -g= -create -nodesfromclassification -libraryid=mrm_lib - hierarchyid=mrm_fixt_root includeinstances -clsnodeid=fixt # Create Hierarchy: "Machines" lbrmanager -u= -p= -g= -create hierarchy -libraryid=mrm_lib -id=mrm_mach_root -name="machines" descr="machines Hierarchy" # Create Library Nodes and Members lbrmanager -u= -p= -g= -create -nodesfromclassification -libraryid=mrm_lib - hierarchyid=mrm_mach_root includeinstances -clsnodeid=mdl # Create Hierarchy: "Factory Resources" lbrmanager -u= -p= -g= -create hierarchy -libraryid=mrm_lib - id=mrm_frl_res_root -name="factory Resources" -descr="factory Resources Hierarchy" # Create Library Nodes and Members lbrmanager -u= -p= -g= -create -nodesfromclassification -libraryid=mrm_lib - hierarchyid=mrm_frl_res_root -includeinstances -clsnodeid=frl # Create Library: "Tools Library" lbrmanager -u= -p= -g= -create library -id=tools_lib -name="tools Library" - descr="tools Library" -administrators=infodba # Create Hierarchy: "Tools" lbrmanager -u= -p= -g= -create hierarchy -libraryid=tools_lib - id=mrm_tools_root -name=tools descr="tools Hierarchy" # Create Library Nodes and Members lbrmanager -u= -p= -g= -create -nodesfromclassification -libraryid=tools_lib - hierarchyid=mrm_tools_root -includeinstances -clsnodeid=tool_mrl 25

(Video) How To Series, Remarkable: Organize And Manage Your Files

27 6 Specifications Management Specifications are design or component selection guidelines set up by expert users for a particular domain or discipline. Using specifications provides a rule-based configuration that guides you in finding only those components suitable to a particular design situation, for example, Find a pump suitable for a high pressure oil pipe and NPS=4. The specifications are typically applied while searching the library using specification information as additional input. Specifications are created in the context of a library and can be associated to one or more libraries. They are revisable. 6.1 Teamcenter releases that support them Specifications Management is supported from Teamcenter 11.2 Release onwards 6.2 Installation with TEM selections Specifications Management is included and deployed as part of the Library Management feature. For installation instructions of Library Management feature, refer section Installation with TEM selections. 6.3 Supported scenarios in Active Workspace Specifications Management is currently exposed via TC Programmatic Interface in RAC and other custom applications. Active Workspace does not currently expose the Specifications Management functionality. 26

28 7 Classification and Library Management Apps in Active Workspace 7.1 Deployment options Administrators will be able to choose from following server features for Indexing and configuration of Classification and Library Management applications: Table 3: Functional comparison for Server Features Server Feature Next Generation Functions Library Classification Classification Management (Presentation layer) Index Classification Attributes Index Classification Classes Index classifying objects Hierarchical filtering of Classes Index Catalog data Index Library Elements Visual Navigation Cards (VNC) for Classes Visual Navigation Cards (VNC) for Library Nodes Compatible Client Feature (see table below) Classification client Library Management client 27

29 Table 4: Minimum Release matrix for various Functions Functions Classification Server Feature Next Generation Classification (Presentation layer) Library Management Index Classification Attributes AW 2.1 Index Classification Classes AW 2.1 Index classifying objects AW 2.1 Hierarchical filtering of Classes AW 3.1 [Tc / Tc11.2.2] Index Catalog data AW 3.3 [Tc11.2.3] Index Library Elements AW 3.0 [Tc11.2.1] Visual Navigation Cards (VNC) for Classes Visual Navigation Cards (VNC) for Library Nodes AW 3.2 [Tc11.2.3] AW 3.0 [Tc11.2.1] Following client side features will expose the above server components Table 5: Functional comparison for Client Features Functions Classification Authoring Browse Classification Class hierarchy using Visual Navigation cards Browse Library hierarchy using Visual Navigation cards Dedicated location for Search and Browse Classification Client Features Library Management 28

30 7.2 Deploying via TEM Following new features are introduced in the Active Workspace > Server Extensions feature group: Dependency Following new features are introduced in the Active Workspace > Client Extensions feature group: Dependency 29

31 8 Common use case examples: 8.1 Indexing Classification Data for Active Workspace search Please refer to section Search in Active Workspace above. 8.2 Extending Classification data Classification Presentation layer Library Management Please follow the value path depicted in the Overview section to gradually and progressive transition into increasing capability of your classified data. The below diagram depicts the Teamcenter Classification maturity model for the customer thereby which customer gets a streamlined user experience. 8.3 Indexing Presentation layer data for Active Workspace search and browse Please refer to section Search and Browse Classification hierarchy using Visual Navigation Cards (VNC) above. 8.4 Indexing Library data for Active Workspace search and browse Please refer to section Search and Browse Library contents using Visual Navigation Cards (VNCs) above. 8.5 Upgrade considerations Classification and Library Management Applications continue to add functionality that can be leveraged by progressively populating additional information into the SOLR database. After upgrading Teamcenter unified or Active Workspace releases, users will continue to get see the preupgrade behavior without having to upgrade the contents of their SOLR database. However, to pick up newer functionality, users will have to upgrade the contents of SOLR. To achieve this, following sequence must be followed to regenerate the SOLR schema and then upgrade it s Pre-upgrade considerations Following steps must be performed manually before upgrade, so some of the Post-Upgrade steps are not required to be performed again, as they will be included in the Upgrade process: Clear SOLR database (to get rid of old data) Remove.XSLT and.xsd files from %TcFTSIndexer_HOME%\working directory 30

32 8.5.2 Post-upgrade considerations Following steps must be performed manually to upgrade the SOLR contents Clear SOLR database (to get rid of old data) Remove.XSLT and.xsd files from %TcFTSIndexer_HOME%\working directory Run bmide_modeltool to generate new schema (xsd,xslt etc.) Note: If preceding steps were performed as part of Pre-upgrade preparations, then this step can be ignored, as TEM will handle this as part of Upgrade Re-index data into SOLR 31

33 9 Sample Data Creation 9.1 Using MRL library For walking through a Sample Data example, we will use the Manufacturing Resource Library that is kitted as part of advanced_installations folder. During this process, we will import the MRL hierarchy first, which will then act as the base Classification data. This will be then extended to the Presentation layer before populating into multiple Libraries. These steps will be executed using command line interface. Figure 5: Snapshot of Classification data extended from base Classification to Presentation layer to Libraries Importing MRL data from the CD Refer to the Installing and configuring the Manufacturing Resource Library section in the Teamcenter 11.3 documentation for instructions on importing the MRL data. NOTE: Access to the above link requires a WebKey Username and Password Extending MRL hierarchy into Presentation layer As detailed in section, the entire MRL hierarchy along with their ICOs can be extended into the Presentation layer by the following command: clsutility import hierarchy -cid=mrm -include_instances 32

34 9.1.3 Creating and populating Libraries from this MRL hierarchy Resource Management hierarchy will be extended into multiple Libraries as such: Resources Library Factory Resources hierarchy Fixtures hierarchy New Resources hierarchy Machining Data Tools Library Tools Hierarchy To do this, these Library and Hierarchy objects will need to be created manually using command line utility: To create a Library, refer section Create a Standalone Library To create a Hierarchy, refer section Create a Hierarchy Then the entire Node hierarchy will need to be extended / imported from Classification Presentation layer using command line utility. There are two ways of doing this 1. Import Node hierarchy without Elements, with Membership Rules a. Import the Node hierarchy Example: lbrmanager create nodesfromclassification libraryid= ResourcesLib hierarchyid= FactoryRes clsnodeid=frl b. Setup Membership rules For details, please refer the Setup membership rules section c. Evaluate Membership rules For details, please refer the Evaluate membership rules section 2. Import Node hierarchy with Elements, without Membership Rules Example: lbrmanager create nodesfromclassification libraryid= ResourcesLib hierarchyid= FactoryRes clsnodeid=frl -includeinstances 33

35 10 Install Configuration Steps in Active Workspace Step by step 10.1 Traditional Classification Indexing Objective - o To index the Traditional classification data in Active Workspace. TEM selections - o Active Workspace > Server Extensions > Reuse and Standardization > Classification Server o Active Workspace > Client > Reuse and Standardization > Classification Client Enable Classification Search o o o o Once above Templates are deployed, following constants will be automatically set by the deployment. (Optionally one can check if they are set correctly via BMIDE. These are required for successful Classification search in AW.) Turn on the Classification Search feature by setting the Awp0SearchClassifySearchEnabled business object type constant to true at the workspaceobject level. Specify that Classification data is indexed by setting the Awp0SearchIsClassifyDataIndexed business object type constant to true at the ItemRevision level. The object type on which it is set is indexed for searching. All subtypes inherit the setting. Be sure that the Awp0SearchIsIndexed business object type constant is set to true at the ItemRevision level. The object type on which it is set is indexed for searching. All subtypes inherit the setting. Creating Search Index Views (Optionally one can check if they are set correctly) o o Search index views are necessary for marking the classification data as indexable and facetable. Make sure the Preference is set - ICS_searchindex_view_visible = TRUE o Run following command to create the search indexing view smlutility -create_indexing_views [-u=user-id] [-p=password] [-g=group] [-reportfile=file-name] [-listids=class-id] [-delimiter=user-specified-delimiter] [- recursive] E.g. smlutility -create_indexing_views -u= -p= -g=dba -listids=mrm recursive 34

(Video) Managing Microsoft Teams [Exam MS-700] Full Course

36 Regenerate schema o bmide_modeltool.bat -u=username -p=password -g=dba -tool=all -mode=upgrade -target_dir="tc_data " o TcSchemaToSolrSchemaTransform.bat %TC_DATA%\ftsi\solr_schema_files Index the Data - o runtcftsindexer -task=objdata:index Search the data in AW - o Now, search data in AW client o Classification category should be displayed in the filter panel o The category should display the classes in Hierarchical fashion(minimum - AW3.2 + Tc10.1.6/Tc11.2.2) Visual Navigation Cards o Not available with Traditional Classification data (needs atleast Next Generation Classification) Caveats - o These steps will not index the Classification Presentation Layer (Next Generation) classification data o This steps will not index the Library Mgmt. data The setup should not have installed AW s Classification Presentation Layer (Next Generation) classification server and Library Management server template. If installed, there are some additional steps that need to be performed Classification Presentation Layer or Next Gen Classification Indexing Objective - o To index the Presentation layer classification data (Next Generation). TEM selections - o Active Workspace > Server Extensions > Reuse and Standardization > Next Generation Classification Server 35

37 Enable Classification Search - o o o o Following business constants will be automatically set by the deployment with above options. (Optionally one can check if they are set correctly via BMIDE. These are required for successful Classification search in AW.) Turn on the Classification Search feature. Make sure the Awp0SearchClassifySearchEnabled business object type constant to true at the workspaceobject level. Make sure that the Classification data will be indexed, by setting the Awp0SearchIsClassifyDataIndexed business object type constant to true at the Cls0ClassBase level. The object type on which it is set is indexed for searching. All subtypes inherit the setting. Check that search data will get indexed. Be sure that the Awp0SearchIsIndexed business object type constant is set to true at the Cls0ClassBase level. The object type on which it is set is indexed for searching. All subtypes inherit the setting. Creating Search Index Views o If extending from Traditional Classification setup (Classification Server), then just double check the following. If new installation, then perform the all the following steps. o Set preference - ICS_searchindex_view_visible = TRUE o Run command smlutility -create_indexing_views [-u=user-id] [-p=password] [-g=group] [-reportfile=file-name] [-listids=class-id] [-delimiter=user-specified-delimiter] [- recursive] E.g. smlutility -create_indexing_views -u= -p= -g=dba -listids=mrm recursive Regenerate schema o bmide_modeltool.bat -u=username -p=password -g=dba -tool=all -mode=upgrade -target_dir="tc_data " o TcSchemaToSolrSchemaTransform.bat %TC_DATA%\ftsi\solr_schema_files Extend Classification data to presentation layer o Run, clsutility -import hierarchy cid=<class_id> o Please note: We had following access related issue for -include_instances, It is now fixed in Teamcenter 11.4 & 12.0_b. o Run below steps for Pre Teamcenter 11.4 and Teamcenter 12.0_b Release First run without -include_instances, this will ONLY extend classic Classification class hierarchy into classification presentation node hierarchy. E.g.: clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy -cid=icm 36

38 Second run with -include_instances, this will extend ONLY ICOs into already extended classification presentation node hierarchy. For this run, please use user credential, who has created the ICOs. E.g.: clsutility.exe -u=user_has_write_access_ico -p=pw_ user_has_write_access_ico -g=dba -import -hierarchy -cid=icm - include_instances o Or Run a single step for Release later than Teamcenter 11.4 and Teamcenter 12.0_b Release For including ICOs in this sub-hierarchy, users can specify the include_instances switch E.g. clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy - cid=icm -include_instances -output=d:\apps_server\temp\clsutility_log.log -show_all_errors > D:\apps_server\temp\clsoutput.txt o If you face any errors during running the clsutility, please refer Troubleshooting / Issues Catalogue section in Classification and Library Management: One-Stop Guide for workaround o Only after successfully extending Traditional Classification to Classification Presentation layer successfully and error free, Finally, make sure the Preference CLS_auto_sync_node_hierarchy = True, for any new data to be automatically synced and extended. Index the Data - o runtcftsindexer -task=objdata:index Search the data in AW - o Now, search data in AW client o Classification category should be displayed in the filter panel o The category should display the classes in Hierarchical fashion (Minimum - AW3.2 + Tc11.2) Visual Navigation Cards o Available for Classification Presentation Layer depending on the minimum Teamcenter version (but Library VNC s will not be available here as Library Management is yet not deployed) 37

39 Caveats o These steps (above) will not index the Library data as it is still not deployed Library Management Indexing Objective - o To index the classification Libraries data. TEM selections - o Active Workspace > Server Extensions > Reuse and Standardization > Library Management Server o Active Workspace > Client > Reuse and Standardization > Library Management Enable Classification Search - o o o o Following business constants will be automatically set by the deployment. (Optionally one can check if they are set correctly via BMIDE. These are required for successful Classification search in AW.) Turn on the Classification Search feature. Make sure the Awp0SearchClassifySearchEnabled business object type constant to True at the workspaceobject level. Make sure that the Classification data will be indexed, by setting the Awp0SearchIsClassifyDataIndexed business object type constant to True at the Lbr0LibraryElement level. The object type on which it is set is indexed for searching. All subtypes inherit the setting. Check that search data will get indexed. Be sure that the Awp0SearchIsIndexed business object type constant is set to True at the Lbr0Library level, and Lbr0LibraryElement level. The object types on which it is set is indexed for searching. All subtypes inherit the setting. Creating Search Index Views o If extending from Traditional Classification setup (Classification Server), or Classification Presentation (Next Generation classification) - then just double check the following. If new installation, then perform the all the following steps. o Set preference - ICS_searchindex_view_visible = TRUE o Run command smlutility -create_indexing_views [-u=user-id] [-p=password] [-g=group] [-reportfile=file-name] [-listids=class-id] [-delimiter=user-specified-delimiter] [- recursive] E.g. smlutility -create_indexing_views -u= -p= -g=dba -listids=mrm recursive 38

40 Regenerate schema o bmide_modeltool.bat -u=username -p=password -g=dba -tool=all -mode=upgrade -target_dir="tc_data " o TcSchemaToSolrSchemaTransform.bat %TC_DATA%\ftsi\solr_schema_files Extend Classification data to Presentation Layer o If extending from Classification Presentation layer (Next Gen level), then no need to perform these steps. Else run following steps for new installation o Run clsutility -import hierarchy cid=<class_id> o Please note: We had following access related issue for -include_instances, It is now fixed in Teamcenter 11.4 & 12.0_b. o Run below steps for Pre Teamcenter 11.4 and Teamcenter 12.0_b Release First run without -include_instances, this will ONLY extend classic Classification class hierarchy into classification presentation node hierarchy. E.g.: clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy -cid=icm Second run with -include_instances, this will extend ONLY ICOs into already extended classification presentation node hierarchy. For this run, please use user credential, who has created the ICOs. E.g.: clsutility.exe -u=user_has_write_access_ico -p=pw_ user_has_write_access_ico - g=dba -import -hierarchy -cid=icm -include_instances o Or Run a single step for Release later than Teamcenter 11.4 and Teamcenter 12.0_b Release For including ICOs in this sub-hierarchy, users can specify the include_instances switch E.g. clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy - cid=icm -include_instances -output=d:\apps_server\temp\clsutility_log.log -show_all_errors > D:\apps_server\temp\clsoutput.txt o Only after successfully extending Traditional Classification to Classification Presentation layer successfully and error free, Finally, make sure the Preference CLS_auto_sync_node_hierarchy = True, for any new data to be automatically synced and extended. 39

41 Extending Library Management data from Classification Presentation (Next Gen) data o lbrmanager -u= -p= -g= -create -nodesfromclassification -libraryid=<library_id> - hierarchyid=<hierarchy_id> -includeinstances -clsnodeid=<cls Node ID> Index the Data - o runtcftsindexer -task=objdata:index Search the data in AW - o Now, search data in AW client o Library and Classification categories should be displayed in the filter panel o The category should display the classes in Hierarchical fashion (Minimum - AW3.2 + Tc11.2) Visual Navigation Cards o Should be now available for Classification Presentation Layer and Library Management Layer Bulk Import of Classification Data into Classification Presentation Layer (Next Generation Classification) If a bulk import of Classification data is being planned using TCXML/PLMXML import into Classification Presentation layer, then please flow below steps 1. Make sure the Preference CLS_auto_sync_node_hierarchy is set to False before import 2. Perform the TCXML/PLMXML import process for bulk import in Traditional Classification Layer, follow tdoc instructions for Importing hierarchy data to perform import process. Creating Search Index Views o If extending from Traditional Classification setup (Classification Server), then just double check the following. If new installation, then perform the all the following steps. o Set preference - ICS_searchindex_view_visible = TRUE o Run command smlutility -create_indexing_views [-u=user-id] [-p=password] [-g=group] [-reportfile=file-name] [-listids=class-id] [-delimiter=user-specified-delimiter] [- recursive] E.g. smlutility -create_indexing_views -u= -p= -g=dba -listids=mrm recursive 40

42 Regenerate schema o bmide_modeltool.bat -u=username -p=password -g=dba -tool=all -mode=upgrade -target_dir="tc_data " o TcSchemaToSolrSchemaTransform.bat %TC_DATA%\ftsi\solr_schema_files Extend Classification data to presentation layer o Run, clsutility -import hierarchy cid=<class_id> o Please note: We had following access related issue for -include_instances, It is now fixed in Teamcenter 11.4 & 12.0_b. o Run below steps for Pre Teamcenter 11.4 and Teamcenter 12.0_b Release First run without -include_instances, this will ONLY extend classic Classification class hierarchy into classification presentation node hierarchy. E.g.: clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy -cid=icm Second run with -include_instances, this will extend ONLY ICOs into already extended classification presentation node hierarchy. For this run, please use user credential, who has created the ICOs. E.g.: clsutility.exe -u=user_has_write_access_ico -p=pw_ user_has_write_access_ico - g=dba -import -hierarchy -cid=icm -include_instances o Or Run a single step for Release later than Teamcenter 11.4 and Teamcenter 12.0_b Release For including ICOs in this sub-hierarchy, users can specify the include_instances switch E.g. clsutility.exe -u=infodba -p=infodba -g=dba -import -hierarchy - cid=icm -include_instances -output=d:\apps_server\temp\clsutility_log.log -show_all_errors > D:\apps_server\temp\clsoutput.txt o Only after successfully extending Traditional Classification to Classification Presentation layer successfully and error free, Finally, make sure the Preference CLS_auto_sync_node_hierarchy = True, for any new data to be automatically synced and extended. Index the Data - o runtcftsindexer -task=objdata:index 41

View more

(Video) Liberty - Softlink Library Management Software

Videos

1. The Best Way to Manage Files and Folders (ABC Method)
(Simpletivity)
2. Tools for Dewey Decimal Classification | Summaries | OCLC Classify | Dewey Cutter | Electronic DDC
(RAFLIMTS)
3. 📚 How to use SharePoint Document Library - Beginners Tutorial
(Kevin Stratvert)
4. The Silva Mind Control Method Audiobook by José Silva (1960) ft.David Wong Dynamic Meditation System
(David Wong - Qi Life Mastery)
5. Illinois Driver Handbook - Audio - 2021
(Unofficial DMV Audio)
6. Introduction LC Subject Headings, Part I
(alctsce)

Top Articles

You might also like

Latest Posts

Article information

Author: Ray Christiansen

Last Updated: 12/20/2022

Views: 6077

Rating: 4.9 / 5 (49 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Ray Christiansen

Birthday: 1998-05-04

Address: Apt. 814 34339 Sauer Islands, Hirtheville, GA 02446-8771

Phone: +337636892828

Job: Lead Hospitality Designer

Hobby: Urban exploration, Tai chi, Lockpicking, Fashion, Gunsmithing, Pottery, Geocaching

Introduction: My name is Ray Christiansen, I am a fair, good, cute, gentle, vast, glamorous, excited person who loves writing and wants to share my knowledge and understanding with you.