Saturday, May 26, 2007

Microsoft squares up to Google with $6bn buy

Bill's most expensive ever purchase

Microsoft today opened a new front in its war with Google for online advertising dollars, with a $6bn cash offer for the Seattle-based online advertising group aQuantive.

This is Microsoft's biggest acquisition to date, and boy, does it want the company: the $66.50 per share offer is an 85 per cent premium on aQuantive's closing price of $35.87 yesterday.

aQuantive has about 2,600 staff and owns the interactive agency Avenue A / Razorfish and an ad serving company called Atlas. It also has an online advertising exchange network called Drivepm - which aggregates excess inventory from publishers and resells it to advertisers. Microsoft is to merge its advertising platform with Atlas.

In a conference call with analysts today, Brad Smith, Microsoft's general counsel, said the aQuantive deal was "complementary", and encouraged authorities in and outside the US to scrutinise its offer.

This has been a hectic time for mergers and acquisitions among ad-serving companies. This week WPP, the UK advertising giant, bought 24/7 Real Media for $600m and AOL bought ADTech, the German ad serving company, for $100m or so - at least that's what sources tell the WSJ.

Last month, Microsoft famously lost out in the race to buy ad-serving front-runner Doubleclick. It thought it had a deal in the bag with a $2bn offer, but the Google out-trumped it with an hilarious $3.2bn. Remember, Doubleclick is a company with $250m revenues. Even more hilariously, Microsoft said the Google-Doubleclick combo was anti-competitive. Sour grapes maybe, but industry gossip has it that Microsoft was turned down by Doubleclick, even after offering to match Google's bid.

The acquisition feeding frenzy reflects the current fashion among online publishing giants to own their own display ad serving technology, to own a search advertising platform, to run their own advertising exchange networks - to reach out to smaller publishers, and now to have their own creative and media buying arms. Google is leading the charge - and everyone is playing catch-up. Yahoo!, for example, has as many users as Google - or thereabouts - but is a lot less successful at monetising them. This is why the company is making such great play of Panama, its shiny new contextualised ad search engine, which should, it hopes, give advertisers as good a return as they get from Google. Yahoo! is also in the acquisition game, last month adding distribution heft, through the $680m acquisition of the 80 per cent of Right Media, an excess inventory advertising network, that it did not own already.

Microsoft is growing less quickly than Google, but it is still a helluva lot bigger company and it could - if it wanted, and if regulators let it - cough up the $50bn that Yahoo! would cost to buy. But first things first. The company has a new $6bn baby to play with. And it wants to play with it every which way.

Kevin Johnson, Microsoft's platforms and services chief, said the company wants to have its online ads "reach consumers on every connected device on the planet" The company aims to deliver adverts through websites, video on demand channels, IPTV, computer games, and mediums it already owns, such as MSN, Xbox, Windows, and Office Live, and also third party publishers and applications such as Facebook and Activision game titles

Differences between Weblogic and WebSphere Application Servers

WebSphere Application Server:


Contain Suite of Products (one stop shop) having,
Express Application Server : Used for JSP's and Servlets deployment
Base(Enterprise) Application Server : Complete J2EE Specification
Network Deployment Application Server : Used if you are working with clustering and load balancing.

  • If you are working for clustering, load balancing, deploying on multiple systems it is better to go for Web Sphere. you can easily work on a complete E-business Application.
  • Admin Console is very good for security settings
  • This application server mainly focus on Integration, Connectivity and Web Services.
  • Websphere implementation on XML is based on latest xerces parser and xalan database, WebServices runtime and tools support.
  • It has better performance, extensive Integration, transmission management etc;
WebLogic Application Server:
  • This Application Server focus more on emerging J2EE Standards and ease of use.
  • Weblogic server's JSP compiler automatically includes java.util.package. In websphere you have to explicitly add this package.
  • easier to store config files in your own repositories.
  • easier to automate builds that include manipulation of server environment.
  • Weblogic starts faster compare to WebSphere
  • Weblogic has default transaction Attribute "Supports".

Monday, May 21, 2007

SAP acquires MaXware

This week SAP announced its acquisition of MaXware, a privately held identity management vendor located in Trondheim, Norway. The core of MaXware’s identity management offering is its user provisioning and virtualization capabilities.

SAP’s acquisition of MaXware has potential to impact the identity management market in several different ways such as:

  • Application-centric identity management becomes a reality। Oracle’s and SAP’s IdM offering will truly have tighter integration with their respective enterprise applications. Integrating with ERP applications will be simplified.
  • Identity becomes an embedded component of enterprise applications। Enterprise applications become the trigger for identity events rather than just a consumer. This has been something that Burton Group has predicted for sometime. Both SAP and Oracle have the opportunity to make this happen.
  • Identity as a service। Again this is something Burton Group has been promoting. SAP has potential to influence identity as a service by combining its NetWeaver, SOA, standards, and identity strategies.
  • Most obviously, SAP’s acquisition brings additional consolidation and competition to the IdM market

Monday, May 14, 2007

Installing the Certificate with IIS

Installing the SSL Certificate with IIS which is bought from Verisign.

  • Open the IIS console from Start> Administrative tools >IIS Manager
  • Browse to Default website which is under local computer > websites > Default website
  • Right click on Default website > Properties
  • Click on Directory Security tab
  • Click on Server Certificate under Server Communications
  • Select process pending request and Install the certificate.
  • Enter the location of your IIS SSL certificate (OR) browse to locate your IIS SSL certificate and then Click Next
  • You will see a confirmation screen.
  • When you have read this information, Click Next.
  • You now have an IIS SSL server certificate installed.

Friday, May 11, 2007

Configuring IIS Web Server with WebSphere App Server

Two Step Process:
- Generating a plugin-cfg.xml file
- Create a new virtual directory for the Web site instance to work with Web Sphere Application Server
  • Go to Web Sphere folder which is under C:\WebSphere Install and Patches\WAS6
  • Select Launchpad.bat file
  • Select launch the installation wizard for web server plug-ins
  • Check Installation roadmap. Click next
  • Select Microsoft Internet Information Services V6
  • Select Option Web Server machine(remote) - If the IIS web server is installed on same(local) machine or on remote machine, it works fine.
  • Location where plug-in has to be generated browse to C:\Program Files\IBM\WebSphere\Plugins
  • Web server port address - 80
  • Type the Server definition Name Ex: webServer1
  • Give the name plugin-cfg.xml
  • Host system where we are generating the xml file.
  • Click Finish.
From Web Server point of view - Integrating iisWASPlugin_http.dll file with IIS
  • Go to IIS Console from Control Panel >Administrative Tools>Internet Information Services(IIS) Manager
  • Expand the tree on the left until you see Default Web Site.
  • Right-click Default Web Site and select New > Virtual Directory to create the directory with a default installation
  • Type sePlugins
  • Browse to the Web Sphere Application Server "C:\Program Files\ibm\WebSphere\Plugins directory "
  • Select the Allow Read and Execute Access check box

Add the Internet Services Application Programming Interface (ISAPI) filter into the IIS configuration

  • Right-click Default Web Site in the tree on the left and click Properties
  • Go to ISAPI Filters Tab
  • Click Add to open the Filter properties window
  • Click Browse in the Executable field.
  • Click the iisWASPlugin_http.dll file.
  • Click OK
  • Type iisWASPlugin in the "Filter Name" field.
  • Expand web sites folder under local computer and click on Web Service Extensions
  • Click on Add a new web service extension on the right pane
  • Browse to the iisWASPlugin_http.dll file location under the "C:\Program Files\ibm\WebSphere\Plugins\bin \IIS_webserver1"
  • Click on Allow
Finally open the browser and give the address

ex: https://192.168.203.23/idm/login.jsp

From the webserver machine click on https://localhost/idm/login.jsp will work