awc

7/26/2019 awc

1/43

Cognizant EMS - Internal

Table of ontents

Introduction to AWC .................................................................................................................................. 2

Key Features ........................................................................................................................................... 2

Enhancements on AWC 2.4: ................................................................................................................. 2

AWC Architecture: ..................................................................................................................................... 3

Client tier: ............................................................................................................................................... 4

Web tier: .................................................................................................................................................. 4

Enterprise tier: ...................................................................................................................................... 4

TcFTSIndexer: ........................................................................................................................................ 5

Vis Server: ............................................................................................................................................... 5

Resource tier: ......................................................................................................................................... 6

Solr Database: ..................................................................................................................................... 6

Active Workspace Installation: .................................................................................................................. 7

Teamcenter Patch Update: ................................................................................................................... 7

AWC Patch update ................................................................................................................................ 10

AWC Features Installation:.................................................................................................................. 11

Install server extension features: ..................................................................................................... 11

Install Active Workspace Client: .................................................................................................. 17

Installing Indexing Engine: .............................................................................................................. 19

Configuring the setup to start the Active Workspace client on a browser:..................................... 23

Deployment of tc.ear and awc.war files through JBoss:................................................................ 24

Pool manager: .................................................................................................................................... 24

Solr, TcFTSIndexer: ......................................................................................................................... 24

7/26/2019 awc

2/43


Common Errors faced during Teamcenter patch update and AWC patch update:........................ 24

Unable To Unzip XXX.Zip File: ...................................................................................................... 24

Service failed to start. The service did not start due to a logon failure:...................................... 25

The Network Adapter could not establish the connection:........................................................... 26

JBoss 5.1.0 tc.ear deploy error: ....................................................................................................... 27

The Web server had a problem. ...................................................................................................... 27

Active WorkspaceFolder Structure: ................................................................................................... 28

AWS2: .................................................................................................................................................... 28

Build ................................................................................................................................................... 29

Out ...................................................................................................................................................... 30

Repo .................................................................................................................................................... 30

Src ....................................................................................................................................................... 30

Solr-4.4.0: ............................................................................................................................................... 31

Awc ..................................................................................................................................................... 32

contrib ................................................................................................................................................ 33

dist ...................................................................................................................................................... 34

TcFTSIndexer: ...................................................................................................................................... 34

bin ....................................................................................................................................................... 35

conf ..................................................................................................................................................... 36

Configuration of AWC: ............................................................................................................................ 37

Start Teamcenter Pool_manager...................................................................................................... 37

Start JBoss server Manager ............................................................................................................... 37

Start Solr ............................................................................................................................................... 38

Start TcFTSIndexer .............................................................................................................................. 39

7/26/2019 awc

3/43


Introduction to AWC

Active Workspace is a light weight version of Teamcenter with no need for client installation. It has better

performance compared to Rich Client or Thin Client. AWC presents complex structures with animated

graphics on UI. It is available on mobile devices. AWC aims on providing access of PLM data to all users

throughout the products lifecycle by providing an organized and in-built understanding, on any device.

Key Features

Available on mobile devices

Simplified AWC installation -reduced manual steps, simplified TEM, Organize feature selection

and enforce prerequisites

Browser independent

Configurable UI

Ability to print an object

Save and share working context

Context specific RFLP Navigation

Refresh, save / recall diagram content and context

Enhancements on AWC 2.4:

Personalize the Home page layout, grouping or protecting the tiles

Visualize huge models in seconds and analyze the features like measure, cross-section and spatial

searching

Multiple select functionality to cut, copy, reassign tasks or to add/remove an object from

favorites

Create Part tile in the main page for easy navigation

7/26/2019 awc

4/43


AWC Architecture:

No particular architecture for active workspace we are going to deploy AWC on top of Teamcenter

4-Tier architecture. So the base for AWC is Teamcenter 4-Tier architecture.

7/26/2019 awc

5/43


Changes to be made in the Teamcenter 4-Tier architecture to have an add on of AWC will be discussed

in the document

Client Tier

Web Tier

Enterprise Tier

Resource Tier

Client tier:

Client functionality is provided by a user-facing Java EE web application (awc.war) that is built using

TEM and deployed on a Java EE web application server such as JBoss or WebSphere. Users

Connect to the client web application using a web browser.

Web tier:

In the team center 4-tier architecture web tier is used to generate the tc.ear file.

