[TUXEDO] TMMETADATA *SERVERS

TMMETADATA(5)

 

Name

TMMETADATA - Tuxedo service metadata repository server

Synopsis

TMMETADATA SRVGRP="identifier" SRVID="number"

CLOPT="[-A] [servopts options] -- -f repository_file [-r] [-o filename]

Description

TMMETADATA is a Tuxedo system server that processes requests to retrieve and/or update Tuxedo service metadata repository information.

TMMETADATA provides and supports just one service, .TMMETAREPOS, which uses FML32 input and output buffers similar to those used by the Tuxedo MIB. The TMMETADATA FML32 buffer format is described in MIB(5).

Note:

Metadata information retrieval and updating are handled through a service independent from .TMIB in order to avoid burdening the BBL with metadata request processing overhead since the metadata repository is stored separately from the Tuxedo configuration.

The CLOPT option is a string of command link options that is passed to TMMETADATA when it is booted. The following run-time parameters are recognized by TMMETADATA:

 

-f

This option is mandatory and specifies the location of the metadata repository_file.

 

 

-r

If this option is specified, TMMETADATA only allows retrieve information requests from the metadata repository and disallows any metadata repository update requests. The TMMETADATA default permissions setting is read/write.

 

 

-o

Used for Service Contract Discovery. This option specifies the name of the text file to store recognized pattern. When set, patterns are output to this file instead of to the metadata repository. If TMMETDATA is "read only" using "-r", "-o"must be specified if service contract discovery is required. The file format is compliant with metadata repository input file specifications.

For more information, see Configuring Service Contract Discovery in the Oracle SALT Administration Guide.

 

Limitation

Because TMMETADATA provides only one service, .TMMETAREPOS, multiple TMMETADATA servers running on a particular Tuxedo domain must all be configured for the same permission access. That is, they either should all be read only or they should all be read and write.

Each TMMETADATA server must be configured to access the same metadata repository file or an exact copy of the file to provide consistent request results. Therefore, it is strongly recommended that a stable version of the metadata repository is made available for multiple TMMETADATA server access.

 

Interoperability

TMMETADATA must run on a Tuxedo 9.0 release or later.

 

Tuxedo Jolt Repository

If invoked on a Tuxedo Jolt repository file with the -r option, TMMETADATA can read and return records from that file just as it would for a Tuxedo metadata repository file.

If invoked on a Tuxedo Jolt repository file without the -r option, TMMETADATA fails upon server initialization.

 

Example(s)

Listing 6 Single TMMETADATA Server Configuration

*SERVERS
	TMMETADATA SRVGRP=ADMIN1 SRVID=137 RESTART=Y MAXGEN=5
		GRACE=3600 CLOPT="-A -- -f /usr/tuxadmin/METAREPOS"

Listing 7 Multiple TMMETADATA Server Configuration

*SERVERS
TMMETADATA    SVRGRP=ADMIN1 SVRID=101 RESTART=N
CLOPT="-A -- -f /usr/tuxadmin/metarepos1 -r"
TMMETADATA    SVRGRP=ADMIN1 SVRID=102 RESTART=Y MAXGEN=5
GRACE=3600 CLOPT="-A -- -f /usr/tuxadmin/metarepos1 -r"
TMMETADATA    SVRGRP=ADMIN1 SVRID=103 RESTART=Y MAXGEN=5
GRACE=3600 CLOPT="-A -- -f /usr/tuxadmin/metarepos1 -r"

 

 

https://docs.oracle.com/cd/E35855_01/tuxedo/docs12c/rf5/rf5.html#3133627

Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference