Teamcenter 13.

Application
Registry
TSS00002 - 13.0
 Contents

Overview of Application Registry

Overview of Application Registry ─────────────────────────── 1-1
System requirements ─────────────────────────────────── 1-1
Preparing for installation ──────────────────────────────── 1-1

Installing Application Registry

Configuring Application Registry parameters ──────────────────── 2-1
Determine installation parameter values ──────────────────────────
2-1
Modify Web service installation parameters ────────────────────────
2-1
Deploy the Application Registry Web service ──────────────────── 2-3
Verify Application Registry installation ──────────────────────── 2-3

Application Registry, Teamcenter 13.0 TSS00002 13.0 2

© 2020 Siemens
 1. Overview of Application Registry
Overview of Application Registry
Application Registry is a service that allows Teamcenter applications to register and look up other
available applications and provide a variety of data sharing functions that include the following:

• Register an application instance (that is, a single installation of a product).

• Look up available application instances.
• Unregister an application instance.

Before you install Application Registry, make sure your system contains the required software, and then
extract the Application Registry package file to a local directory.

System requirements
Application Registry works with the following Teamcenter products:

• Teamcenter (all versions)

• Engineering Process Management
• Teamcenter Enterprise
• Portfolio, Program and Project Management
• Systems Engineering and Requirements Management

Application Registry requires a Web application server.1 For information about Web application server
support for Teamcenter products, see the Hardware and Software Certifications knowledge base article
on Support Center.

Note:
If you use Application Registry with Teamcenter Enterprise, make sure you install the PUP Server
(PUP) module on your Teamcenter Enterprise corporate server and also install Teamcenter
Interface on your Web application server.

Preparing for installation

Application Registry is distributed as a package file named
TeamcenterApplicationRegistry_v2007_JRE142.zip available for download from the software
downloads area on Support Center. Extract the full contents of this file using any ZIP extraction tool or,
alternatively, using the following Java jar command:

JAVA_HOME\bin\jar xvf TeamcenterApplicationRegistry_v2007_JRE142.zip

1 Siemens Digital Industries Software supports Application Registry on all Web application servers supported for use with
Teamcenter products.

Application Registry, Teamcenter 13.0 TSS00002 13.0 1-1

© 2020 Siemens
 1. Overview of Application Registry

Note:
These procedures use Windows path and command syntax except where otherwise specified. On
Linux systems, replace backslashes (\) with slashes (/).

The archive contains the TeamcenterApplicationRegistry_v2007_JRE142 directory, which contains the

following directories.

Directory Description

client Client library and WSDL interface to Application Registry.

server ApplicationRegistry.war file.

libs Additional libraries required by the server and client.

test Test application for verifying Application Registry

This guide refers to the TeamcenterApplicationRegistry_v2007_JRE142 directory as pkg.

To install Application Registry, you need the pkg\server\ApplicationRegistry.war file. Some application
servers may also require one or more JAR files from the pkg\libs directory.

1-2 TSS00002 13.0 Application Registry, Teamcenter 13.0

© 2020 Siemens
 2. Installing Application Registry
Configuring Application Registry parameters

Determine installation parameter values

Determine the appropriate values for Application Registry installation parameters. You set these
parameters in Modify Web service installation parameters.

• ApplicationRegistryStorageDir
Set this parameter to the full path of the directory in which you want Application Registry to store
contact information for each registered application, for example, /ApplicationRegistryStorage/
contactInfoStorage. The default value of this parameter is change-me-storage-dir.

• ApplicationRegistryLogDir
Set this parameter to the full path of the directory in which you want Application Registry to store log
files, for example, /ApplicationRegistryStorage/logs. The default value of this parameter is change-
me-log-dir.

• ApplicationRegistryLogLevel
This parameter controls the amount of information recorded to the log directory. The valid log level
values are as follows:

• Disabled: Disable logging.

• Fatal: Record fatal error messages only.
• Error: Record error messages also.
• Warn: Record warning messages also.
• Info: Record information messages also.
• Debug: Record debugging messages also. This setting records the maximum amount of log
information.

The default value of this parameter is Info.

Note:
On Linux systems, ensure that the application server user (usually nobody:nobody) has write
access to the ApplicationRegistryStorage directory. For example:

chown -R nobody:nobody /usr/ApplicationRegistryStorage

Modify Web service installation parameters

Modify Application Registry installation parameters as needed in the web.xml file.

Application Registry, Teamcenter 13.0 TSS00002 13.0 2-1

© 2020 Siemens
 2. Installing Application Registry

Some Web application servers support editing Web service configuration parameters through a
graphical interface, but others do not. For information about modifying Web service configuration
parameters using a graphical interface, see the documentation for your Web application server.
Alternatively, you can modify Web service configuration parameters manually by performing the
following steps.

Note:
• The following steps work for all supported Web application servers.

• In the following steps, replace TEMP with the name of a temporary directory. Replace
JAVA_HOME with your Java home directory.

1. Extract the Application Registry WAR file to a temporary directory by entering the following
commands:

mkdir TEMP\ApplicationRegistry2
cd TEMP\ApplicationRegistry2
JAVA_HOME\bin\jar xvf pkg\server\ApplicationRegistry.war

2. Configure Application Registry installation parameters:

a. Open the following file for editing:

TEMP\Application Registry2\WEB-INF\web.xml

b. Locate the following text:

<servlet>
<servlet-name>ApplicationRegistryServlet</servlet-name>
<display-name>Teamcenter Application Registry Service</
display-name>
<description>Teamcenter Application Registry Service</description>
<servlet-class>

COM.inovie.services.integration.applicationRegistry.server.ApplicationRegistrySe
rvlet
</servlet-class>
<init-param>
<param-name>ApplicationRegistryStorageDir</param-name>
<param-value>change-me-storage-dir</param-value>
</init-param>
<init-param>
<param-name>ApplicationRegistryLogDir</param-name>
<param-value>change-me-log-dir</param-value>
</init-param>
<init-param>
<param-name>ApplicationRegistryLogLevel</param-name>
<param-value>Info</param-value>
</init-param>
</servlet>

2-2 TSS00002 13.0 Application Registry, Teamcenter 13.0

© 2020 Siemens
 Deploy the Application Registry Web service

c. Replace change-me-storage-dir, change-me-log-dir, and Info with the appropriate values

for ApplicationRegistryStorageDir, ApplicationRegistryLogDir, and
ApplicationRegistryLogLevel.

3. Rebuild the Application Registry WAR file by entering the following commands:

cd TEMP\ApplicationRegistry2
JAVA_HOME\bin\jar cvf ApplicationRegistry.war *.*

Deploy the Application Registry Web service

Deploy the Application Registry Web service file, pkg\server\ApplicationRegistry.war, as documented
for your Web application server. Make sure you define the context root as /ApplicationRegistry.

Start the Application Registry Web service if it does not start up automatically. Some Web application
servers must be shut down and restarted to load configuration changes.

Verify Application Registry installation

To verify Application Registry installation, open the following URL in a Web browser:

http://host-name:port/ApplicationRegistry/

Note:
Some Web application servers require that the URL end with a slash (/). On other Web application
servers, the trailing slash is optional.

Replace host-name and port with the appropriate values for your Web application server.

If Application Registry installation is successful, Application Registry displays a message similar to the
following:

And now... Some Services

AdminService (wsdl)
AdminService
Version (wsdl)
getVersion
urn:TCApplicationRegistry (wsdl)
registerApplication
unregisterApplication
lookupApplicationByGUID
lookupApplicationsByName
lookupAllApplications
registerInstance

Application Registry, Teamcenter 13.0 TSS00002 13.0 2-3

© 2020 Siemens
 2. Installing Application Registry

unregisterInstance
lookupInstanceByGUID
lookupInstancesByName
lookupAllInstances
getApplicationRegistryVersion

2-4 TSS00002 13.0 Application Registry, Teamcenter 13.0

© 2020 Siemens
Siemens Digital Industries Software
Headquarters Europe
Granite Park One Stephenson House
5800 Granite Parkway Sir William Siemens Square
Suite 600 Frimley, Camberley
Plano, TX 75024 Surrey, GU16 8QD
USA +44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas Suites 4301-4302, 43/F
Granite Park One AIA Kowloon Tower, Landmark East
5800 Granite Parkway 100 How Ming Street
Suite 600 Kwun Tong, Kowloon
Plano, TX 75024 Hong Kong
USA +852 2230 3308
+1 314 264 8499

About Siemens Digital Industries Software

Siemens Digital Industries Software is a leading global provider of product life cycle management
(PLM) software and services with 7 million licensed seats and 71,000 customers worldwide.
Headquartered in Plano, Texas, Siemens Digital Industries Software works collaboratively with
companies to deliver open solutions that help them turn more ideas into successful products. For
more information on Siemens Digital Industries Software products and services, visit
www.siemens.com/plm.
This software and related documentation are proprietary and confidential to Siemens.
© 2020 Siemens. A list of relevant Siemens trademarks is available. Other trademarks belong to
their respective owners.