In AWC, awc.war file will be generated in the aws2 folder once the client is installed.

To enable the 3D visualization functionality first we need to install visualization server pool

assigner.

When Visualization server pool assigner feature is selected it mainly installs the middle tier

processes that communicate with the visualization server processes of the Active Workspace

client.

This feature will be present in the Client of AWC as shown in below screenshot.

Enterprise tier:

Mainly two features related to Active Workspace will be present in this tier

TcFTSIndexer

Vis Server

7/26/2019 awc

6/43


TcFTSIndexer:

It is a four tier SOA client used to export Team center data for importing into Solr database. This

server manages overall indexing processes.

The following command can be used to index the object data of team center

runTcFTSIndexer.bat -task=objdata: index

TcFTSIndexer and Solr database will be interconnected and communication between these two

will be referred to as indexing.

Vis Server:

The Visualization Server provides dynamic 3D visualization functionality to the Active Workspace client.

Vis Server will be within the Active Workspace as shown in the below screen shot

Visualization Data Server:

The Visualization Data Server improves Visualization performance by caching visualization data close to

the Visualization Server Manager. It caches product structure, computes Massive Model Visualization

(MMV) spatial hierarchies, and prepopulates JT files in the FCC for faster visualization streaming to the

Active Workspace client. The Visualization Data Server is part of the MMV solution for Active

Workspace.

A single Visualization Data Server can support one or more Visualization Server Managers.

7/26/2019 awc

7/43


Visualization Server Manager

The Visualization Server Manager streams visualization data to the Active Workspace client. It

Manages a pool of rendering processes, starting and stopping processes as needed.

Resource tier:

If Active Workspace under server extensions is selected while installing then it will add binaries to

TC_ROOT and data model changes to the database and TC_DATA. It adds the Active Workspace

(aw2_template.xml) and Relationship Viewer(relationshipviewer_template.xml) templates to the

database.

Solr Database:

Solr is a database which is full text search engine that stores indexed team center data. TcFTSIndexer and

Solr will be communicating in a way like if any indexing is done using TCFTSIndexer then the indexed

data will be stored in solr database.

7/26/2019 awc

8/43


Active Workspace Installation:

To install Active Workspace features of Teamcenter we need to apply AWC patch to the Teamcenter. After the patch

update we can configure the Active Workspace Environment accordingly.

The prerequisites for Active workspace Patch update are:

The base version of Teamcenter is fully installed (Tc10.1.0).

The base version of Teamcenter (10.1.0) should be patched to the compatible Teamcenter version with

active workspace i.e.,Tc10.1.4.

Check the JRE version installed. Oracle and Siemens strongly recommends upgrading to JRE 1.7 for

application like TEM and Pool Manager.

Note: JRE1.7 is required for Browser based clients after Tc9.1.2.7

JDK1.7or above is required for Active Workspace War file generation.

Check if the Environmental variables like JAVA_HOME, JRE_HOME, and ORACLE_HOME are set. If

not, set before proceeding with the installation.

Before proceeding with Teamcenter patch update and AWC patch update download the listed installation packages

from GTAC.

TC10.1.0_patch_4_install.

TC10.1.0_patch_4_wntx64.

TC10.1.4_Activeworkspace_2.4a_wntx64.

Teamcenter Patch Update:

The following procedure will explain how to proceed with the Teamcenter patch update process:

Backup the TC_DATA and TC_ROOT/install folder of the base version Teamcenter setup.

Unzip the installation package (TC10.1.0_patch_4_wntx64 and TC10.1.0_patch_4_install) to a desired

location, preferable to the location where TC_ROOT is available.

Stop all the process and services related to Teamcenter.

Copy the content of TC10.1.0_patch_4_install folder to TC_ROOT/install.

Run TEM.bat from TC_ROOT/install folder and select the Updates Manager from Maintenance window.

7/26/2019 awc

9/43


Under Update kits location, browse to the location where you unzipped the TC10.1.4_patch_4_wntx64

folder up to wntx64 folder and proceed.

7/26/2019 awc

10/43


Operating System user need to enter the password to proceed further. This is needed since Teamcenter use

this specific user to create required services.

Note: The installation process will proceed further even though the wrong credentials are entered, but

installation will fail in the middle. So care should be taken while providing the user credentials.

Teamcenter Administrative user window requires the Teamcenter database credentials to be entered to

proceed with the installation. Provided the wrong credentials, the window will not proceed further. This is

the credentials which you determined during the creation of corporate server while installing Teamcenter

base version.

7/26/2019 awc

11/43


After the installation is completed, the TEM window will prompt for TC_DATA patch up. For that process

unzip the TC10.1.4_patch_4_wntx64\wntx64\tc\data.zip contents to the TC_DATA.

Now the patch update process is completed. To check for the update, check the version of Teamcenter

opening Rich client.

AWC Patch update

Backup the TC_DATA and TC_ROOT/install folder of the updated version Teamcenter setup.

Unzip the installation package (TC10.1.0_activeworkspace_wntx64) to a desired location, preferable to the

location where TC_ROOT is available.

Stop all the process and services related to Teamcenter.

Run TEM.bat from TC_ROOT/install folder and select the Updates Manager from Maintenance window.

Under Update kits location, browse to the location where you unzipped the

TC10.1.4_activeworkspace_wntx64 folder up to wntx64 folder and proceed.

After this operating system user credentials and Teamcenter database credentials are to be provided and

click on the startat the confirmation panel which initiates AWC patch update.

After the installation, unzip the TC10.1.4_activeworkspace_wntx64\wntx64\tc\data.zip contents to the

TC_DATA.

After installing the Teamcenter patch (10.1.4) and AWC (2.4A) patch, one can able to install the AWC features. The

Active workspace can be verified by running the Teamcenter TEM window again and proceeding to the features

window, you can able to see the active workspace appearing as one of the feature.

7/26/2019 awc

12/43


AWC Features Installation:

The order of the AWC feature installation is as follows:

Server Extensions.

Client.

Indexing Server.

Install server extension features:

AWC Server extension features installation add required AWC binaries to the TC_ROOT and adds data model

changes to the database and TC_DATA. It adds the Active Workspace (aw2_template.xml) and Relationship

Viewer (relationshipviewer_template.xml) templates to the database. The prerequisites required to install this

AWC feature are:

64-bit operating system.

64-bit JDK.

Teamcenter with Four tier architecture. (JAVA EE server and JAVA EE web tier).

To install this feature, the procedure to be followed is:

Start TC_ROOT\Tem.bat as administrator. and proceed to the features window.

7/26/2019 awc

13/43


7/26/2019 awc

14/43


In the features under Active workspace under sever extension tab of AWC feature and proceed further by

clicking Next.

7/26/2019 awc

15/43


Teamcenter Administrative Window will ask for user and password. You need to enter credentials of the

database which you created while installing the base version of Teamcenter. The installation will not

proceed if wrong credentials are provided.

In the Indexing Engine user window, you need to enter the credentials for the indexing engine to be used

for Active Workspace indexing.

If the indexing engine is already installed, provide the same user and passwords in the given text

fields and proceed.

If not installed, make note of user and password input you provide in the text fields as the same

will be required while installing Indexing engine and proceed.

7/26/2019 awc

16/43


At the next window, you need to provide the search engine URL .The Search engine general preferred for

Active Workspace is Solr.

If Solr and indexing engine is installed on a machine, provide the URL to access the search

engine for Active Workspace.

If not, change the hostname of the machinehttp://host:port/solrand proceed.

Note: host is the machine designated to run Solr. This is the machine on which the Indexing Engine is

installed.

Port is the port value used by Solr. The default is 8983.

7/26/2019 awc

17/43


Database Template Summary will help you to know about the templates that are being added to the

database after the installation of this feature.

7/26/2019 awc

18/43


Confirmation of the installation by clicking startwill update the TC_ROOT, database and TC_DATA with

notified templates.

Install Active Workspace Client:

After the server extension feature installation, we need to proceed with the installation of Active Workspace client.

Client functionality is provided by a user-facing Java EE web application (awc.war) that is built using

TEM and deployed on a Java EE web application server such as JBoss or WebSphere. Users connect to the client

web application using a web browser.

The prerequisites for active workspace client installation are:

A minimum of 16 GB of free memory to successfully generate the awc.war file. Siemens PLM Software

recommends that the machine used have a minimum of 24 GB. Windows Server operating system.

JDK 64-bit is installed and the JAVA_HOME system environment variable must be set.

The procedure to be followed for the AWC client installation is:

Run the TC_ROOT\tem.bat as administrator and navigate to the features window.

Select Active Workspace Client (Java EE) under client section of Active Workspace feature.

7/26/2019 awc

19/43


The proceeding page is Prerequisites checks page where the environment needed for the Active workspace

client installation is verified by the Teamcenter Environment Manger.

Enter the desired path where the Teamcenter should create log files related to AWC and click Run.

RAM availability and JDK version compatibility are verified further. If you get warning for RAM

availability and passed status for JDK version, the installation will proceed. In other cases like

failed in both checks and failed in JDK version compatibility, the installation will not proceed

further.

The JDK version compatible recommended by siemens for active Workspace is JDK1.7 or above.

Even the RAM availability is around 8GB or more, the installation will proceed.

After the prerequisites check TEM will proceed to the AWC client Settings where the user need to input the

Teamcenter 4-Tier URL, JDK path and Bootstrap URLs.

The data entered used to configure the Awc.war file which needs to be deployed on a web

application server to make the active workspace client work on a web browser.

Any Error in the input data will generate awc.war successfully, but we cannot able to access the

AWC client.

7/26/2019 awc

20/43


Clicking on Startbutton on confirmation will start the installation of AWC client and creation of awc.war

file.

The created awc.war file can be found at TC_ROOT\aws2\stage\out directory which you need to deploy on

a web application server to login to Active workspace client.

Installing Indexing Engine:

Installing the Indexing Engine installs the Solr database. This is a full-text search engine that stores indexed

Teamcenter data. It is installed by selecting the Indexing Engine feature in TEM.

Prerequisites for installing the Indexing Engine:

64-bit operating system

JDK 64-bit or JRE 64-bit.The procedure to be followed for the AWC client installation is:

Run the TC_ROOT\tem.bat as administrator and navigate to the features window.

Select Active Workspace Indexing Engine and Active Workspace Indexer under Indexing server section

of Active Workspace feature.

7/26/2019 awc

21/43


In the Teamcenter Administrative User window input the credentials of Teamcenter database that is created

during the installation of base Teamcenter version.

7/26/2019 awc

22/43


In the Indexing Engine User window, enter the user and password credentials of Solr indexing engine

which you entered during the installation of Active Workspace server extension feature or during Solr

creation.

In the next window Indexing Engine Configuration browse to the location where solr_schema_files are

available. Generally they can be found at TC_DATA\fts\ solr_schema_files and proceed.

If you want to run the indexing engine as a service, check the button install indexing engine as

a service

7/26/2019 awc

23/43


AWC Indexer settings check Standalone Indexing Environment and input the Teamcenter 4-tier URL

which will be configured in the generation of awc.war file to work on AWC client functionality.

The Indexer Type selection window is about the configuration of indexer to work for indexing the object

data or structure data. We can configure the indexer to work for both features for index the data as

required.

7/26/2019 awc

24/43


Object Data Indexer settings window is to input the object data extraction time for which the indexer will

index the data related to the object (created in between the Start time and end time). If no end time is

selected, the indexer will index up to the present system time.

Click on the start on the confirmation page to install the indexing engine feature for the active workspace.

Configuring the setup to start the Active Workspace client on a browser:

After the installation of all the features of active workspace we need to deploy the generated awc.war through

Java EE web application server such as JBoss or WebSphere.

7/26/2019 awc

25/43


For the Active workspace 2.4A and Teamcenter 10.1.4 version the JBoss version supported is jboss -as-

7.1.1.Final where you need to deploy the tc.ear and awc.war files. On a successful deploy we will be able

to login to the Teamcenter and AWC client functionality through browser.

Before logging into the active workspace client check for the following services working:

Pool manager is started or not. If pool manager is running as a service, start through services.msc or

Task manager else run it manually.

Active workspace indexing service Solr, TcFTSIndexer should be started and running successfully.

Deployment of tc.ear and awc.war files is successful.

Deployment of tc.ear and awc.war files through JBoss:

To deploy the Teamcenter EAR file and Active workspace WAR file using JBoss we need to copy the

files generated to the folder...\jboss-as-7.1.1.Final\standalone\deployments\ and running the command

standalone.bat of the jBoss.

The tc.ear file will present in the Teamcenter webtier folder which you created during the four tier

configuration of Teamcenter.\web_Tier\staging1\deployment\tc.ear.

The awc.war file will present in the TC_ROOT\aws2\stage\out\awc.war.

Pool manager:

Start the pool manager service through services.msc or Task Manager\services option.

