For related programming information, see the CORBA Programming Reference.
•
•
• Before executing a command, you must ensure the bin directory is in your defined path, as follows:For c shell (csh): set path = ($TUXDIR/bin $path)For Bourne (sh) or Korn (ksh): PATH=$TUXDIR/bin:$PATH
export PATHUse the idl2ir command to create an Interface Repository and load interface definitions into it. If no repository file exists, the command creates it. If the repository file does exists, the command loads the specified interface definitions into it. The format of the command is as follows:For a detailed description of this command, see the File Formats, Data Descriptions, MIBs, and System Processes Reference in the Oracle Tuxedo online documentation.Use the ir2idl command to display the content of an Interface Repository. You can also extract the OMG IDL statements of one or more interfaces to a file. The format of the command is as follows:For a detailed description of this command, see the File Formats, Data Descriptions, MIBs, and System Processes Reference in the Oracle Tuxedo online documentation.Use the irdel command to delete the specified object from the Interface Repository. Only interfaces not referenced from another interface can be deleted. By default, the repository file is repository.ifr. The format of the command is as follows:For each application that uses one or more Interface Repositories, you must start one or more of the Interface Repository servers provided by Tuxedo CORBA. The server name is TMIFRSVR.You can add one or more entries for TMIFRSVR to the SERVERS section of the application’s UBBCONFIG file.By default, the TMIFRSVR server uses the Interface Repository file repository.ifr in the first pathname specified in the APPDIR environment variable. You can override this default setting by specifying the -f filename option on the command-line options (CLOPT) parameter.The following example shows a SERVERS section from a sample UBBCONFIG file. Instead of using the default file repository.ifr in the default directory ($APPDIR) where the application resides, the example specifies an alternate file and location, /usr/repoman/myrepo.ifr.For more information, see the section Required Order in Which to Boot CORBA C++ Servers on page 3‑61 in Chapter 3,Creating the Configuration FileNotice that the TMIFRSVR Interface Repository server is the fifth server started.For a description of the TMIFRSVR -f filename parameter, refer to the File Formats, Data Descriptions, MIBs, and System Processes Reference. In addition to the CLOPT -f filename parameter, the TMIFRSVR parameter can contain other parameters (those that are not specific to the Oracle Tuxedo system) in the SERVERS section of an application’s UBBCONFIG configuration file.See the section How to Create the SERVERS Section of the Configuration File on page 3‑54 in Chapter 3, Creating the Configuration File for details about parameters such as SRVGRP, SRVID, RESTART, MAXGEN, and GRACE.