LMS Collection Tool Measurement

Instructions
ORACLE LMS WHITE PAPER

|

MARCH 2016

This document is intended to describe the technical steps to be performed
by the Customer in order to properly collect data for Oracle Product
license metrics usage tracking.
This document and all information contained herein are STRICTLY
CONFIDENTIAL and are for use by Oracle and Customers for the
purposes of the Oracle products license usage measurement. They are
not to be divulged in whole or in part whether electronically or as hard
copy to any third party without the express permission of Oracle or
authorized signatory.

..................... 6 2....................Contents Introduction ............................................................ Technical Requirements .....................................................................................2.................................................................................................................................................................1........1........................................................................................................ 16 4...........Running the Tool on Linux / UNIX ........................................................................ 15 Multiplexing architecture ............................................................. CPU Scripts ........................................ Measurement Overview ........................................................... Base Script ............................... 6 2.........................................................2...............3..................................... 11 On Windows Systems........................ 6 2....................................................................................................................... Running the Scripts ...........................LMSCPU Script...................................................................................................................................................................................... 12 Examples .......... 9 Examples .................... Collected Data Description ... 5 1........................3............................................ 8 On Linux / UNIX Systems ..................................................................................... 5 1.................................................................... Troubleshooting Initial Phase ...................................................... 5 1................................................. Conventions ...... Credentials Requirements ...................................................................................................................... 15 Troubleshooting Executing Phase ............................................................................................................................................................................................................................................................. 16 2 | LMS Collection Tool Measurement Instructions ........................ 13 Partitioned Servers .......................................................................Running the Tool on Windows ........................................................ 15 3................................................................................................................................................................. 8 2............................................... Data Collection ..................................................................................5....................................4............................................................................ 4 1.................................................................................................................................................................................................................................................................... 3 1..................................................................... Data Collection Scripts ........................................ Files Overview ................................. 3 1...........................................................................

 o For UNIX/Linux deployments – Provides information on running the tool on UNIX/Linux environments o For Windows deployments – Provides information on running the tool on Windows environments Troubleshooting initial phase – Provides troubleshooting information on how to start the script 3 | LMS Collection Tool Measurement Instructions . The Oracle LMS Collection Tool (referred to herein as the “LMS Collection Tool” or “tool”) is a collection of scripts that are executed from within the operating system of the server(s) where the Oracle Software is installed. This tool detects and collects measurement data for the Oracle Software running on Windows servers and most versions of UNIX and Linux.Provides information on running the tool on UNIX/Linux and Windows environments. “Oracle Software” designates all the products listed above.Introduction The LMS Collection Tool Measurement Instructions document is intended for system and middleware administrators as well as anyone else who wants to perform LMS measurement process.  Technical Requirements – Provides an overview on the pre-requisite information (credentials. etc…) required to run the tool  Credentials Requirements – Provides a summary of credentials needed to run the scripts  Running the Scripts . by accessing the scripts outside of the tool. Revisions may only be made with the written approval of appropriate Program Manager. In what follows. environment variable. In addition. 1. They are not to be divulged in whole or in part whether electronically or as hard copy to any third party without the express permission of Oracle or an authorized signatory. machine name. This document is owned by Oracle License Management Services – Global Business Services. and a minimal basic knowledge or experience with Windows or UNIX environments is required. Measurement Overview This document describes the technical steps required to collect license measurement data for the following Oracle products:  Oracle Application Server (OAS) or Internet Application Server (iAS)  Oracle WebLogic Server or BEA WebLogic Server (WLS)  Oracle Service-Oriented Architecture (SOA) Suite  Oracle Tuxedo or BEA Tuxedo This document and all information contained herein are STRICTLY CONFIDENTIAL and are for use by Oracle and Customers for the purposes of Oracle license usage measurement. you thereby agree to the Oracle LMS License Agreement. The document is structured as follows:  Files Overview – Provides information on the files included in the LMS Collection Tool. A basic knowledge of computers. domain names. Note: Running scripts outside of the LMS Collection Tool is not recommended or supported by Oracle LMS.

