Micro Focus. Enterprise View. Multi Daemon User s Guide. Supported Environments

Transcription

1 Micro Focus Enterprise View Supported Environments

2 Copyright 2008 Micro Focus (IP) Ltd. All rights reserved. Micro Focus (IP) Ltd. has made every effort to ensure that this book is correct and accurate, but reserves the right to make changes without notice at its sole discretion at any time. The software described in this document is supplied under a license and may be used or copied only in accordance with the terms of such license, and in particular any warranty of fitness of Micro Focus software products for any particular purpose is expressly excluded and in no event will Micro Focus be liable for any consequential loss. Animator, COBOL Workbench, EnterpriseLink, Mainframe Express, Micro Focus, Net Express, REQL and Revolve are registered trademarks, and AAI, Analyzer, Application Server, Application to Application Interface, AddPack, AppTrack, AssetMiner, CCI, DataConnect, Dialog System, Enterprise Server, Enterprise Server with MTO, EuroSmart, FixPack, LEVEL II COBOL, License Server, Mainframe Access, Mainframe Manager, Micro Focus COBOL, Micro Focus Studio, Micro Focus Server, Object COBOL, OpenESQL, Personal COBOL, Professional COBOL, Server Express, SmartFind, SmartFind Plus, SmartFix, SourceConnect, SupportLine, Toolbox, VS COBOL, WebSync, and Xilerator are trademarks of Micro Focus (IP) Ltd. IBM and CICS are registered trademarks, and IMS, DB2, DB2/390, DB2 Connect Enterprise Edition, DB2 Connect Personal Edition, COBOL for OS/390, Enterprise Systems Architecture/390, ESA/390, MVS, MVS/ESA, OS/390, S/390, System/390, VSE/ESA and MFS are trademarks, of International Business Machines Corporation. Netscape Enterprise Server is a trademark of Netscape Communications Corporation. Internet Information Server, Windows 95, Windows 98, Windows NT 4.0, Windows ME and Windows 2000 are registered trademarks of Microsoft Corporation. Pentium is a registered trademark of INTEL Corporation. Borland Database Engine and Midas are trademarks of Inprise Corporation. Oracle is a trademark of Oracle Corporation Inc. UNIX is a registered trademark of The Open Group. Solaris, Ultra Sparc and Java are trademarks of Sun Microsystems, Inc. Linux, GCC compiler, GNU CTAGS, GNU DIFF, Samba and KDE/GNOME refer to Open Source tools. This product includes modified versions of software developed by the Apache Software Foundation (as described on the Apache web site). The YGrep Search Engine is Copyright (c) Yves Roumazeilles. All other trademarks are the property of their respective owners. No part of this publication, with the exception of the software product user documentation contained on a CD-ROM, may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or machine-readable form without prior written consent of Micro Focus (IP) Ltd. Contact your Micro Focus

3 representative if you require access to the modified Apache Software Foundation source files. Licensees may duplicate the software product user documentation contained on a CD- ROM, but only to the extent necessary to support the users authorized access to the software under the license agreement. Any reproduction of the documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification. U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software and the Documentation were developed at private expense, that no part is in the public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFAR et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR , as applicable. Contractor is Micro Focus (IP) Ltd, 9420 Key West Avenue, Rockville, Maryland Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.

4 4

5 5 Table of Contents 1. OVERVIEW JOB CREATION WIZARD SPECIAL JOBS END DAEMON JOB SUMMARY UPDATE JOB MULTI DAEMON MENU ORGANIZATION OF JOB FOLDER RESTARTING PROCESS FAILURE SCENARIOS RESTARTED JOBS... 21

6 6

7 7 1. Overview The new multi daemon replaces the old listener/daemon. It consists of two daemons Main and Secondary. The purpose of the Main daemon is to execute the main jobs, which cannot run concurrently: Inventory Job Analysis Job Life Cycle Inventory Deletion Job Summary Update Job Rapid Assessment Source Recognizer The rest of the jobs can run concurrently with other jobs, provided that they are submitted for a different organization view. They can be processed by both daemons, Main and Secondary: Inventory Probe Quality Analysis HTML Export Unsupported Syntax Object Measures History Update Calculate Custom Views Metrics Function Point Analysis Quality Analysis Import Defects (Tickets) Function Point Life Cycle Dashboard HTML Export Tasks Govern HTML Export Export OM View to Portal Export Standard View to Portal Portal Authorization Task/SLA/Cost Export The End Daemon Job is a special job, which stops either daemon. The new Multi Daemon menu allows the daemon to be started in foreground or background mode. It begins by checking whether NLS is provided. If the NLS_ENCODING value is not NONE, i.e. begins with ISO, its value (the current locale encoding) is compared with that of the LANG variable. If the value is the same, the encoding is supported and the daemon will function properly. If it is not the same, the daemon will stop running and an error

8 8 message will appear: Comparison of current locale setting and internal encoding failed. Check error log for details. Make sure the value of the LANG variable in your profile file and the value of the NLS_ENCODING environment property are the same (ISO8859-1) and start the daemon again. Note: In the environment properties (see Work with Environment Properties in Configuration Manager) is a section COMMON where you can find the NLS_ENCODING property. The value of the property can be NONE (no NLS support) or ISO For more information about the LANG variable that should be exported in your profile file, see the Installation Guide.

9 9 2. Job Creation Wizard There are two ways to submit a job by right-clicking the organization view tree in the left-hand pane, or by clicking New in the Work With Jobs form. Either will start the new Job Creation Wizard which will guide you through the process of job submission. If you start the wizard by right-clicking the organization view tree, the job parameters will be automatically populated. Starting the wizard with the New button in Work with Jobs requires you to fill in most of the parameters manually. The second screen of the Wizard allows you to select the type of job you want to submit and to set the date and time after which the job will be executed. The current date and time are taken by default, which means that the job will be executed immediately after submission.

10 10 Job Main Properties

11 11 The third screen lets you set various additional parameters, depending on the job type you have selected: Job Detail Properties for the Inventory Job The next screen will ask you to specify the daemon that will execute the job. The main jobs described in the Overview section above can be executed by the Main daemon only. The other jobs can be scheduled for execution by either daemon. Two more properties can be set: Job priority - range: 1-9 This parameter lets you prioritize the jobs. The job priority determines the order in which the eligible jobs will be scheduled for execution. Hold Job if checked, the submitted job will be put on hold and will not be executed. To release the job, uncheck Hold Job.

12 12 Click Generate to submit the job.

13 13 Now if you open the Work with Jobs function, you will see all submitted jobs:

14 14 In the example given there are two scheduled jobs. If you select a job that has not yet been started, you can change the Priority and Hold parameters. For the non-main jobs, you can also change the daemon that will execute the job.

15 15 3. Special Jobs 3.1. End Daemon Job This new job lets you stop a daemon simply by scheduling it in the Work With Jobs function. In order to stop the daemon immediately after execution of the running job, simply submit the End Job with the higher priority. Next select the daemon you want to stop (Main or Secondary):

16 16 If you have started both daemons, you have to execute this job twice for each of the daemons. This job lets you stop the daemons if they are running in background mode and are not visible in the console Summary Update Job You use the Summary Update Job to force a refresh of the various screens. This job is automatically submitted after one or more main jobs finish and there are no more jobs eligible for execution.

17 17 4. Multi Daemon Menu The new multi daemon has a new menu. It is accessed from the job directory by typing:./startev If you are using more than one schema, you will be asked which schema you would like to work with. Type the number of the schema and press Enter. Otherwise, you will be taken directly to the Choose application to start menu. Select which of the daemons you want to start and in which working mode (foreground or background): Choose application to start: 1. Start Daemon 1 2. Start Daemon 2 3. Start all daemons 4. Start Agent 5. Start Custom Agent 6. Start Portal 7. Shutdown Portal 8. Back >.1 Choose way to start application: 1. Foreground 2. Background 3. Back >.1 Starting daemon 1... You can start both daemons at the same time by selecting option 3 from Choose application to start menu. In this case the daemons will be started in the default background mode. If you choose to start a single daemon, you will be asked in which mode you would like to start it. By default, the daemons work in background mode, waiting for new jobs to be submitted. The daemons will continue working even if you close the console.

18 18 If you select foreground mode, the daemon will write some diagnostic messages to the console. Note: In foreground mode, the daemon is linked to the console and will be killed if you close it! To stop the daemon gracefully, submit an End Daemon job before closing the console. If either daemon is already running for a given schema, trying to start it again will produce no results. This avoids having two instances of a given daemon running at the same time. To verify if the daemons are currently running, type the following command in the console: ps -Af grep -i kby This command will provide you with a list of all the daemons running on different schemas: IG Jan21 pts/9 00:00:00../bin/kbYAIM IG Jan21 pts/9 00:00:00../bin/KbYDaemon 1 GIADEV SH Jan21 pts/6 00:00:00../bin/KbYDaemon 1 SDK520 SH :06 pts/6 00:00:00../bin/KbYDaemon 2 HSD55PN LT :08 pts/8 00:00:00 grep -i kby In the example above, you can see three daemons running on three different schemas: The schema HSD55PN has the Main and Secondary daemons running, and the schemas HSD55PN and SDK520 have only the Main daemon running. A running daemon will pick up any jobs that are eligible for execution and execute them. If you want to stop a daemon, you have to submit an End Daemon job from the Work With Jobs form. We do not recommend you stop or kill the daemons in any other way. The Enterprise View menu lets you start the UNIX Agent too. It can be started in foreground or background mode. All remarks written above for the daemons are valid for the Agent, only the way to stop it differs. In foreground mode the Agent can be stopped by pressing Ctrl+C. In background mode the process must be killed the name of the executable is KbYAgent. You can start the UNIX Custom Agent if it is available in the default location enterpriseview/bincustom/directory. It can be started and stopped in the same way as the UNIX Agent. The name of the executable is KbCustAgent. If Enterprise View Portal is installed in the default location enterpriseview/mfev-portalserver/bin/ - it can be started or shut down from the Enterprise View menu. Follow the instructions on the screen to check the output of the executed commands.

19 19 5. Organization of Job Folder There are some changes in the management of the job folder related to the new multi daemon functionality. In the job folder, a new subfolder will be created for each schema used: job/dbalias_<schema name> It will contain all the information the host part needs in order to connect to the database. When a job is executed, the daemon will take the Job ID and create a temporary working subfolder under the Enterprise View folder with the following name: job_<schema_name>_<jobrecid> When the job finishes, the daemon will archive this folder (in a tar.gz file) and copy the archive file to the job/result subfolder. The archive name will be the same as the folder name: job_<schema_name>_<jobrecid>.tar.gz.

20 20

21 21 6. Restarting Process One of the important features of Enterprise View is the restarting process. When a job fails for some reason, it can be restarted by starting the daemon again. The job restarts automatically if it has failed during execution Failure Scenarios There are two main failure scenarios: Controlled Non-controlled In both situations, the next time the daemon is started, the failed job is automatically restarted. The only difference is in the status displayed in the Work with Jobs function: In case of controlled failure, the status will be Failed In case of non-controlled failure, the status will be In Progress Generally, the non-controlled stopping of the daemon is a result of power failure. Some of the potential causes of controlled failure are: Oracle problem Configuration problem (missing mandatory configuration file or parameter ) Internal failure (segmentation fault) 6.2. Restarted Jobs If a failure occurs, the daemon tries to restart the job. If the job fails again, the daemon stops running. Only if a Daily Life Cycle job fails does the daemon stop after the first unsuccessful execution of the job. Most of the jobs are automatically restarted from the beginning. Only a few jobs are automatically restarted from the step or object where the failure occurred. These jobs are: Analysis Daily Life Cycle Life Cycle

22 22 Jobs Restarted from a Step/Object: During normal processing, each job stores the following information in restart configuration files: Job being executed Step being executed Current managed object The restart configuration files are stored in job_<schema_name>_<jobrecid>, and if a failure occurs this folder remains, so it is not archived in the job/result folder. (See the chapter Organization of Job Folder for more details about the Job Folder management.) When the daemon is started again, it recognizes that a job has to be restarted, then automatically locates it in job_<schema_name>_<jobrecid> and starts it again. Each job checks the restart configuration files for a previous failure. Depending on the contents of these files, the job moves to the failed step and starts the processing from the object on which the failure occurred. If the processing fails again on the same object, it automatically continues from the next object without stopping. If the object is a different one, the job stops again. It is restarted from this second object and the processing continues. The restart configuration files are: KbXRestartModule.txt contains information about the module that has failed. A job has several modules: Configuration, Attribute Loader, Relations Loader, etc. KbXRestartPoint.txt contains information about the failure point. A module can contain several logical units. For example, the Relations Loader loads object-toobject relations, as well as attribute-to-attribute relations. KbXRestartObject.txt contains information about the file (object) that caused the failure. You can use these files to find out where exactly a failure occurred and what caused it.