easyCMDB Forums - All Forums

How do I purge all these mysql-bin.0000* files?

Fri, 18 May 2012 02:43:23 +0000

The MySQL database is configured to write transaction logs to enable point-in-time recovery. These log files can build up over time to consume quite a lot of disk space. /easyCMDB/amp/mysql/data/mysql-bin.0000*

easyCMDB does not purge these files from disk by default.

It is recommended that you include the mysql-bin* files in your filesystem backups to external storage so that you can recover them if required. In the event that you need to restore the database to a point in time, you will need a full backup file plus a number of mysql-bin files. See our Recovery Guide for more information.

Once the mysql-bin files have been copied/backed-up elsewhere, they can be safely deleted. The best way to do this is to switch on the Delete Master Logs option in the Database Backup Job in the Job Manager.

We recommend cloning the Database Backup Job (Tools & Utils > Job Manager), and configuring the copy to run once per week with the Delete Master Logs option switched on. This will retain one week's worth of logs files on your system, with the assumption that filesystem backups are also in place to archive the history.

New encoder required for PHP 5.3.10

Wed, 16 May 2012 04:25:50 +0000

On Windows 2008 platforms an updated encoder file is required to support PHP 5.3.10. If you intend to apply the PHP 5.3.10 upgrade you will first need to download and apply the encoder file.

The updated encoder file will run fine on PHP versions < 5.3.10, so it can be applied well before upgrading PHP.

Here are the steps:

1. Download the ixed-win.5.3.10.zip file from our server under the “3rd party software” section (via your /admin URL > Check for Updates) into a temporary folder
2. Stop your easyCMDB IIS web server
3. Replace the file \easycmdb\amp\php\ext\ixed.5.3.win with the one in the contained zip file. Make a copy of the file in the unlikely event it does not work.
4. Restart easyCMDB IIS web server

NOTE: you may have to perform an iisreset before the O/S will release hold on the ixed.5.3.win file.

How do I add a drop-down list of Services to my change form?

Fri, 11 May 2012 03:40:28 +0000

Follow these steps:

1. Open Tools & Utils > Form Editor
2. Select CI Type = Changes and the desired Subtype / Attribute Scheme combination.
3. Create the custom field "service_collection_id" with Data Type "Link to CI"
4. Modify the field so the display option is LIST
5. Open Tools & Utils > Database Schema Menu > CI Field Definition
6. Select CI Type = Changes
7. Click on Modify next to the "service_collection_id" and set the Subtype to "Service" and Relationship to "Affects"

You should now be able to select a Service when creating your Change Request and see it linked under the Collections tab.

Facebook page

Mon, 07 May 2012 04:31:56 +0000

Just started our new Facebook page. Like us please!

http://www.facebook.com/Easycmdb

How can I specify a view to list records whose date falls within the next 30 days?

Wed, 02 May 2012 03:28:06 +0000

Views can be created to include special keywords to query dates.

For example, to query CI records whose "Expiry Date" falls within the next 30 days, define a view with criteria:

"Expiry Date" > "today" and "Expiry Date" < "today + 30 days"

As well as "today" you can use "yesterday" and "tomorrow" or "now"
"now" includes the time whereas "today" does not.

In addition to "days" you can use "hours", "months", "years"

e.g. a condition of "yesterday - 3 months" is also valid.

How do I dynamically link CIs to a Collection?

Thu, 26 Apr 2012 03:55:12 +0000

1. Create the Collection CI

2. From the relationship screen for the Collection, click on the desired tab for the CI Type you wish to link to.

3. The tab must be empty (no existing links) before you can dynamically link CIs to the Collection. So unlink any that currently exist.

4. Click on the 'New Link' button and enter the desired search criteria for the CIs you wish to link to the Collection. Note that ALL matching CIs will be linked that match the criteria.

5. At the bottom of the results window, click on "Save As Dynamic List"