SOA Acronym for Service-Oriented Architecture. monospace Monospace type indicates commands within a paragraph. text that appears on the screen. Conventions The following text conventions are used in this document: Table 1. code in examples. or text that you enter. LMS Abbreviation for License Management Services CPU Central Processing Unit LMSCPU Acronym for LMS CPU query/script. emphasis. OAS Acronym for Oracle Application Server. or placeholder variables for which you supply particular values. Text conventions convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action. FMW Acronym for Fusion Middleware. Troubleshooting executing phase – Provides troubleshooting information on how to run the script successfully  Collected Data – Provides a description of the data collected by the tool 1. This will refer to Oracle ServiceOriented Architecture Suite throughout this document. WLS Acronym for WebLogic Server. URLs. or terms defined in text or the glossary italic Italic type indicates book titles. iAS Acronym for Internet Application Server. This will refer to Oracle WebLogic Server or BEA WebLogic Server throughout this document. 4 | LMS Collection Tool Measurement Instructions .1.

cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/resources/util/WLST/WLSNUP/getWLS _NUP.sh 5 | LMS Collection Tool Measurement Instructions . Refer to the Running the Scripts section for more information on the instructions for running the scripts. 1.3. TABLE 2.2. BASE SCRIPT OPERATING SYSTEM LOCATION Windows Oracle_LMS_Collection_Tool\LMSCollection\bin\LMSCollection. When you run the Base Script you will get the Oracle LMS License Agreement displayed and collect Oracle software configuration files. COLLECTION SCRIPTS OPERATING SYSTEM DESCRIPTION / CONFIGURATION FILES LOCATION OAS AND IAS: THESE PLUGIN SCRIPTS COLLECT OAS INSTALLATION INFORMATION AT THE OPERATING SYSTEM LEVEL OF THE SERVER WHERE IAS OR OAS IS DEPLOYED Windows Oracle_LMS_Collection_Tool\LMSCollection\resources\util\OAS\run_opmnctl_status. Data Collection Scripts These scripts are automatically called by the Base Script and collect individual product information.cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/bin/LMSCollection.sh 1.sh WLS NUP: THESE SCRIPTS COLLECT NUP CONFIGURATION INFORMATION FROM THE RUNNING INSTANCES OF WEBLOGIC SERVER FOR BOTH WEBLOGIC AND ORACLE SOA SUITE PRODUCTS. cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/resources/OAS/run_opmnctl_status. Running the tool to start a particular product measurement may automatically trigger supporting plug-in scripts to run as well. Dependencies amongst each product measurement are preset in the tool’s configuration files.1. Windows Oracle_LMS_Collection_Tool\LMSCollection\resources\util\WLST\WLSNUP\getWLS _NUP. TABLE 3. Base Script The Base Script is the main/driver script that needs to be run. Files Overview The Oracle_LMS_Collection_Tool.4.zip archive contains the scripts listed in the sections below.

2. Data Collection This chapter describes the technical steps required to be executed by the operating system and middleware admin in order to collect LMS Collection Tool measurement data.x. 6 | LMS Collection Tool Measurement Instructions .1-10. o WebLogic Standard Edition. o WebLogic versions 10. WebLogic Suite 11g and 12c. o WebLogic versions 5. Products measured by the Oracle LMS Collection tool include:  All BEA WebLogic Server Editions and versions. Windows Oracle_LMS_Collection_Tool\LMSCollection\resources\util\tuxedo\countclients.cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/resources/util/tuxedo/countclients. the operating system-specific commands will return the hardware information. CPU Scripts These scripts collect information about the machine’s processor where the Oracle software is installed. CPU SCRIPTS OVERVIEW OPERATING SYSTEM FILES LOCATION Windows Oracle_LMS_Collection_Tool\LMSCollection\resources\util\LMSCPU\lms_cpuq. TABLE 4. Depending on the operating system deployed. Technical Requirements Identification of the following operating system credentials by the respective administrator is required in order to run the Oracle LMS Collection Tool.sh TUXEDO: THESE SCRIPTS COLLECT TUXEDO CONFIGURATION INFORMATION FROM THE RUNNING INSTANCES THE TUXEDO PRODUCT. WebLogic Platform.  All Oracle WebLogic Server Editions and versions.sh 2. If you require any assistance with the information presented in this chapter.1.0 o WebLogic Express.3-12. WebLogic Advantage.sh 1.WLS BASIC: THESE SCRIPTS COLLECT WLS BASIC CONFIGURATION INFORMATION FROM THE RUNNING INSTANCES OF WEBLOGIC SERVER FOR BOTH WEBLOGIC AND ORACLE SOA SUITE PRODUCTS.5. WebLogic Premium.cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/resources/util/LMSCPU/lms_cpuq. please contact your LMS representative.cmd Linux / UNIX Oracle_LMS_Collection_Tool/LMSCollection/resources/util/WLST/WLSBasic/wlsbasic-measurement. WebLogic Enterprise Edition. Windows Oracle_LMS_Collection_Tool\LMSCollection\resources\util\WLST\WLSBasic\wlsbasic-measurement.

