Author Archive

Remote Installation Go or No Go?

May 27th, 2010

Remote installation go or no goThese days virtualization, high speed internet connections and lots and lots of remote desktop possibilities open a new world of installing or implementing software at a customer.

It’s becoming usual to install software remotely. Giving you the flexibility to work when you want, taking into account time zones,  a great benefit. You can install something from Europe on a server in the US without causing downtime during office hours. Thereby continue your daily tasks when a large install or database update is running. Wow, only benefits!

No, in specific scenarios it also brings a  bunch of disadvantages. What if a account is locked or you miss specific rights to install the software or download/ upgrade to the latest patch? Right,  I think your first thought right now is… Create a checklist, duhhh, pre requisites, requirements etc… but we stay human so a small mistake is made within a split second and computers stay computers… they keep suprising you!

One of those mistakes can cause a delay that, again think of time zones, might take up a whole day. Thereby the urgency of problems you encounter as vendor might be interpreted with a wrong severity when you notify them with an issue. This in contradiction with an onsite visit when you can directly contact the system administrator, DBA or project manager.

The last thing that can make a remote project a real pain is internet connection performance, slow VPNs or disconnecting remote desktop connections.

From a Westbury perspective, I’ve completed several remote implementations of our SMI Suite. Each one of them with a few hiccups as described above. However  it saved me a lot of travel time and jet lag.

Looking at the future I think we will continue remote implementations by learning from the bumps we have to take sometimes.

Finally it is not only our call… many customers want us to be onsite to share knowledge on the job and give them a great week when we blast them away with our SMI Suite.

Share your ideas of remote installation/ implementations, both pros and cons.

Richard

Post to Twitter

Upgrade Business Objects to SP2… a few guidelines

April 14th, 2010

When upgrading Business Objects to the latest service pack, SP2, you need to have a lot of patience. At several customers we’ve performed an upgrade and if you wait long enough it will come around.

At our most recent upgrade the install started fine but while the installer was “Validating Install” we had time enough to get coffee, lunch, coffee, dinner, a good night sleep another coffee and so on..  a total no go.  After struggling with this I started to search the internet for similar stories.

I found some pretty interesting articles like: http://wiki.sdn.sap.com/wiki/display/BOBJ/XI3.1+SP2+Installation+on+Windows and http://neverknewthat.wordpress.com/2009/08/25/xi31sp2-slowinstall/. Both indicating that there is a silent install functionality.

Using the silent install the install was finished before my coffee was finished! However creating the .ini file can still be a pain because the cancel of the installation can take up a few minutes. Below a guideline:

(Assumption that the installer is already unzipped).
1. Create an empty response.ini file
Create a empty response.ini file on a location that’s easy to reach. You can use any name you like, but to keep it easy I used response. For this example I created it on the c:\ root.

2. Start the setup with the -w option
Open a command prompt and navigate to the install directory. Start the setup.exe with the -w option followed by the location of the response file.
E.g.: setup.exe -w c:\response.ini

3. Follow all the steps until the installation validation process starts.
Choose CANCEL here and abort the installation. The response.ini file will be updated with the options you selected during the setup.  (Please post your response.ini file below (without password), this way people reading this blog don’t need to do the -w part of the setup but can use your template)

4. Start the setup with the -r option
Open a command prompt and navigate to the install directory. Start the setup.exe with the -r option followed by the location of the response.ini file.
E.g.: setup.exe -r c:\response.ini

At this point the setup will start on the background, you don’t get any message if the setup is completed or executed successfully. Navigate to the Business Objects home directory (e.g. c:\program files\Business Objects\BusinessObjects Enterprise 12.0) and open the Logging directory. There you find an install file that holds all the install information, one of the last lines will show either a success or failure.

As final check you can go to the Central Management Console and log in. Navigate to the Servers and select the CentralManagementServer. Go to Metrics and the product/resource version should show 12.2.*.

Hope it helps.. it sure did for me!

Richard

Post to Twitter

Change the way you look at your planning

October 5th, 2009

Personally I am not a great planner. I forget things, miss appointments or book events on already taken time…. and Planning Viewsthat is even when I am alone, never mind if a whole team is planning changes based on the same resources. So it is important to make sure everybody who’ s involved in planning has a good overview of the free time slots and already planned events.

When we look at the change process we talk over a lot of planning. Planned start and finish times, actual start and finish times and the related work orders also take a spot in the planning process.  Thereby you need to bear in mind that your organization maybe has some freezes or there is a specific National Day, like ‘Koniggchiginnedag’ (1.46).

If your company has a CAB meeting every day, the Change Manager needs to provide a clear overview of the upcoming changes and the impact of then on the organization. All of the points above have one thing in common, if you have a good overview of the events it will make your live a lot easier, it will reduce the planning mistakes and eventually save costs.

So, let’s dive into the options:

  1. Send an email every day with a list of changes that are planned in the upcoming few days
  2. Teach a pigeon to fly between several floors or buildings and strap a printout of the changes to his tiny legs
  3. Use a web based solution that gives, the people you grant access, everyone access to a clear overview of the upcoming changes

The first one is frequently used but requires a lot of “hand” work , has the risks of making simple mistakes with potentially big consequences.

650The second one is an option but has at least one big flaw… what if there is a new building, new employee or the location is changes… You need to retrain the pigeon.

And last but not least, or let’s call it the best… a web based solution that provide a lot of users to see all the changes in a pretty, easy to read, interface. When you take the web based solutions and there is a new employee, a new floor or building you simply change the access rights or maybe change the location of the web based application. So instead of training a pigeon to fly a new route change the DNS and the new location is ready to see the changes.

Thereby is the internet always faster than a pidgin… well.. almost always. In South-Africa we advise you to use the pigeon (http://news.bbc.co.uk/2/hi/8248056.stm).

So, I came to the simple conclusion, use a good looking, intuitive web based Calendar. Just like the Westbury ITSM Calendar. With this solution you can import the data from you Service Management application. Combine it with other sources that contain your Freezes (Holidays, National Days or planned maintenance), or add events yourself. Take advantage of the read only functionality that ensures you that there is  no need for extra licensing or your application because it has its own user administration. And finally create several calendars so you can easily “filter” through your changes by showing, for example, only the High Impact ones

I will not start a marketing talk now over our calendar, I already did that, I just wanted to point out the need of a good, unified way of sharing your planning. Sad but true, I will create a similar calendar for myself to compensate my poorly planning skills. So, think it over, take a look at our Change Calendar (http://westbury-it.com/solutions/change-calendar) and fall in love with it :-) !!

Till next time,

Richard

Post to Twitter

How to…

August 27th, 2009

“How to…” is quite a generic title for a post so no doubt you will fill in the blanks yourself. And think of something nice… only for me to disappoint you, because the “How to…”  I’m focusing on is… “How to build a good report”.

The first thing you need to keep in mind is that building a report is not that hard… and actually the definition of a report is the hardest part.  So to create a report – instead of just starting to build – you first need to think about a few important steps.

  1. Determine what information you need and who needs it
  2. Start building the report with selecting the data
  3. Manipulate the data (add calculations or other parameters)
  4. Create a final layout and broadcast it to your audience

The most important one of these is the first one, because based on the answer the following can be assessed. To determine which information you need you must think at several sub questions like:

  • What is the exact goal of the report, is it a simple overview,  detailed overview with calculations, or an in-depth view of performance per, let’s say, assignment group;
  • Number of Incidents per Assignment Group, Category and Priority
  • Who needs the information (management, a customer or is it for someone with in depth knowledge);
  • Management
  • How do they expect to receive the report (report with refresh possibility, PDF, Excel or HTML)
  • Report
  • How often should the report be broadcast (once, every day, weekly)
  • Every Monday morning at 8:00 am

Based on those answers you can start determining the source for you data, the answer on question 2. When you are using SMI Suite, and yeah you should,  the data will be available through several complete universes. Right now I’m taking the Incident process as an example so we need to select the Incident universe to get the data.

Once you’ve selected the objects you want to report on, that’s it… Business Objects will provide you with a default report with a tabular overview of the selected data.

tabularview

Then the last part kicks in, time to create some calculations like averages, sums, counts or percentages, and maybe create some variables that represent data in a more “jip en janneke taal” [Ed: this Dutch idiom translates to "in layman's terms", but it's cute so I didn't want to edit it out entirely]. I will add an percentage of the total number per category and priority shown per Assignment group.

Finally create the final layout and it can look like this. Because it is for the management I have decided to give exceptional high percentages a red color and “in the danger” percentages an orange color. In this case they can see at a glance the status and the possible issues.

fixed-view

Finally you can set up a scheduler, part of Business Objects, and publish the report in the desired format.

If you don’t think a report over and start building without thinking you will see that a lot of work is lost in adjusting everything.  So keep this list to guide you through the process or if you have a better guide please share!

In the next blog I will CHANGE the subject! You’re a real Sherlock if you know the subject, so surprise me!

Richard

Post to Twitter

Software development illustrated

July 15th, 2009

I’ve been working in the software development sector for 5 years now and the following cartoon is a real life example of how software development is performed.  The last year I work more and more in the Business Intelligence sector and I believe that the cartoon is also applicable on report building.

SoftwareDevelopment

To get the valuable information from your data is a real profession and needs to be performed from a specific angle. Do not take your own “way of working”  to build a report but look at the basis!  Ask yourself three questions:

  1. Who needs the information?
  2. What information is needed?
  3. Is this information available?

Once you have the answers you can start building your report.  Of course, the answers can be quite extended or not easy to answer but these are the fundamentals to create a valuable report.

In a future blog I will talk through a real life example of building a valuable report!

Personally I love cartoons like the one above,  so if you have comics about software development or related… don’t hesitate to share with us!

Richard


078.23.33.648VERBURG, A.C.J.

Post to Twitter