November 21, 2007

The page cannot be found in Infoview

In Business Objects XI, you may get an error saying The page cannot be found when trying to access InfoView or the Central Management Console. One cause for this problem is that, on Windows Server 2003, IIS 6.0 blocks .NET 2.o .aspx applications by default. To enable them, go to Administrative Tools -> Internet Information Services (IIS) Manager, click the Web Service Extensions, select ASP .NET v2.0xxxx and click Allow.

Detailed info on this operation:

[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed

When trying to log on to InfoView on BusinessObjects XI, you may get this error because the CMS can't be contacted. This may be happen because of a firewall or traffic filtering on your network. The first reason is reasonably easy to solve: make sure there is no firewall blocking you in the path from the client to the BO server. If you suspect it's the latter, try putting localhost on the System textbox.

November 1, 2007

Access and consume a Web Service from Integration Services

Sometimes you need to consume a Web Service that is specific enough for you not be able to use the default Web Service Task available on SSIS 2005.

In this example I'm going to show how to consume a Web Service that returns a .NET object (a serialized DataSet, for example). For this, we'll have to use a Script Component that allows us to insert some custom code that is able to do what we need. The
Script Component will be part of a Data Flow acting as a Source that provides rows to Transformations down the pipeline.

Acessing a Web Service from a Script Component is pretty much similar to how we'd do it in a standard .NET application:
  1. You need a proxy class (in the VB language) for the Web Service you want to consume. You can create it using the wsdl.exe application like this:
    wsdl /language:VB http://yourserver/yourWebService?WSDL /out:yourProxyClass.vb
  2. Access the Script Component's code and, on the code window, go to the Project menu and select "Add Existing Item". The item you have to add is the proxy class you created previously (yourProxyClass.vb, in this example). Next, go to the Project menu, select "Add Reference" and add the System.Xml and System.Web.Services assemblies.
  3. Now you have to write the code to acess the Web Service and output its results onto the outputs you defined for the Script Component.
    In this example, the Web Service defines a class called Export which has a method called getDataSet(String) that outputs is a serialized DataSet. The Script Component has one output, called Output0, with two columns (colOne and colTwo) defined as a String (DT_STR)
Public Class ScriptMain
Inherits UserComponent

Dim webServiceExport As Export
Dim dsResults As DataSet

'Prepare the required connections and initialize objects
Public Overrides Sub AcquireConnections(ByVal Transaction As Object)

webServiceExport = New Export()
dsResults = Nothing

End Sub

'Get the data from the WebService
Public Overrides Sub PreExecute()

webServiceExport.Timeout = 3600
dsResults = webServiceExport.getDataSet("test parameter string")

End Sub

'Go through the received data and add it to the output rows
Public Overrides Sub CreateNewOutputRows()

Dim dtResults As New DataTable

dtResults = dsResults.Tables(0)

Output0Buffer.colOne = dtResults.Columns(0).ToString()
Output0Buffer.colTwo = dtResults.Columns(1).ToString()


End Sub

End Class

If you need some Web Services for testing you can search at

Detailed information links:
Referencing Assemblies in a script:
Using the Script Component as a source: