Archive for March, 2010

ARSocial, a Java Plugin for Twitter – BMC Remedy AR System integration

March 29th, 2010

Credits – Sebastiaan de Mann

Twitter – @sebas

ARSocial is a Twitter – BMC Remedy AR System integration that allows you to publish tweets, replies, direct messages as well as have an overview of your friends timeline, a search option and mentions. Because it is based on the AR System it can be fully integrated into the ITSM Suite as well as custom built applications. The plugin and application are open source and released on with a BSD style license. Please be aware this is only a ‘preview’ release and is not quite ready for production use.

Here are some pics of the wonderful app

Detailed information in author’s words:

Architecture

The ARSocial application consists of several parts:

  • ARDBC Plugin for listing tweets, mentions, direct messages and search

The ARDBC Plugin treats the twitter feeds (friends, direct messages, search) as a database source. Because of the speed of the Twitter API we can do fast searches and show all relevant information, mentions and direct messages. It also allows for the creation of tweets, replies and direct messages.

  • ARSocial Console form, for an overview of all twitter related items

This will be the main form for the users of the application. It is meant to keep an overview of all tweets that are sent by friends, mentions of the twitter account and searches (for example tweets that mention your company name)

  • Vendor and Regular forms

Vendor Forms are built from the ARDBC Data sources to show the information in the Tables of the console. Regular forms are used to store sent Tweets and Direct Messages.

All items and source code can be found in the download package.

What you will need

  • BMC Remedy AR System 7.5 server
  • Midter 7.5
  • Remedy Developer know-how
  • Plugin Server know-how
  • Java know-how
  • A twitter account
  • An AR Server that you can break without getting people angry at you (really, I’m serious)

You can download a ‘developer preview’ of the application here: arsocialpreview

at the moment there’s only standard twitter client functionality implemented, and there is no direct integration into the ITSM Suite, however because of the architecture including Vendor Forms it is quite easy to integrate into any itsm and custom built applications. Over the next few weeks I will expand the plugin and the application.

For now please be aware there are several open issues, including ordering of tweets in the table fields and missing functionality in the stand-alone application.

Please provide feedback on BMCDN communities, contact Sebas on twitter or send an email.

Minimum DB2 database Transaction logsize for Installing BMC Remedy

March 28th, 2010
Minimum DB2 database transaction log size
When you upgrade an AR System 7.5.00 server that uses an IBM® DB2 Universal
Database® in an environment supporting BMC Remedy IT Service Management
(ITSM) applications, BMC recommends a minimum database transaction log file
size of 1.3 gigabytes (GB).
Before starting the upgrade, adjust the following DB2 Universal Database
configuration parameters to ensure that logfilesize >= 1.3 GB:
???? LOGFILSIZ
???? LOGPRIMARY
???? LOGSECOND
For example:
WARNING
This example is from a test environment and represents a minimum transaction
log file size. To determine the log file requirements for your environment, consult
your database administrator before beginning the upgrade.
For more information about determining your transaction log file size, go to
http://publib.boulder.ibm.com/tividd/td/tec/SC32-1233-00/en_US/
HTML/ecoimst65.htm.

Minimum DB2 database transaction log size

When you upgrade an AR System 7.5.00 server that uses an IBM® DB2 Universal Database® in an environment supporting BMC Remedy IT Service Management (ITSM) applications, BMC recommends a minimum database transaction log file size of 1.3 gigabytes (GB).

Before starting the upgrade, adjust the following DB2 Universal Database

configuration parameters to ensure that logfilesize >= 1.3 GB:

???? LOGFILSIZ

???? LOGPRIMARY

???? LOGSECOND

For example:

Log file size (4KB) (LOGFILSIZ) = 20000

Number of primary log files (LOGPRIMARY) = 8

Number of secondary log files (LOGSECOND) = 10

WARNING

This example is from a test environment and represents a minimum transaction log file size. To determine the log file requirements for your environment, consult your database administrator before beginning the upgrade.

For more information about determining your transaction log file size, go to

http://publib.boulder.ibm.com/tividd/td/tec/SC32-1233-00/en_US/

HTML/ecoimst65.htm.

%d bloggers like this: