Monitoring and Maintaining Your BRM System.This chapter provides information and guidelines to help you manage the day to day operation of your Oracle Communications Billing and Revenue Management BRM system.About Monitoring BRMYou use the following tools to monitor BRM components In addition, you can use component specific diagnostic tools such as Table 2 1 provides an overview of the system monitoring tools Table 2 1 BRM System Monitoring Tools.Monitoring Tool. Functions.Componentpinctl utility.Stop and start components.Get diagnostic data.Clear log files. All system components.See Components Monitored and Controlled by the pinctl Utility.Monitor key performance indicators.Oracle databases.Diagnostic Data Handler.Get application diagnostic data.Pipeline Manager.Log files. Get status and error messages.All system components.Qo. S statistics.Get Qo. S statistics.CMHTTP and SNMP system monitoring.Get instrumentation data from probes.Set configuration values.Pipeline Manager.Real time pipeline.See BRM OMF Instrumented Objects.Components Monitored and Controlled by the pinctl Utility.You can use the pinctl utility to monitor the following BRM components Connection Manager.CM Master Process CMMPConnection Manager Proxy cmproxyData Managers Oracle Data Manager.Email Data Manager.EAI Data Manager.View and Download SYMANTEC WISESCRIPT PACKAGE EDITOR 8.REFERENCE FOR WISE PACKAGE STUDIO V1.WISESCRIPT PACKAGE EDITOR 8.Disable New Instance Microsoft Script Editor Debug' title='Disable New Instance Microsoft Script Editor Debug' />Paymentech Data Manager.Account Synchronization Data Manager.Invoice Data Manager.EAI Java Server. Invoice Formatter.Paymentech Answer Simulator.Pipeline Manager, including Real time pipeline.Batch pipeline. Batch Controller.System Manager. Node Manager.Using the pinctl Utility to Monitor BRMYou can perform the following monitoring tasks by using the pinctl utility You also use the pinctl utility to start, stop, halt, and restart system components.For information about starting and stopping BRM by using the pinctl utility, see Starting and Stopping the BRM System.For more information, see pinctl.Setting Up the pinctl Utility.Install the pinctl utility executable on any system that runs a BRM component.Each instance of the pinctl utility is configured by a pinctl.BRM components running on the system.See Configuring the pinctl Utility.Important. AIX only To start more than one pipeline process in the same machine, you must assign a different IFWEVENTHANDLER port for each pipeline process.For example, if you are starting rtp, aaa, and bre in the same AIX machine.IFWEVENTHANDLERPORT envval XXXX1.IFWEVENTHANDLERPORT envval XXXX2.IFWEVENTHANDLERPORT envval XXXX3.To run the pinctl utility, set the PERL5.LIB environment variable to point to the third party applications install directory.To do so, perform one of the following Add the following paths to the PERL5.LIB environment variable for the root account on each managed node BRMHomeThird.Party. AppstoolsPerl.Lib. BRMHomebin. Before you deploy the callpinctl script in BRMSPIinstalldirectorybin, add the following paths to the PERL5.LIB variable in the script BRMHomeThird.Party. AppstoolsPerl.Lib. BRMHomebin. Getting the Status of a Component by Using the pinctl Utility.You can get the status of a component at any time.To get the current status of a component by using the pinctl utility Go to the BRMHomebin directory.Run the following command pinctl status componentwhere component is the component for which you want the status.For a list of valid component values, see pinctl.For example. pinctl status dmoracle.You can use the collectdata parameter to get diagnostic data when checking the status of a component pinctl status collectdata component.See Getting Diagnostic Data for a Component by Using the pinctl Utility.Clearing Log Files for a Component by Using the pinctl Utility.To clear a components log file by using the pinctl utility Go to the BRMHomebin directory.Run the following command pinctl clear componentwhere component is the component whose log file you want to clear.For a list of valid component values, see pinctl.For example. pinctl clear dmoracle.You can also clear log files when you start a component by using the cstart command.See Starting a Component and Clearing the Log File.Getting Diagnostic Data for a Component by Using the pinctl Utility.You can use the pinctl utility to get diagnostic data about a component at the following times Before startup by using the start command.The data is collected before the component is started.Before shutdown by using the stop command.The data is collected after the component is stopped.While it is running when you use the status command.When you run the restart and cstart commands.Note. If you collect data during the stop all or status all commands, data is collected for all components before the command is carried out.For example, if you stop all components, data is collected about all the components, and then they are stopped.The diagnostic data is written to a file in the components log directory.The file name is component.When a new file is created, BRM renames the existing file to component.YYYYMMDDhhmmss for example, dmoracle.To get diagnostic data about a component by using the pinctl utility Go to the BRMHomebin directory.Run the following command pinctl action collectdata component where action specifies the action to be executed for example, start, during which you want to collect diagnostic data.For a list of valid component values, see pinctl.For example. pinctl start collectdata dmoracle.Diagnostic Data Collected by the pinctl Utility.Date and time the data was collected.Extended information from the system for example, system, node, release, and kernel ID.Environment variables for the current terminal session.System limits for the current terminal session.Memory information for example, available memory.Storage device information for example, available disk space.Patch level on the system.Kernel parameters.Network status showing all sockets, routing table entries, and interfaces.Network status summary.Inter process communication facilities status.NFS statistics. Duration of time that the system has been up.All active components.All active users.Configuring the pinctl Utility.You can configure the pinctl utility by editing the pinctl.See the following topics The pinctl.BRMHomebin. Customizing the Components Included in allYou can customize the components that are included in the pinctlall component.Open the pinctl. BRMHomebin.Find the following lines in the file.List of services to be part of all Optional.Mention the service names separated by a space.For example, allmyall.After all, enter each component that you want to start with the all command allcomponent.X is the component you want to add.For a list of valid component values, see pinctl.Important. Make sure the components are in the order in which you want them started.The order is reversed when the components are stopped.Save and close the file.Customizing pinctl.Starting and Stopping Optional Components.The default pinctl.BRM system components only.To configure pinctl.Synchronization Queue DM dmaq, you must Open the pinctl.BRMHomebin. Add the following line to the components list startsequenceservicename aliasname java app pipeline dependentservice.This determines the order in which components are started or stopped.For example cm1cmcm2cmwhere cm1 and cm2 are cm services.Java based. app indicates that the component executable is located in the BRMHomeapps directory. Non Stop Dj Dandia Songs Free Download there. This indicates that dependentservice must start before servicename is started.For example, to add dmaq to the components list.Add the following line to the startup configuration section of the file startcomponentcpidproc searchpattern pidvarnamecport portnumber testnap directoryname.It must be unique if not, the last parsed definition is used.If you enter nothing which is recommended, the default is PID, which matches CMPID in PINLOGcmcm.The directory is relative to BRMHomesys.For example, to enter a startup configuration for dmaq.DMAQPORT. Save and close the file.Creating a Custom all Parameter List.You can create aliases for custom lists of components that are controlled by the pinctl utility all component.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |