Archive for May, 2011

Gathering Requirements for an Application Map

The Goal:
To provide a realistic and accurate representation of the application or business service.

What’s Needed:
High level architecture diagrams of the application to be discovered and mapped
– Needs to include all application components (DB, App Servers, Load Balancers, etc).
Application Details
– Ports used
– Application details (App name, DB names, etc.)
– IP ranges of servers & devices
Access to application SME
– Needs to have detailed understanding of application environment
– Needs to understand application component configurations
Credentials for application components
– We will provide a list of whats required based upon application architecture

Application SME Involvements:
The Time Requirement:
– Should be limited to 4-8 hours total per application
– Will be Q&A type involvement
– Time will be broken up into several shorter sessions
Other Requirements
– Help troubleshoot discovery issues with non-standard configurations
– Help gather credentials
– Identify any internal processes we need to follow
The Goal:
– Validate that the maps being created are accurate representations of the application
– Ensure that we have included all relevant components and tiers
– Ensure discovery process is sustainable going forward.

Configuring PowerShell Agent for UCMDB

To Configure PowerShell:
1) Enable PowerShell remoting.
– Launch PowerShell v2.0 as an administrator.
– Run the enable-PSRemoting cmdlet:
— Starts the WinRM service and sets the statup type to Automatic
— Enables a firewall exception for WS-Management communications
— Creates a listender to accept requests on any IP address

2) To trust all hosts, run the following from the command line:

Set-Item WSMan:\localhost\Client\TrustedHosts *

To Trust only restricted IP addresses, specific the addresses in place of the asterisk (*).

3) Restart WinRM by running the following from the command line:

Restart-Service winrm

Reset the default UCMDB 9.x JMX Password

If you are not entirely familiar with the functions of the UCMDB JMX console, you can use the following simple steps to change the default (and very unsecure) JMX “sysadmin” default password.

1) Access the JMX console:
http://<your application hostname or ip>:<port>/jmx-console/

2) Under UCMDB, locate and select “UCMDB:service=Security Services”

3) Under Operations, locate and select “changeSystemUserPassword”

4) In the proceeding table, fill out the fields as follows and select “Invoke”.

userName:  sysadmin
password: yournewpassword

5) If you wish to test your new password, clear your browser cache/cookies and reload the JMX console, or simply use a different browser (if you have one).


Return top