Archive for October, 2011

What are the ITSM 7.x Object Prefixes

Sunday, October 23rd, 2011

ITSM 7.x Object Prefixes:

  • AP: Approval Server
  • APR: Approval Server
  • APW: Approval Server
  • ASE: Assignment Engine
  • AST: Asset Management
  • BMC.AM: BMC Asset Management Namespace
  • BMC.CORE.CONFIG: CMDB Configuration
  • BMC.CORE: CMDB Classes
  • BSM: Not part of ITSM 7.0.¬† Part of the CMDB Atrium CMDB Console deployable application
  • CAI: Command Automation Interface
  • CBK: Charge Back
  • CFB: Change Management Flashboards
  • CFG: Configuration
  • CHG: Change Management
  • CMDB: Configuration Management Database
  • CMS: Configuration Management System
  • COM: Company
  • CTM: Contact Management
  • FB: Flashboards (base AR)
  • FIN: Financial
  • HPD: Help Desk (Incident Management)
  • KMS: Knowledge Management System
  • LIC: License
  • NTE: Notification Engine
  • OBJSTR: CMDB, Object Store
  • PBM: Problem
  • PCT: Product Catalog
  • PDL: Product Dictionary Library
  • RAC: Application Administration Console
  • RE: Reconciliation Engine
  • RMG: Time Segments (Foundation system)
  • RQC: Requester Console
  • RRC: Reporting
  • SHR: Shared
  • SIT: Site
  • SLM: Service Level Management
  • SRM: Service Request Management
  • SYS: System
  • TMS: Task Management System
  • VIS: Process Visualizer (Foundation system)

 

 

History of BMC Remedy Action Request System

Sunday, October 23rd, 2011

Remedy Corp. The Company was incorporated on November 20, 1990 in Delaware Headquarters Mountain View, California, USA. Key people: Larry Garlick – Founder & CEO, Dave Mahler – VP Marketing, and Doug Mueller – Chief Architect Version 1.0.

Action Request System 1.1 — Approx. Nov 1992

Action Request System 2.0 — 1993

Action Request System 2.1 — 1994

Action Request System 3.0 — 1996

Action Request System 3.1 — May 1997

Action Request System 3.2 — Sep 1998

Action Request System 3.2.1 — 1998

Action Request System 4.0 — Jan 1999 Improved installation process and user interface. ¬†Improvements to Fields, Objects and Workflow, and added various other features to the Remedy Administrator.

Action Request System 4.0.1 — Sep 1999

Action Request System 4.0.2 — Jun 1999

Action Request System 4.0.3 — Nov 1999

Action Request System 4.5 — May 26, 2000

  • Improved installation process
  • Enhanced performance and stability of the Remedy User
  • Added functionality to the Remedy Administrator
  • Enhanced logging functionality – records the appropriate logging (API, filter, or SQL) to the status list, and returns the log via each API call until you request a stop. You can specify getting the log directly or having the log written to a specific file.
  • Provides hooks for building interfaces to allow it to authenticate against external directories.
  • Groups together interrelated objects specific to an application on a packing list. ¬†Modifies or deletes these objects through an editor in Remedy Administrator.
  • Gives server logs maximum sizes and can be configured to be circular logs.
  • Associates properties like version tags, version information, and labels.
  • Has no constraints on the number of server threads; customers can use as many as their database and system resources can support.
  • Extends the business time functionality by adding the Application-Bus-Time-Subtract command.

Action Request System 4.5.1 Maintenance — Jun 30, 2000

Action Request System 4.5.2 Maintenance — Feb 14, 2000

Action Request System 5.0 with Web and Windows clients — Dec 10, 2001

Action Request System 5.0.1 — Mar 15, 2002

Action Request System 5.1 — Sep 11, 2002

Action Request System 5.1.2 Maintenance — Oct 17, 2003

Action Request System 6.0 — Feb 6, 2004

Action Request System 6.03 — Jan 2005

Action Request System 7.0 — May 9, 2006

Action Request System 7.0.01 — Oct 6, 2006

Action Request System 7.1.00 — Aug 31, 2007

Action Request System 7.5.00 — Jan 16, 2009

Action Request System 7.6.03 — Fall 2010

Action Request System 7.6.04 — December 2010

Set AIE 7.6.04 up on its own RPC Port

Tuesday, October 18th, 2011

To set AIE onto its own RPC Port, you will need to add in a new RPC port number to the ARSystem, update the aie.cfg file, and restart the ARServer and AIE services so that the changes can take effect. By putting AIE onto its own port number, this helps to prevent the rest of the system from experiencing performance issues when your AIE jobs are running.

The steps to complete this task are as follows (the following steps are under Linux/Unix):

  1. Open the AR System Administration Console and navigate to Server Information.
  2. Change to the Ports and Queues tab.
  3. In the table, locate an empty line and enter in an RPC Prog Number, Min Threads, and Max Threads values.
  4. Apply the changes.
  5. From the server, stop AIE and the ARServer.
  6. Navigate to where the aie.cfg file is located and open it up in a text editor. If you used the default install, this should be located at:
    • /opt/bmc/AtriumCore/aie/service/conf/aie.cfg
  7. Part way down you should see a section for “PrivateRPCPort:”. On this line, add in the RPC port you defined above.
  8. Save your changes.
  9. Restart your ARServer. You had to do the stop/start in order for the new port numbers to take effect.
  10. Restart you AIE instance. It will start up using the new details.