Every time the members of the Collection are determined the query you supplied will be run, so the addition or removal of members will be dynamic according to what is in the database.

How do I configure the Job Runner against multiple databases?

Fri, 06 Apr 2012 04:29:28 +0000

For Windows:

1. Edit your jobrunner.ini file

Jobrunner.ini can be found under \easyCMDB\scripts

A new process block must be add for each database you wish to run job runner against. Each process block must be named as [ProcessN] where N starts at zero and increments by 1 for each database.

If your easyCMDB install root is not under C:\ drive change all directory references to your current install root for each Process.

Change to the database you wish to run the jobrunner against for each process.

2. Install job runner service

From the command line:

cd \easyCMDB\scripts
jobrunner.exe –i
sc config jobRunner depend= MySQL
sc start jobRunner

All syntax must be entered exactly as shown including the space in between the = and MySQL.

The new service will start immediately and will automatically start following system reboot.

Example jobrunner.ini file:

[Settings]
ServiceName=jobRunner
CheckProcessSeconds = 600
[Process0]
CommandLine = E:\easyCMDB\amp\php\php.exe -c E:\easyCMDB\amp\php E:\easyCMDB\wwwroot\job_runner.php test1 E:\easyCMDB\amp\php
WorkingDir= E:\
UserInterface = No
Restart = No
[Process1]
CommandLine = E:\easyCMDB\amp\php\php.exe -c E:\easyCMDB\amp\php E:\easyCMDB\wwwroot\job_runner.php test2 E:\easyCMDB\amp\php
WorkingDir= E:\
UserInterface = No
Restart = No

For Linux & Solaris:

Here is a script which can be used to start & stop the job runner for every easyCMDB database on the server:

EASYCMDB_ROOT=/opt
PHP=$EASYCMDB_ROOT/easyCMDB/amp/php

start() {
for db in `ls -d $EASYCMDB_ROOT/easyCMDB/amp/mysql/data/easycmdb_*`
do
db=`basename $db | sed 's/easycmdb_//g'`
echo -n "$db: "
$PHP/bin/php -c $PHP/etc/php.ini $EASYCMDB_ROOT/easyCMDB/wwwroot/job_runner.php $db $PHP start &
echo
done
}

stop() {
for db in `ls -d $EASYCMDB_ROOT/easyCMDB/amp/mysql/data/easycmdb_*`
do
db=`basename $db | sed 's/easycmdb_//g'`
echo -n "$db: "
$PHP/bin/php -c $PHP/etc/php.ini $EASYCMDB_ROOT/easyCMDB/wwwroot/job_runner.php $db $PHP stop
echo
done
}

status() {
for db in `ls -d $EASYCMDB_ROOT/easyCMDB/amp/mysql/data/easycmdb_*`
do
db=`basename $db | sed 's/easycmdb_//g'`
echo -n "$db: "
$PHP/bin/php -c $PHP/etc/php.ini $EASYCMDB_ROOT/easyCMDB/wwwroot/job_runner.php $db $PHP status
echo
done
}

case "$1" in

start)
start
;;
stop)
stop
;;
status)
status
;;
*)
echo "$0: {start|stop|status}"

esac

Update 20120330 available

Mon, 02 Apr 2012 19:32:16 +0000

* Time can now be recorded when entering notes against incidents and changes. The time entered will be included in the 'Total Hours' calculation when the incident/change is closed.

* Incident and Change notes may now be marked 'For Attention' of a single recipient, which displays the note on their 'Notes' Dashboard section.

* NEW Data Import Wizard Job enables automated import of CSV data. This uses the same options as the Tools & Utils > Data Import Wizard

* Database backup function now automatically zips output file. Database restore function supports zip files.

Who is permitted to rename CIs?

Thu, 29 Mar 2012 20:01:25 +0000

Configuration Items can be renamed if you are one of:

1. Access Level = Administrator
2. Access Level = Read+Write+Create Any
3. The Owner of the CI

Otherwise the 'name' field is set to read-only.

How do I create a recurring change?

Fri, 23 Mar 2012 01:14:47 +0000

A Change Request can be triggered automatically by using the 'Template Runner' Job under the Job Manager.

Here are the steps:

1. Create a Change Template which details the work, assignment etc, along with any Tasks and linkages you may require.

2. Clone the 'Template Runner' Job under Tools & Utils > Job Manager, and configure it to execute the Change Template you created above.

3. Set the Job to run as often as required and enable it.

Done!

How to relate incidents with company rather than user?

Thu, 22 Mar 2012 21:57:19 +0000

The default configuration is that incident records will be associated with an end user (a.k.a 'affected user')

If you wish to instead link an incident record with a particular company / client name then we recommend the following approach:

1. Create a new Collection Type under Lookup Value Maintenance called 'Customer'

2. Import your customer list via CSV using the Data Import Wizard into the Collections > Customer type.

3. (Optional) Customize the form used to manage Customer entries using the Tools & Utils > Form Editor

4. Hide / remove the affected user and related contact fields from your incidents forms using the Form Editor

5. Create a new custom incident field called 'customer_collection_id' whose data type is 'CI Link', field title "Affected Customer" and position it on the form

6. Set the display option of this field to "LIST"

7. Under Schema Field Definition, edit the properties of the customer_collection_id field and set it to Relationship = Affected, Subtype = Customer

When creating incidents you should now be presented with a list of Customers to choose from.

This approach is intended where a single easyCMDB company contains data for multiple clients as opposed to a multi-company approach.

PHP 5.3.10 support on Linux now available

Sun, 18 Mar 2012 20:18:28 +0000

PHP 5.3.10 upgrade now available for customers running easyCMDB on Linux platforms.

What are the differences between Editions?

Fri, 16 Mar 2012 02:04:54 +0000

easyCMDB is available in 3 Editions:

1. Small Business
2. Enterprise Lite
3. Enterprise

The Small Business Edition (SBE) is only available to companies with < 50 employees and supports up to 250 CIs. SBE excludes multi-company capability and integration options. A maximum of 2 databases may be created.

The Enteprise Lite Edition (ELE) supports up to 1,000 CIs and excludes multi-company capability. A maximum of 2 databases may be created.

The Enterprise Edition (EE) is available for all CI tiers including unlimited options for individual CI groups. Full functionality is included with the ability to create up to 10 companies and system integration extensions.

Additional company & CI licenses can be purchased at any time.

All Editions come complete with Configuration, Change, Incident, Problem, Service, SLA and Document management modules.

Where can I see the reason entered when an incident is placed on hold?

Thu, 08 Mar 2012 01:30:19 +0000

The text entered when an incident is placed on hold is stored in the field 'status_reason'.

This text can be viewed in the following ways:

- Automatically written to a note entry by enabling the 'Note' option next to the 'status' field in the Form Editor.

- Included in an email notification using the __STATUS_REASON__ tag

- Included on a form by making the 'status_reason' field visible

- Included in form/report output by including the 'status_reason' field in a View

Other status values such as 'Cancelled' and custom on hold statuses also require input of a reason.

How does placing an incident On Hold affect the SLA?

Tue, 28 Feb 2012 00:56:09 +0000

An incident is placed on hold when you set the status to "On Hold" or any other status which you have set as an on hold status under System Settings > Incidents tab.

When the incident is taken off hold (i.e. changed to a non-on hold status) the Target Resolution Date is recalculated by adding the time the incident was on hold for.

e.g. If an incident was placed On Hold on Monday 10am and the Target Resolution Date was Monday 1pm, then later the incident was taken off hold on Wednesday at 10am, the new Target Resolution Date would be Wednesday 1pm.

If the incident was then resolved on Wednesday 2pm, this would be deemed by the system to be outside the agreed SLA. (i.e. SLA Met = N)

Single Sign-On Enhancements

Mon, 20 Feb 2012 03:43:43 +0000

easyCMDB now supports SAML-based SSO, and also integrates with Crowd from Atlassian. (http://www.atlassian.com)

SQL Server support available

Mon, 20 Feb 2012 03:40:45 +0000

easyCMDB is now shipped with Microsoft SQL Server support, and existing customers can elect to transfer from MySQL to SQL Server if desired.

There is no intent to discontinue MySQL and support will be available for the foreseeable future.

Update 20120119 available

Mon, 20 Feb 2012 03:37:30 +0000

Update: 20120119
==============

-- Enhancements

* Data Import Wizard Rehearse mode now includes relationship linking

* Replace mode in the Data Import Wizard will now replace relationship links with those imported that match the same CI Type and relatonship

* When searching People CIs the User ID field is now included as a default search field

* Users now redirected to announcement window when logging in if there are unread announcements

* New 'Template Runner' Job enables change or incident templates to be scheduled to run at regular intervals

* New Access Control Group report when selecting the "Report" button in ACG relationship screen and under Access Roles > ACG tab

* New User Permissions report under Access Roles > Users tab that outputs user CI permissions

* Added default Access Role to Sync LDAP Job

* Added new 'Incident Category Report' under Incident/Problem/Service Management Category

* NEW 'Auto Folders' options for Changes and Incidents in System Settings. Switching on this option will automatically create document folders beneath the default folder for each incident/change if one or more documents are attached.

* Task Notes can now be listed & edited beneath the Tasks tab for incidents and changes by toggling the Summary/Notes option.

* Now possible to edit the relationship description between Collections without having to relink

* Extended 'get_ci' web service:
- Now returns multiple records
- Added 'match_attributes' input parameter to contain name, op and value of additional/alternative matching fields
- Added 'return_attributes' input parameter to specify list of attributes to return (default is all)
- Added 'custom_properties' flag, to determine whether to return custom properties
- Will impact current usage of this method
- See Integration Guide for further details

* Multi entry Embedded Forms: Added "Max Entries" parameter to Form Field Definition. Setting > 1 will present Embedded Form as a Table with rows and columns so multiple entries can be input.

* Stat Reports can now be generated for other CI Types other than incidents and changes. Added example Type, Status and Monthly stat reports for each CI Type under Asset/Configuration Management reports.

* Added new 'Custom Job' to Job Manager, which can be used to schedule the execution of a custom PHP class. Please refer to the Job Manager documentation for details.

* Added Start Date, End Date, Due Date, Customer Name, Program Name, and Project Type as built-in fields for Collection CI. These fields have been moved from the Project Properties to make them more accessible.

* New right-click menu available on Dashboard over Incident and Change numbers, which allows quick note display/entry, incident resolution and closure.

* Database admin changes to support MS SQL

* Added ability to include "Linked CIs" when defining CI views

* Added support for SAML SSO authentication under System Settings > Security

* Added support for Atlassian Crowd® SSO authentication under System Settings > Security

* Can now add individual users to Access Roles via Users tab

* Added Racks and Documents to Event Calendar CI options

* Update to PHP API functions

* Dashboard Right-click menu can now be disabled via Access Roles > Functions

* Bulk Update now supports Change Request reference and multi-version creation

* Data Import Wizard now supports Templates when importing incident or change records

Closing Change Request in one go

Fri, 20 Jan 2012 05:52:19 +0000

Hello,

Is there any way to close the change request in one go? In easyCMDB there are many old requests are there which is not yet closed.

Appreciate a quick help.

Where can I find the MySQL log file?

Sun, 08 Jan 2012 22:34:59 +0000

On Linux & Solaris:

/easyCMDB/amp/mysql/data/.err

On Windows:

\easycmdb\amp\mysql\data\.err

Where is the root directory / folder under which easyCMDB is installed and is the name of the easyCMDB host machine.