4-10 o Tuxedo Add-On products  Jolt  TSAM  WTC  SALT  Tuxedo Adapters  Message Q Oracle Tuxedo o Tuxedo 11g and 12c o Tuxedo Add-On products  Jolt  TSAM  WTC  SALT  Tuxedo Adapters  Message Q Oracle SOA Suite o Versions 10g. For example 7 | LMS Collection Tool Measurement Instructions . WL_HOME – This environment variable must be set in the shell that is running the LMSCollection script. set in LMSCollection\resources\util\WLST\wlstInput. set in LMSCollection\resources\util\WLST\wlstInput.txt file. WebLogic_DomainAdminID– Administrative ID for the WebLogic Domain. TECHNICAL REQUIREMENTS FOR THE DATA COLLECTION SCRIPTS PRODUCT REQUIREMENTS OAS and iAS The OAS and iAS data collection process does not have specific technical requirements. set in LMSCollection\resources\util\WLST\wlstInput.3 or greater. the WebLogic Server being measured must be version 10. Target_Machine_Name_or_IP– Name of machine to connect to via WLST.txt file. WebLogic_DomainHostURL_or_IP:Port – URL of the Domain administrator’s host and port.txt file you would write the above information on a comma separated line. set in LMSCollection\resources\util\WLST\wlstInput. set in LMSCollection\resources\util\WLST\wlstInput. 11g. and 12c o Components of SOA Suite  Oracle Service Bus  Oracle BPEL Oracle Application Server o Version 10g o All editions TABLE 5. In the wlstInput. WL_HOME is the directory where WebLogic is installed. For processor based WebLogic or SOA measurement. WebLogic_DomainAdminIDPassword– Password of the Admin User of the WebLogic Domain.txt file. WLS and SOA The following application server’s connection details must be identified by the WebLogic Server administrator if the instance is running WebLogic Basic or licensed under the Named User Plus (NUP) metric.txt file.txt file. WebLogic_DomainName– Name of the WebLogic domain to connect to. You can set this location in the LMSCollection\resources\util\WLST\wlstInput.txt file.    BEA Tuxedo o Tuxedo versions 6. In order to measure NUP. WebLogic Home and domain configuration information is not needed.

or OAS administrator username and password. or OAS Windows administrator username and password.WebLogic_DomainHostURL_or_IP:7001. Tuxedo. Running the LMS Collection Tool requires the acceptance of the Oracle LMS License Agreement (included in the script). Technical operating system requirements Operating System credentials Windows NT / Windows Administrator username and password. NOTE: Root username is recommended but another account can be used given that it has Root’s privileges.0. 8 | LMS Collection Tool Measurement Instructions . NOTE: Administrator username is recommended but another account can be used given that it is part of the Administrators group.0.3.txt file upon completion and replace it with a template file.Target_Machine_Name_or_IP.127. 2. TUXCONFIG – Environment variable pointing to the Tuxedo configuration file. Credentials Requirements The following operating system credentials must be identified by the operating system administrator in order to run the Discovery and CPU scripts: Table 6.WebLogic_DomainAdminIDPassword 127. 2. By default the LMS Collection tool will delete the wlstInput.2. Tuxedo The following Tuxedo environment variables must be identified and set. Running the Scripts This section describes how to run the Oracle LMS Collection Tool for the products listed in the Measurement Overview section of the document.1:7001. Tuxedo.weblogic1 NOTE: After execution off the LMS Collection Tool it is recommended to remove the information above as a standard security measure. WebLogic. base_domain.WebLo gic_DomainAdminID.WebLogic_DomainName.1. TUXDIR – This environment variable must be set in the shell that is running the LMSCollection script. TUXDIR is the directory where Tuxedo is installed.weblogic. Linux / UNIX / AIX Root username and password. WebLogic.0.0.

5. A quoted string of directory names separated by a comma is required when more than one directory is to be searched. which can be found in LMSCollection\resources\util\license_agreement. $unzip Oracle_LMS_Collection_Tool. we provide instructions on running the tool on Linux/UNIX or Windows environments for each product. The default is the root directory -fsall true | false When specified. 9 | LMS Collection Tool Measurement Instructions . Customers can also choose to run the tool to collect data for multiple (or all) products at once on a given machine. run the LMS Collection Tool to collect data for all the Oracle Software products listed in the Measurement Overview. indicates that you have read and accepted the Oracle LMS License agreement. Refer to Table 7 for specific examples.zip file and extract the files. $ cd bin $ . Go to the bin directory and type ‘LMSCollection. $ chmod –R +x * 6. Details on this option are provided in the sections below./LMSCollection. if you log on as another user the search may not pick up all of the necessary Oracle Software Files. Note: the syntax of all available command line options is as follows [-d search_dir] [-fsall true|false] [-o dir_name] [-follow true|false] [-debug true|false] [-m all|ip|user] [-L Y|N] [-p product] [-fastsearch] TABLE 7. Go to the Oracle_LMS_Collection_Tool directory. 2. Default is true. Go to the directory where you placed the Oracle_LMS_Collection_Tool. Open a Terminal window. all file systems (including remote ones) are searched.txt In what follows. Log into the target system as root.zip file to the target system. 3. 4.sh’ with the proper options to run.zip. Copy the Oracle_LMS_Collection_Tool. LINUX AND UNIX OPTIONS OPTION DESCRIPTION -d search_dir Specifies the directories to be searched for Oracle Software installations. $ cd Oracle_LMS_Collection_Tool/LMSCollection Note: It is recommended to change permissions to execute for all files prior to usage.sh <OPTIONS> Refer to Table 6 below for instructions on the proper options that you need to include. $ mkdir /tmp/LMS_Review 7. Create the output directory where the output files will be stored.Note: Running LMS Collection Tool with the –L Y option. otherwise only the local file system is searched. If you are unsure of the products installed on a given server. On Linux / UNIX Systems 1.

Return the output file ‘LMSCollection-<MACHINE_NAME>.Z if bzip2 or compress is found on your UNIX system) file that contains Oracle Software related files will be created.* 9. The file will be named LMSCollection-<MACHINE_NAME>. Valid options are one or more of the following: LMSCPU. -m all|ip|user Option to turn on masking of sensitive information for WebLogic license and configuration files.bz2 or .tar. Refer to the README. WLS.-o dir_name Option to output the file to the directory specified by dir_name. Default is off.txt for details.tar. WLSNUP. so this must be set to false for the script to work with those systems.txt for more details. Default is true. -p product Option to pass in a list of Oracle products to look for. Perl needs to be in the system path for this to run. environment variables and command line options. -follow true | false Follow symbolic links during file search.tar or . -debug true | false Option to turn on debugging information. Note: The fast search option of the tool is intended to gather information from the system with minimal file searching. -L Y | N Option to agree to license agreement without having it displayed. 10. Tuxedo. Length of Scan. registry. the default is the local directory. 10 | LMS Collection Tool Measurement Instructions .tar(. WLSBasic.bz2 (or . to your LMS representative per the instructions that were provided to you. and log files on the target machine. Default is false. 8. After the tool has finished running the data collection process. SOA and Tuxedo only.tar’ (.bz2). run the LMS Collection Tool to collect data for all the Oracle Software products listed in the Measurement Overview by using the –p all option. Some older versions of AIX do not allow the find command to follow symbolic links.tar. an output directory and a . To verify that the Oracle LMS Collection Tool is running. If not specified.Z). The Oracle LMS Collection Tool searches for several possible configuration.tar. you can use the following UNIX commands: $ ps -ef | grep find $ tail -a /<output_dir>/FMWfiles. Default is off. FormsReports.z or . so the License Agreement will be printed on the screen. Applicable to WebLogic. Refer to the README. SOA. all If you are uncertain of the products installed on a given server. -fastsearch Option to have the tool search for default Oracle environments from well known file locations. OAS.

txt file is required to be valued correctly in order for the WebLogic NUP or WebLogic Basic script to run./LMSCollection./LMSCollection. The wlstInput. Example Commands: WebLogic and WLBasic: -p WLS. LINUX AND UNIX OPTIONS EXAMPLES PRODUCT OPTIONS OAS $ . run the tool by adding the appropriate options and value the input file wlstInput.sh -d / -p Tuxedo -o /tmp/LMS_Review -p product collects the Tuxedo product files -o dir_name in this case the output directory will be the LMS_Review folder For customers who need data masking. run the tool with the following options: $ ./LMSCollection./LMSCollection. Example Commands: SOA. TABLE 8. they can run the tool with the following options: $ . WLSNUP Tuxedo $ .WLSBasic.sh -d / -p SOA -o /tmp/LMS_Review -p product collects the SOA product files -o dir_name in this case the output directory will be the LMS_Review folder For customers who need data masking.sh -d / -p WLS -o /tmp/LMS_Review -p product collects the WLS product files -o dir_name in this case the output directory will be the LMS_Review folder For customers who need data masking.txt./LMSCollection. The wlstInput./LMSCollection./LMSCollection.sh -d / -p OAS -o /tmp/LMS_Review -p product collects the OAS product files -o dir_name in this case the output directory will be the LMS_Review folder FormsReports $ .sh -d / -p Tuxedo -o /tmp/LMS_Review -m all 11 | LMS Collection Tool Measurement Instructions .txt file is required to be valued correctly in order for the WebLogic NUP or WebLogic Basic script to run. run the tool by adding the appropriate options and value the input file wlstInput.sh -d / -p SOA -o /tmp/LMS_Review -m all For customers who are using WebLogic Basic or own SOA Suite licenses under the Named User Plus metrics. WLBasic and WLS NUP: -p SOA.Running the Tool on Linux / UNIX Table 8 below provides examples on the options that could be passed as parameters to step 7 above.sh -d / -p WLS -o /tmp/LMS_Review -m all For customers who are running WebLogic Basic or own WebLogic Named User Plus licenses.sh -d / -p FormsReports -o /tmp/LMS_Review -p product collects the FormsReports product files -o dir_name in this case the output directory will be the LMS_Review folder WLS $ ./LMSCollection.Examples . and WLS NUP: -p WLS. run the tool with the following options: $ .txt.WLSBasic WebLogic.WLSNUP SOA $ .

Log into the target Windows system as Administrator. Create the output directory where the output files will be stored. WINDOWS OPTIONS OPTION DESCRIPTION -d search_dir Specifies the folders to be searched for Oracle software installations. > cd Oracle_LMS_Collection_Tool\LMSCollection\bin 6. Tuxedo.sh -d / -p all -o /tmp/LMS_Review -p all collects all product files -d search_dir searches all file directories starting from / -o dir_name in this case the output directory will be the LMS_Review folder On Windows Systems 1. 4.cmd’ with the proper options to run. 3. and OAS product files -d search_dir in this case the /opt/software AND /home/software paths will be searched -o dir_name in this case the output directory will be the LMS_Review folder -L Y denotes that the LMS License Agreement was read and accepted All products $ . Copy the Oracle_LMS_Collection_Tool.sh -p WLS. -d search_dir [-p product] [-o dir_name] [-debug true|false] [-m all|ip|user] [-L Y|y|N|n][-fastsearch] TABLE 9. if you log on as another user the search may not pick up all of the necessary Oracle Software Files. A string of directory names separated by a comma is required when more than one directory is to be 12 | LMS Collection Tool Measurement Instructions .Tuxedo.OAS -d "/opt/software.Multiple Products $ . >mkdir C:\LMS_Review 7. SOA. Go to the Oracle_LMS_Collection_Tool bin folder. Refer to Table 9 for specific examples. Open a command prompt window.SOA. Unzip the file using to the same directory.zip file to the target system. 2.cmd <OPTIONS> Refer to Table 8 below for instructions on the proper options that you need to include./LMSCollection. /home/software" -o /tmp/LMS_Review -L y -p product Collects WLS. >LMSCollection. Type ‘LMSCollection. Note: the syntax of all available command line options is as follows. Go to Windows ‘Start’ > ‘Run’ menu and type ‘cmd’ 5./LMSCollection.

Refer to the README. Examples . Default is false. -m all|ip|user Option to turn on masking of sensitive information. -L Y|y|N|n Option to agree to the license agreement without having it displayed.e. all If you are unsure of the products installed on a given server. Note: The fast search option of the tool is intended to gather information from the system with minimal file searching. Return the output file ‘LMSCollection-<MACHINE_NAME>. c:.zip. you can use the Windows Task Manager. Perl needs to be in the system path for this to run. WLS. FormsReports. The Oracle LMS Collection Tool searches for several possible configuration. To verify that Oracle LMS Collection Tool is running.searched. SOA and Tuxedo only. The default is all fixed or local drives. to your LMS representative per the instructions that were provided to you. the License Agreement will be printed on the screen. run the LMS Collection Tool to collect data for all the Oracle Software products listed in the Measurement Overview by using the –p all option. -fastsearch Option to have tool search for default Oracle environments from well known file locations. WLSBasic. Default is off.bz2 or . the default is the %TEMP% directory.tar’ (.zip file that contains Oracle Software related files will be created. an output folder and a . i. 9. -debug true | false Option to turn on debugging information. Refer to the README. The file will be named LMSCollection-<MACHINE_NAME>. 8.d: (not the CDROM or NFS drives). registry and log files on the target machine. 13 | LMS Collection Tool Measurement Instructions . Applicable to WebLogic. SOA.txt for more details. -o dir_name Option to output the collected files to the directory given by <dir_name>. WLSNUP.tar.Running the Tool on Windows The table 10 below provides examples on the options that could be passed as parameters to step 7 above. After the tool has finished running the data collection.tar. Valid options are one or more of the following: LMSCPU.txt for details.Z). 10. Tuxedo. environment variables and command line options. If not specified. Default is off. Length of Scan. -p product Option to pass in a list of Oracle products to look for. OAS.

SOA.d:\ -o C:\LMS_Review -p product collects the Tuxedo product files -d search_dir by searching the c: and d: drives -o dir_name in this case the output directory will be the LMS_Review folder Multiple Products > LMSCollection.OAS -d c:\. For example: WebLogic and WLBasic: -p WLS. Tuxedo.d:\ -o C:\LMS_Review -p product collects the OAS product files -o dir_name in this case the output directory will be the LMS_Review folder FormsReports > LMSCollection.TABLE 10.d:\ -o C:\LMS_Review -p product collects the SOA product files -d search_dir by searching the c: and d: drives -o dir_name in this case the output directory will be the LMS_Review folder For customers who are using WebLogic Basic or own SOA Suite licenses under the Named User Plus metrics.cmd -p WLS.cmd -d / -p FormsReports -o C:\LMS_Review -p product collects the FormsReports product files -o dir_name in this case the output directory will be the LMS_Review folder WLS > LMSCollection.txt.cmd -p Tuxedo -d c:\.WLSBasic WebLogic. The wlstInput.txt file is required to be valued correctly in order for the WebLogic NUP or WebLogic Basic script to run. WINDOWS OPTIONS EXAMPLES PRODUCT OPTIONS OAS > LMSCollection.cmd -p SOA -d c:\. and WLS NUP: -p WLS. WLBasic and WLS NUP: -p SOA.txt.txt file is required to be valued correctly in order for the WebLogic NUP or WebLogic Basic script to run. run the tool by adding the appropriate options and value the input file wlstInput. For example: SOA.Tuxedo.cmd -p OAS -d c:\. The wlstInput.WLSNUP SOA > LMSCollection. and OAS product files -d search_dir by searching the c: and d: drives -o dir_name in this case the output directory will be the LMS_Review folder -L Y denotes that the LMS License Agreement was read and accepted 14 | LMS Collection Tool Measurement Instructions .d:\ -o C:\LMS_Review -p product collects the WLS product files -d search_dir by searching the c: and d: drives -o dir_name in this case the output directory will be the LMS_Review folder For customers who are running WebLogic Basic or own WebLogic Named User Plus licenses. run the tool by adding the appropriate options and value the input file wlstInput.SOA.cmd -p WLS -d c:\.WLSBasic.WLSNUP Tuxedo > LMSCollection.d:\ -o C:\LMS_Review -L y -p product collects the WLS.

At this time the script will use default values for the output directory and search directory. Troubleshooting Initial Phase  Invalid script options. the Oracle LMS Collection Tool needs to be run on the operating system of the underlying server hardware to collect the relevant CPU information (an exception to this would be when an Oracle-approved hard partitioning technique is used). in addition to running the Oracle LMS Collection Tool from within the partition on which the Oracle software is deployed. If screenshots are not provided. o Make sure that the directory you used for the –o output directory option is writable by the user running the script. then screenshots of the embedded hypervisor administration interface are required. o Use comma separated directories for the –d search dir option. o If you are not sure of the options to use. is used. Table 11 below provides an example on running the script to collect the CPU information of the underlying server hardware. such as VMware. the script will not continue.cmd -p LMSCPU -o C:\LMS_Review -p product collects the CPU information -o dir_name in this case the output directory will be the LMS_Review folder Multiplexing architecture If Oracle software is part of an environment in which multiplexing hardware or software is used and individual connections cannot be identified. not two nor tab character. If invalid options are given to the script at startup. LMSCPU OPTIONS PRODUCT OPTIONS LMSCPU > LMSCollection.LMSCPU Script If server partitioning is in use.  Not accepting the license agreement. TABLE 11. then all users and/or devices must be declared at the multiplexing front end. The license agreement must be accepted before continuing on with the script. If an embedded hypervisor. These screenshots must show the underlying base server hardware for each virtual guest.All Products > LMSCollection. o Make sure there is one space after the options. then the hardware specifications are needed along with mappings of each virtual guest to its underlying base server hardware. you can choose not to give any options and have the script prompt you for values. 15 | LMS Collection Tool Measurement Instructions . Please review the startup command line options listed above.cmd –p all -d c:\. the script will not start. 3.d:\ -o C:\LMS_Review -p all collects all product data -d search_dir by searching the c: and d: drives -o dir_name in this case the output directory will be the LMS_Review folder Partitioned Servers . o Use the correct options to the –p Product option. If you don’t accept the prompt or use the –L Y license agreement option.

You can have lines for multiple servers.WebLogic_DomainName.  Running the script with the Tuxedo Product options without setting up your environment.bz2 is the output name extension when running the script on Unix and bzip is used for compression.WebLogic_DomainAdminIDPassword  o 127.txt has not been updated to include the values needed to connect to your WebLogic domain(s). The message shown will be:  The file wlstInput.txt file and are running a search for a product that needs to run the WLST commands for WLNUP and/or WLSBasic.txt are correct and try again.txt is set up correctly.zip o LMSCollection-LinuxMachineB_all.tar.LinuxMachineC_all.tar.WebLogic_DomainAdminID.1. you can value it in the wlstInput. Troubleshooting Executing Phase  Running the script with the WLNUP and/or the WLSBasic Product options without setting up your environment. Please contact your LMS representative if you require further assistance.0.txt file correctly before running the script. Not having the correct permissions to search or write to the output directory. If it is and you still have WLST errors.bz2 16 | LMS Collection Tool Measurement Instructions . For example  Target_Machine_Name_or_IP. After the LMS Collection tool finishes. Please do so at this time in a separate text editor.  <productsrun> is a list of the Oracle Fusion Middleware products searched for during the execution of the script.tar is the output name extension when running the script on Unix and compression is not able to be completed.txt file you would write the information from the Technical Requirements table on a comma separated line. o If you do not update the wlstInput.  . base_domain.weblogic1 In addition to the WebLogic domain variables. the script will pause (if not using the –L option) and request that you update the file. If the error persist contact your LMS representative for further assistance.0.zip is the output name extension when running on Windows.WebLogic_DomainHostURL_or_IP:700 1.3 WLST output errors with the WLNUP and/or the WLSBasic Product options. all results will be placed in a file named <machine_name>_<productsrun>. you will be notified with a message at the end of the entire script run. Make sure that the values in wlstInput.zip (.tar o LMSCollection. In the wlstInput.  . then those errors are acceptable. 4.0. .weblogic. Please make sure that you set up the Tuxedo TUXDIR and TUXCONFIG environment variables correctly when running the script. o If there is an error during the WLST product run. Please make sure that you value the LMSCollection\resources\util\WLST\wlstInput.txt file.1:7001. Make sure that the wlstInput.   WLS_HOME=C:\Oracle\Middleware\wlserver_10. where  <machine_name> is the dns name of the machine that the script is run on.  . if you do not have the WLS_HOME environment variable set. Some examples: o LMSCollection-WindowsMachine_WLS_SOA.txt file.bz2).0. Collected Data Description The scripts collect the following files and information. Depending on the server security setup we may not always be able to connect to the running WebLogic Server.127.tar.  o While the script is paused you can correctly value the wlstInput.

txt <machine_name>lms_cpuq.zip(. OAS SOA results-oas-query<machine_name>.txt Oracle Process Management Notification process names 17 | LMS Collection Tool Measurement Instructions .sh startup.log oraInstall*.TABLE 12.xml cache-config. Whenever you add a new domain.xml Module-.txt *ubb* tuxconfig* dmconfig* tuxwsvr.xml install*. WLS SOA tangosol-coherence.properties Application Server start up scripts and properties.. it is registered in this file. COLLECTED DATA DESCRIPTION PRODUCT FILE DESCRIPTION All Products <machine_name>-info.properties ear-deployer.ini bdmconfig* Tuxedo license configuration and log files.xml domain.xml *jms. <machine_name>_<products run>. WLS SOA startWebLogic.tar.xml config.log These files are created or updated by FMW product installers when a product is installed and includes information such as the date when the FMW product was installed.xml setupinfo.sh startManagedWebLogic.txt This file contains a listing of files collected by the LMS Collection tool. WLS SOA OAS comps. WLS SOA domain-registry.sh startNodeManager.xml ias.bz2) Compressed archive of the contents to be collected. Tuxedo lic.out installActions*.sh startWLS.xml domain.xml ejb-deployer.txt These files contain elements that are used by J2EE Application Servers to configure and deploy FMW applications. LMSCollection-Actions<machine_name>-txt This file contains a listing of the files run and the actions taken by the LMS Collection tool LMSCollection<machine_na me>-.xml Coherence configuration files.xml opmn.log installProfile*.xml *jdbc.xml deployment.txt These files contain the Operating System and machine information. WLS SOA Tuxedo OAS registry.xml server.xml This registry file contains the location of all domains currently registered with this WebLogic Server installation.

CA 94065. Oracle and/or its affiliates. We specifically disclaim any liability with respect to this document. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.oracle. This document may not be reproduced or transmitted in any form or by any means. Octavian Soimu. This document is provided for information purposes only. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International. the AMD logo.com/oracle oracle.650. nor subject to any other warranties or conditions.7200 CONNECT WITH US blogs. including implied warranties and conditions of merchantability or fitness for a particular purpose. electronic or mechanical. Inc. 0615 LMS Collection Tool Measurement Instructions March 2016 Author: Dan Pipitone Contributing Authors: Iulian Zagan.506. without our prior written permission. AMD. World Headquarters Worldwide Inquiries 500 Oracle Parkway Phone: +1. Cornel Panait 18 | LMS Collection Tool Measurement Instructions .Oracle Corporation. All rights reserved.com/oracle twitter. This document is not warranted to be error-free. and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Oracle and Java are registered trademarks of Oracle and/or its affiliates. USA Fax: +1. for any purpose. and no contractual obligations are formed either directly or indirectly by this document.7000 Redwood Shores. whether expressed orally or implied in law.506.com Copyright © 2015. Other names may be trademarks of their respective owners. UNIX is a registered trademark of The Open Group. and the contents hereof are subject to change without notice. Opteron.650.com/oracle facebook.