If service is not present, we need to run the service manually. We need to open the command prompt at

TC_ROOT\poolmanager and run mgrstartconfig.bat which will start the pool manager.

Solr, TcFTSIndexer:

To enable the indexing feature of Teamcenter we need to run the indexing services.

To run Solr, run the runSolr.bat opening the command prompt at TC_ROOT\ solr-4.4.0.

To run TcFTSIndexer, run runTcFTSIndexer.bat opening command prompt at

TC_ROOT\ TcFTSIndexer\bin.

Common Errors faced during Teamcenter patch update and AWC patch update:

Unable To Unzip XXX.Zip File:

The Teamcenter Environment Manager window will throw the error Unable to unzip bin.zip , Unable

to unzip fsc.zip , unable to unzip XXX.zip file

Cause:

Running Teamcenter services like FSC, Server Manager, process that is running due to the last login to the

Teamcenter are still holding the required files and the session is not ended fully.

7/26/2019 awc

26/43

7/26/2019 awc

27/43


The Network Adapter could not establish the connection:

Cause:

When the installation is proceeding and if the database related services are not started or stopped due to other

applications.

Oracle database: In case of oracle database, this error is observed when the oracle listener and oracle sid services

are not started or stopped.

7/26/2019 awc

28/43


Solution:

Need to run services manually through services.msc or through Task Manager.

JBoss 5.1.0 tc.ear deploy error:

Following process need to follow if faced deployment error with JBoss:

In JBOSS 5.1.0 do the following changes

Search for profile.xml file in the location mentioned below

Make the changes From -> To as shown

Add class=java.io.File as shown inside parameter.

The Web server had a problem.

This error will come when you try logging into active workspace when every installation step is done

successfully.

Cause:

Patching active workspace on higher version of Teamcenter

The supported Teamcenter version for Active Workspace 2.4 A is 10.1.4. The installation will proceed

successfully if you try to patch Teamcenter version above 10.1.4 with active workspace 2.4 A.

Solution:

The supported version is needed to be patched. Check the required packages as mentioned and should proceed

further. If not the installation is need to be done from base version which is not optional.

7/26/2019 awc

29/43


Active WorkspaceFolder Structure:

Three folders will be included in TC_ROOT when AWC is installed on top of team center as follows

AWS2

SOLR-4.4.0

TCFTSINDEXER

AWS2:

This folder is related to AWC client. Once the client is installed awc.war file will be generated in the

Out folder.

This awc.war is responsible for the client related functionality

Deploy awc.war using JBOSS or WEBSPHERE and after deploying you can be able to access the URL

and active work space screen appears in the browser.

New customization related projects can be created by using generatModule.cmd. This is simply

called as module generator.Some of the module generator types are as follows.

7/26/2019 awc

30/43


If any customized changes are made and if that changes need to be reflected in thin client then

gwtcompile.cmd command needs to be run so that all the changes will be updated in the awc.war

file and deploy the new war file in jboss then the changes will be reflected in the thinclient.

Build

7/26/2019 awc

31/43


All the java scripts related to client functionality will be present in this folder.

Out

Awc.war file will be generated in this out folder which is responsible for the architectural

information of thin client active workspace.

In the war folder tc.htmlwill be having the information regarding the browser in which thin

client can be opened.

aws2\stage\out\war\thinclient contains all the information related to images of icons and basic

themes like light, dark which appears on thinclient.

All the .classfiles related to the new customization projects will be present JAVAC folder.

Log file related to gwtcompile.cmdwill be generated in log folder.

Repo

All the jar files related to Team center SOA like TcSoaClassification, TcSoaCommon,

TcSoaCore, TcSoaDocumentManagement, TcSoaImportExport, TcSoaVisualization will be

present in this folder.

Src

Any new customization projects related to GWT customization will be added into the source

folder.

7/26/2019 awc

32/43


Solr-4.4.0:

Solr is a database which is full text search engine that stores indexed team center data.

runSolr.bat:

To launch Jetty with the Solr WAR, just run the start.jar

In the batch file there is a command as shown below which will be used to run the start.jar.

This will start up the Jetty application server on port 8983, and use your terminal todisplay the logging information from Solr.

You can see that the Solr is running by loadinghttp://localhost:8983/solr/in your web

browser. This is the main starting point for Administering Solr.

solrWinService.bat:

This batch file mainly used to specify whether to run Solr as a windows service or a manual

