Managed Elements (Windows, RHEL and Sybase)

I have finally installed a sybase ASE on two different platforms, Windows 2003 and Linux (rhel5). Installation of ASE is pretty much straight forward as long as you were able to use the X-Windows subsystem on the Linux platform. Some note worth writing down are:

1.) On RHEL, you need to set the bashrc profile and rc.local with the proper ASE enviroment variable settings.

2.) On both Windows and RHEL, 'sa' password is initially set to blank password.

- Use the management console provided by ASE on Windows platform to set it.

- Execute the command isql -Usa -P -S to login in. 

- Issue a 

    >sp_password , NULL

    >go

3.) To start the ASE service on RHEL, run the startserver -f RUN_ located on the $ASE_HOME$/install directory

Installation of PATROL Agent

1.) Check the documentation for prerequisites

2.) Create a user for PATROL

3.) On RHEL, install the Agent (Management Element on the Installation Setup) using the PATROL account, (this will create a mini-http server)

4.) Access the Patrol installation using a browser from a Windows platform (managed element must be connected to the network) 

Configuration of PATROL for Windows, UNIX and Sybase

1.) Install a Patrol Classic Console on Windows platform

2.) Install the Patrol KMs (Windows, UNIX and Sybase) on the Console (Select the 'Consoles' checkbox on the Installation Setup)

3.) Check the documentation for the prerequisite configuration for Windows, UNIX and Sybase.

4.) To start Patrol Agent use the command line ./PatrolAgent -p 3181 on the /opt/bmc/Patrol3 directory

5.) Key in the sybase directory (/opt/sybase/) on the Patrol configure ASE KM menu 

6.) Specify the krg file as indicated on the /opt/sybase/ASE-15_0/RHEL5PATROL.krg

Notes: I haven't really concentrated on the installation and configuration on PATROL for UNIX and Sybase, but a lot of the configuration are on the documentation. I have encountered a problem on perform Agent data collection since I didn't installed it. This is something that I need to revisit after everything clears out on the other modules.

Its been a while!!!

Its been a while since I have logged on to this blog site. Ok, just to update things up... I'm gonna use this site as a reference site for all the "passion" and work related that I have been doing for the pass two months. 

Currently I have two major projects at my hand, one is for "passion" and the other one is for the "work" related. I'll call the "work" related... ESM.

ESM has a couple of components, namely:

1.) BPM 2.7 

2.) PNA 7.7

3.) BEM 7.3

4.) SIM 7.3

5.) TDFD 7.5

6.) CMDB 7.5

7.) And finally a reporting engine

Here's my IP Address mappings

1.) 192.168.180.90 - vm2k3beim

2.) 192.168.180.91 - vm2k3portal

3.) 192.168.180.92 - vm2k3patrol

4.) 192.168.180.93 - vmrh5patrol

5.) 192.168.180.94 - vm2k3pna

6.) 192.168.180.95 - vm2k3remedy

Dexterra Concert (4.5) Installation

The tide had just turned 180 degrees. I'm now carrying a product that's once a potential competitor to my previous company. Dexterra Concert 4.5, a platform which its strength lies on the offline processing of the data on the handheld devices, typically windows mobile platform devices and a sync technology which transfer the frontend data to its corporate backends.

Installing this product is a little bit tricky, especially on the web server side. Btw, its also a Microsoft centric solution. Installation must be done in particular order,

• OS - Windows platform (2003 server)
• SQL - MS SQL Server (2005)
• Web Server - IIS (6.x and Higher). The trick comes on the FP Extension and ASP.Net installation
• .NET Framework (2.0)

These are the basic components needed to put up a Dexterra server. For the development of the client side:

• Visual Studio (2005)
• Windows Mobile SmartPhone SDK (5.0)
• Windows Mobile Pocket PC SDK (5.0)
• Microsoft Active Sync (4.2)
• Microsoft Virtual Machine Network Services Driver- network simulation

Dexterra Concert (4.5) components includes:

• Dexterra Server - The engine itself.
• Dexterra Conductor - Exposes the business objects to the devices. (Web based)
• Dexterra Orchestrator - CRUD Interface method for sync (Visual Studio plugins)
• Dexterra Composer - Tools for developing the client application on the device (Visual Studio plugins)

The Purpose

What's the purpose of this blog?

Practically anything under the sun, from technical stuff to guides and walkthroughs. It may also serve as a quick reference on certain topic, knowledge or even experiences that have been encountered before. The very heart of this blog contains a simple message and philosophy; which is... "giving is a visible act of gratitude"

Dedicated to Net.