Installing CA Enterprise Log Manager - CA Technologies

More documents

Recommendations

Info

Creating Virtual CA Enterprise Log Manager ServersAdd Virtual Disk Drives13. Specify your Disk Capacity and Location and then click Next. An advancedoptions dialog appears.You can either store this disk with your virtual machine or you can specifyanother location. We recommend a minimum of 500 GB.14. Accept the default values for the Advanced Options and click Next.15. Confirm your settings and click Finish to create the new virtual machine.Use this procedure to add virtual disk drives for event log storage. Use thesesame settings regardless of the role a specific CA Enterprise Log Manager serverplays in your network.To edit the settings1. Right-click your virtual machine in the VMware Infrastructure Client andselect Edit Settings.The Virtual Machine Properties dialog appears.2. Highlight the CD/DVD Drive 1 properties.3. Click the Host Device option button, and select your DVD-ROM drive from thedrop-down list.4. Select the Device Status option, Connect at power on.5. Click Add to launch the Add Hardware Wizard and add a second hard disk.6. Highlight Hard Disk in the device list and click Next. The Select a Disk dialogappears.7. Select the option, Create a new virtual disk, and click Next.8. Specify the size of your new disk and select the option, Specify a datastore toset its location.CA Enterprise Log Manager detects this additional drive during installationand assigns it to data storage. We recommend maximizing the amount ofstorage that you can make available to CA Enterprise Log Manager.Note: The default Block Size setting in VMware ESX Server is 1 MB, whichlimits the maximum disk space that you can create to 256 GB. If you needmore space, up to 512 GB, increase the Block Size setting to 2 MB using thiscommand:Vmkfstools --createfs vmfs3 --blocksize 2M vmhba0:0:0:3Restart the ESX Server for the new setting to take effect. More informationabout this command and other commands is available in the VMware ESXServer documentation.Click Next to display the Specify Advanced Options dialog.238 Implementation Guide
Creating Virtual CA Enterprise Log Manager Servers9. Accept the default values for the Advanced Options and click Next. The Readyto Complete dialog appears.10. Click Finish to store your changes to this virtual machine. This action returnsyou to the VMware Infrastructure Client dialog.Install CA Enterprise Log Manager on the Virtual MachineUse this procedure to install CA Enterprise Log Manager on a virtual machine thatyou created previously.You can configure a virtual or dedicated CA Enterprise Log Manager server afterinstallation to serve in one of several functional roles such as management,collection, or reporting. If you install a CA Enterprise Log Manager managementserver, do not use it to receive event logs or to run queries and reports. Installseparate virtual CA Enterprise Log Manager servers to act as reporting andcollection servers for the best performance.Review the normal installation instructions before installing CA Enterprise LogManager in a virtual environment. The installation worksheet helps you to gatherthe information you need.To install CA Enterprise Log Manager on a virtual machine1. Load your CA Enterprise Log Manager OS Install disk in the physicalDVD-ROM drive, or locate the directory where you copied the installationimage.2. Highlight your virtual machine in the virtual machine inventory list,right-click on it, and select Power On.3. Proceed with the normal CA Enterprise Log Manager installation.4. Configure the installed CA Enterprise Log Manager server for the functionalrole you intend, using the information in the section on installing a CAEnterprise Log Manager server.More informationInstalling a CA Enterprise Log Manager Server (see page 66)Install CA Enterprise Log Manager (see page 71)Creating a Completely Virtual EnvironmentIf you do not yet have a CA Enterprise Log Manager environment implemented,you can create an all-virtual log collection environment. This scenario assumesthat have a sufficient number of physical servers available, each with a group ofat least four processors, to install each of the intended CA Enterprise LogManager servers.Appendix E: CA Enterprise Log Manager and Virtualization 239
Page 1 and 2:
CA Enterprise Log ManagerImplementa
Page 4 and 5:
Contact CAContact Technical Support
Page 7 and 8:
ContentsChapter 1: Introduction 13A
Page 9 and 10:
Import CA Enterprise Log Manager Us
Page 11 and 12:
Access CA Enterprise Log Manager th
Page 13 and 14:
Chapter 1: IntroductionThis section
Page 15:
About This GuideNote: For details o
Page 18 and 19:
Server PlanningServer RolesA CA Ent
Page 20 and 21:
Server Planning■Restore point ser
Page 22 and 23:
Server PlanningThe next simplest ar
Page 24 and 25:
Log Collection PlanningLog Collecti
Page 26 and 27:
Log Collection PlanningAn automated
Page 28 and 29:
Federation PlanningLog Collection G
Page 30 and 31:
Federation Planning3. Decide which
Page 32 and 33:
Federation PlanningTo implement the
Page 34 and 35:
Federation PlanningAn example feder
Page 36 and 37:
User and Access PlanningUser Store
Page 38 and 39:
User and Access PlanningRequired in
Page 40 and 41:
User and Access PlanningThe default
Page 42 and 43:
Subscription Update Planning■Cont
Page 44 and 45:
Subscription Update PlanningPort 80
Page 46 and 47:
Subscription Update PlanningVerify
Page 48 and 49:
Subscription Update PlanningHow Sub
Page 50 and 51:
Subscription Update PlanningThe pro
Page 52 and 53:
Subscription Update PlanningExample
Page 54 and 55:
Agent PlanningAgent PlanningAgents
Page 61:
Agent PlanningFor smaller implement
Page 64 and 65:
Understanding the CA Enterprise Log
Page 66 and 67:
Installing a CA Enterprise Log Mana
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Initial CA Enterprise Log Manager S
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Install the ODBC ClientUsers of thi
Page 84 and 85:
Install the ODBC ClientODBC Data So
Page 86 and 87:
Installing the JDBC ClientTest Serv
Page 88 and 89:
Installing the JDBC ClientInstall t
Page 90 and 91:
Installation TroubleshootingProduct
Page 92 and 93:
Installation TroubleshootingRegiste
Page 94 and 95:
Installation TroubleshootingImport
Page 96 and 97:
Page 98 and 99:
Page 101 and 102:
Chapter 4: Configuring Basic Users
Page 103 and 104:
Configuring the User StoreMore info
Page 105 and 106:
Configure Password PoliciesConfigur
Page 107 and 108:
Create the First AdministratorCreat
Page 109:
Create the First Administrator4. Se
Page 112 and 113:
Edit Global ConfigurationsThe Syste
Page 114 and 115:
Working with Global Filters and Set
Page 116 and 117:
Configuring the Event Log StoreAbou
Page 118 and 119:
Configuring the Event Log StoreAbou
Page 120 and 121:
Configuring the Event Log StoreGene
Page 122 and 123:
Configuring the Event Log StoreSet
Page 124 and 125:
Configuring the Event Log StoreNote
Page 126 and 127:
ODBC Server ConsiderationsTo set ev
Page 128 and 129:
Configuring SubscriptionAction Aler
Page 130 and 131:
Configuring Subscription2. Accept o
Page 132 and 133:
Configuring Subscription11. If your
Page 134 and 135:
Configuring SubscriptionRSS Feed UR
Page 136 and 137:
Configuring SubscriptionMore inform
Page 138 and 139:
Configuring SubscriptionConfigure a
Page 140 and 141:
Using the Agent ExplorerYou base yo
Page 142 and 143:
Configuring the Default AgentTo rev
Page 144 and 145:
Example: Enable Direct Collection U
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
View and Control Agent or Connector
Page 156 and 157:
Hierarchical FederationsHierarchica
Page 158 and 159:
Meshed FederationsIn a ring or star
Page 160 and 161:
Configuring a CA Enterprise Log Man
Page 163 and 164:
Chapter 8: Working with the EventRe
Page 165 and 166:
Appendix A: Considerations for CA A
Page 167 and 168:
Understanding Differences in Archit
Page 169 and 170:
Understanding Differences in Archit
Page 171 and 172:
Configuring CA AdaptersIn addition
Page 173 and 174:
Configuring CA AdaptersConfigure th
Page 175 and 176:
Sending CA Audit Events to CA Enter
Page 177 and 178:
Sending CA Audit Events to CA Enter
Page 179 and 180:
When to Import Events4. Click Edit.
Page 181 and 182:
Importing Data from a SEOSDATA Tabl
Page 183 and 184:
Page 185 and 186:
Page 187 and 188: Integrating with CA Audit r8 SP2Imp
Page 189 and 190: Integrating with CA Audit r8 SP22.
Page 191: Integrating with CA Audit r8 SP2To
Page 194 and 195: How to Modify CA Audit Policies to
Page 204 and 205: How to Configure a CA Access Contro
Page 206 and 207: How to Configure a CA Access Contro
Page 208 and 209: How to Import CA Access Control Eve
Page 219 and 220: Appendix C: CA IT PAM Consideration
Page 221 and 222: Prepare to Implement CA IT PAM Auth
Page 223 and 224: Copy the Certificate to the CA IT P
Page 225 and 226: Install the Third-Party Components
Page 227: Launch and Log in to the CA IT PAM
Page 230 and 231: About Backing Up the CA EEM ServerA
Page 232 and 233: Back Up a CA Enterprise Log Manager
Page 234 and 235: Replace a CA Enterprise Log Manager
Page 236 and 237: Creating Virtual CA Enterprise Log
Page 250 and 251: agent exploreragent groupagent mana
Page 252 and 253: auto-archiveCA adaptersAuto-archive
Page 254 and 255: CEG fieldscertificatescold database
Page 256 and 257: defrosted database stateA defrosted
Page 258 and 259: event log storageevent log storeeve
Page 260 and 261: global groupglobal resourceglobal u
Page 262 and 263: LMArchive utilityThe LMArchive util
Page 264 and 265: message parsing token (ELM)A messag
Page 267 and 268: emote storage serverA remote storag
Page 269 and 270: servicesSNMPSNMP trap contentsThe C
Page 271 and 272: summarization rulesSummarization ru
Page 273 and 274: IndexAadministration tasksuser stor
Page 275: description • 18in federated repo
show all

Installing CA Enterprise Log Manager - CA Technologies

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?