start.

Usage: solrWinService.bat -i or -c orr

-i - Installs Solr as a Windows Service.

-c - Simulates Solr Windows Service installs behavior on a console for debug

purpose.
http://localhost:8983/solr/http://localhost:8983/solr/http://localhost:8983/solr/http://localhost:8983/solr/

7/26/2019 awc

33/43


-r - Removes Solr as a Windows Service.

No arguments defaults to -i option

Awc

SolrCloud:

SolrCloud is the name of a set of new distributed capabilities in Solr. Passing parameters to enable these

capabilities will enable you to set up a highly available, fault tolerant cluster of Solr servers. Use

SolrCloud when you want high scale, fault tolerant, distributed indexing and search capabilities.

Solr:

Collection:

On a single instance, Solr has something called a SolrCorethat is essentially a single index. If you want

multiple indexes, you create multiple SolrCores. With SolrCloud, a single index can span multiple Solr

instances. This means that a single index can be made up of multiple SolrCores on different machines.

We call all of these SolrCores that make up one logical index a collection.

7/26/2019 awc

34/43


A collection is essentially a single index that spans many SolrCores, both for index scaling as well as

redundancy. If you wanted to move your 2 SolrCore Solr setup to SolrCloud, you would have 2

collections, each made up of multiple individual SolrCores.

Solr.xml:

This is the primary configuration file Solr looks for when starting. This file specifies the list of

"SolrCores" it should load, and high level configuration options that should be used for all SolrCores.

If no solr.xml file is found, then Solr assumes that there should be a single SolrCore named "collection1"

and that the "Instance Directory" for collection1 should be the same as the Solr Home Directory.

schema.xml:

This file defines the schema for the index including field type definitions with associated analyzers. It

contains details about the fields that you can include in your document and also describes how those

fields can be used when adding documents to the index or when querying those fields.

Zoo.cfg:

Solr embeds and uses Zookeeper as a repository for cluster configuration and coordination - think of it as

a distributed file system that contains information about all of the Solr servers.

contrib

Analysis-extras:

TheInternational Components for Unicode (ICU) plug-in is an essential tool for dealing with

languages other than English.

7/26/2019 awc

35/43


Analysis-extras folder includes integration with ICU for multilingual support, and analyzers for

Chinese and Polish.

Clustering:

The clustering plugin adds support for running multiple redundant servers together in a cluster by running

in a cluster, you can distribute the connection load among several server

Extraction:

Apache Solr Extraction provides a means for extracting and indexing content contained in "rich"

documents, such as Microsoft Word, Adobe PDF, etc.

Langid:

Its purpose is to identify language from documents and tag the document with language code.

The module can optionally map field names to their language specific counterpart

E.g. if the input is "title" and language is detected as "en", map to "title_en".

dist

Solrjis a java client to access solr.

It offers a java interface to add, update, and query the solr index.

TcFTSIndexer:

It is a four tier SOA client used to export Team center data for importing into Solr database. This server

manages overall indexing processes.

7/26/2019 awc

36/43


bin

Tcenv:

In the tcenv folder there will be a batcfh file which will be pointing to the tc_profilevars.

Encryptpass.bat:

If a new user is needed to run TcFTSIndexer , create an encrypted password file by setting an

environment variable, within the console, to the password value.

E.g.: set mytcenv=mytcenv

Then run the encryptPass.bat utility with the -tc argument specifying the Environment variable name

created.

E.g.: encryptPass -tcpassword.

runTCFTSIndexer.bat:

runTcFTSIndexer -task=type:action [additional-arguments]

The main actions provided by structure indexing are:

-task=structure:test

Performs basic tests, such as for Teamcenter logon, FMS connectivity, verifying or downloading

of transform files, Solr schema, and so on. This command must be run exclusively; it cannot be

run concurrently with other exclusive actions.

-task=structure:show

Shows a summary of all configured product configurations.

-task=structure:sync

Performs normal synchronization and delete actions for all product configurations. This command

must be run exclusively. This command queues up all the synchronization actions for the product

configurations. The queued synchronization actions are processed as resource permits.

-task=structure:syncone product-config-UID

Performs normal synchronization and delete actions for a single product configuration UID. This

command must be run exclusively. This command queues up all the synchronization actions

7/26/2019 awc

37/43


for the product configurations. The queued synchronization actions are processed as resource

permits.

-task=structure:recoverfailures

Changes all product configurations with failed states to the ready to Index state or the

marked for Deletion state.

-task=structure:resetall

Downloads the latest transform and schema files, resets all active product configurations to the

Ready To Indexstate, and resets all deleted product configurations to the Marked For Deletion

state. This command must be run exclusively.

-task=structure:reset product-config-UID

Resets the given PRODUCT_CONFIG_UID setting to the Ready To Index or Marked For Deletion

state. This command must be run exclusively.

conf

All the language related property files will be present in configuration folder.

7/26/2019 awc

38/43


Configuration of AWC:

Once AWC features are installed, starting all the required services we can able to login to AWC client

through a web browser.

To start AWC client we need to check the following services.

Teamcenter pool manager.

Server manager like JBoss.

SOLR indexing service.

TcFTS indexer service.

Start Teamcenter Pool_manager

IF the pool_manager service of Teamcenter is working as a service, then start the service through TASK

MANAGER or Services.msc. If not start the pool_manager manually.

To start pool_manager manually,

Open Command prompt though Runas Administrator.

Run cd %TC_ROOT%/pool_manager.

Run mgrstartconfig1.bat file to start the pool_manager manually.

Pre-check that environment variable like TC_ROOT and TC_DATA are pointing to the correct installation

path

Start JBoss server Manager

For the AWC client functionality to be accessible in a browser we need to deploy the generated awc.war

which is created during the installation of AWC client.

7/26/2019 awc

39/43


The supported JBoss for the AWC 2.4 is JBOSS1.7.0

To start JBoss,

Open Command prompt though Runas Administrator.

Run cd jboss_home/bin

Run the command standalone.batb .

HOST_NAME= the hostname where the JBoss configuration is being deployed.

Proper JDK version is needed to run the JBoss, check JDK >1.7 for AWC (browser based client

architecture).

Start Solr

For the AWC indexing feature to work we need SOLR running in the background. We need to run the

Solr service manually if it is not installed as a service.

To start Solr Manually,

Open another Command Prompt through Run as Administrator. Run cd %TC_ROOT%/solr-4.4.0

Run runsolr.bat file to start the Solr indexing service.

7/26/2019 awc

40/43


Start TcFTSIndexer

Search feature of AWC is enabled by proper object data indexing which is achieved through the TcFTS

indexer service. If indexing is not properly done, the search feature will not work. The output from AWC

client will be.

To enable it, start the Teamcenter TcFTSIndexer service.

To Start and check the status of this service,

Open another Command Prompt through Run as Administrator.

Runcd %TC_ROOT%/TcFTSindexer/bin.

Run TcFTSIndexer.bat file with the arguments as runTcFTSIndexer task=objdata:test. If it

gets succeeded the result will be as shown.

Next Run the command runTcFTSIndexer task=objdata:index to index the object data for

the first time.

7/26/2019 awc

41/43


On successful completion of the indexing process, the command prompt will show the below status.

To synchronize the object data in specific interval of time we need to run the command

runTcFTSIndexer task=objdata:syncinterval=25which synchronize the data for every 25

seconds.

While running the TcFTSIndexer again ti index we need to run the reindex command

runTcFTSIndexertask=objdata:reindex instead of index command in the step 4which index

the data that is not indexed instaed of indexing from the first.

7/26/2019 awc

42/43


Procedure to Enable the Full Text search

Navigate to the conf folder in the TcFTsIndexer Folder in %Tc_Root% directory.

Ex: E:\Siemens\Teamcenter10\TcFTSIndexer\conf

Open the properties file TcFtsIndexer_objdataSearch for the

indexDatasetFileContent property which Specifies whether to process or skip dataset file

content indexing. By default its value is False

Enable it by changing the value to True.

7/26/2019 awc

43/43

Open a new Teamcenter command window and navigate to the TC_ROOT\TcFTSIndexer\bin

directory. Run the following runTcFTSIndexer utility command.To perform a new, full index

without deleting the existing indexed data

runTcFTSIndexer -task=objdata:index

To clear the existing full-text search data and perform a new, full index.

runTcFTSIndexer -task=objdata:reindex

.Open the active workspace client on a web browser and search for a key word that is available in

any dataset attached. Now you will be able to view all the datasets that contain the search word in

the search results pane of workspace client.

Before Enabling i.e: TcFtsIndexer_objdata=false.

After enabling it the search results:

Documents

awc