Learn more
 

Replicate SAP BusinessObjects BI Data from PowerShell


Write a quick PowerShell script to query SAP BusinessObjects BI data. Use connectivity to the live data to replicate SAP BusinessObjects BI data to SQL Server.



The CData ODBC Driver for SAP BusinessObjects BI enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real SAP BusinessObjects BI data with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating SAP BusinessObjects BI data to other databases. This article shows how to replicate SAP BusinessObjects BI data to SQL Server in 5 lines of code.

You can also write PowerShell code to download SAP BusinessObjects BI data. See the examples below.

Create an ODBC Data Source for SAP BusinessObjects BI

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

To connect to your SAP Business Objects BI instance, you must set the following connection properties:

  • Url: set this to the rest API URL. After logging into the Central Management Console, choose 'Applications' from the combo box. Double-click on 'RESTful Web Service' and you'll see the access URL. By default it is, http://{Server-Name}:6405/biprws.
  • User: set this to the username of your instance.
  • Password: set this to the password of your instance.

Connect to SAP BusinessObjects BI

The code below shows how to use the DSN to initialize the connection to SAP BusinessObjects BI data in PowerShell:

$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData SAPBusinessObjectsBI Source x64"

Back Up SAP BusinessObjects BI Data to SQL Server

After you enable caching, you can use the code below to replicate data to SQL Server.

Set the following connection properties to configure the caching database:

  • CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.

  • CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:

    Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;

The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.

$conn.Open() # Create and execute the SQL Query $SQL = "CACHE DROP EXISTING SELECT * FROM " + $MyCustomReport $cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn) $count = $cmd.ExecuteNonQuery() $conn.Close()

The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.

Other Operations

To retrieve SAP BusinessObjects BI data in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples commands to SAP BusinessObjects BI through the .NET Framework Provider for ODBC:

Retrieve SAP BusinessObjects BI Data

$sql="SELECT StoreName, TotalRevenue from MyCustomReport" $da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn) $dt= New-Object System.Data.DataTable $da.Fill($dt) $dt.Rows | foreach { $dt.Columns | foreach ($col in dt{ Write-Host $1[$_] } }

Ready to get started?

Download a free trial of the SAP BusinessObjects BI ODBC Driver to get started:

 Download Now

Learn more:

SAP BusinessObjects BI Icon SAP BusinessObjects BI ODBC Driver

The SAP BusinessObjects BI ODBC Driver is a powerful tool that allows you to connect with live data from SAP BusinessObjects BI, directly from any applications that support ODBC connectivity.

Access SAP BusinessObjects BI data like you would a database through standard ODBC Driver interface.

In this article

Related articles