Skip to Content

Getting Started with BOBJ .NET SDK 3.1 SP4 EDGE

I am trying to get started with some SDK work (.NET). I have not done SDK since my 6.5 days of VBA in Full Client Documents. I have downloaded all of the documentation I can find about the SDK but something that would be really helpful would be a general overview of how to get started.

  • What do I have to download or where do I find the files I need? (object libraries, .jar files, runtime)
  • How do I add .NET SDK to my .NET applications? (register .dll, copy files to folders.)
  • One article I found referenced a runtime download file that isn't in my list of products in Service Marketplace. How do I get them? I currently have a support ticket open on this one.
  • Is there a way to call the JAVA SDK from a .NET application?

I am on 3.1 SP4 right now. But will also need to know the same information for when I upgrade to 4.1 next year sometime!

  • What's compatible?
  • What's different?
  • What's new?
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Nov 15, 2012 at 02:31 PM

    Hi Tammy!

    The .NET and Java SDKs can be installed from either the server install or the client install in 3.1. When you do the installation, it registers the .NET assemblies in the GAC so that they are available when you select the "References" for a project in Visual Studio.

    There is no way to run the Java SDK directly from .NET without installing a third-party component that will translate the Java to .NET. I've played with this a bit recently for a project for a client - it's very memory intensive and can be slow. I finally ended up writing the code I needed in Java (access to assign/read custom access levels is not available in the .NET SDK until the SP5 release of BI 4.0) and shelling out to it to get the functionality I needed.

    The move to 4.x is a little problematic because the COM Interop modules are embedded in the .NET assemblies. So, if you use VS 2008, you need to use the Interface versions of the classes (e.g. IInfoStore instead of InfoStore, etc.) If you're in VS 2010, there is a property in the assembly reference called "Embed Interop Types" which you can set to False and use the non-Interface version of the classes.

    Also in 4.x there are some problems getting to the properties of specific reports in the regular SDK - you have to use the Web Services SDK to access them.

    Are you working in C#, VB.NET, or VBA? If you're interested, I have a lot of sample C# code on my website: www.dellstinnett.com/sample_code.html.

    -Dell

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Tammy

      I've been following this tread with interest as I always learn tons from Dell. And on occasion I can actually add value my self 😊. In this case, there are two things to consider;

      1) The assemblies from BusinessObjects Enterprise XI 3.1 v 12.x) are not supported in VS2010 (only assemblies from BI 4.0 (v 14.x) are supported in that version of .NET). Now, I am not saying this is the cause of the issue as theoretically the assemblies should work - as long as framework 4.0 is not used. However, the developer is in an untested and thus unsupported environment. If the developer wants to use the 12.x assemblies, I'd strongly recommend using VS2008.

      2) The log4net error is well documented on these forums as well as KBases, etc. Simply use the search term 'log4net crystal net' in the search box at the top of this web page and you should get a number of hits (KBs, discussions, wiki(s), etc., etc.).

      - Ludek

      Follow us on Twitter

      Got Enhancement ideas? Try the SAP Idea Place

      Share Your Knowledge in SCN Topic Spaces

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.