Author Topic: Creating cognos report front end either .NET or java?  (Read 114 times)

0 Members and 1 Guest are viewing this topic.

Offline CyborgRepublic

  • Full Member
  • *
  • Posts: 201
  • Karma: +0/-0
    • View Profile
Creating cognos report front end either .NET or java?
« on: November 08, 2008, 06:16:21 PM »
Which is better for creating cognos report front end either .NET or java?

Techronnati | where technology never sleeps

Creating cognos report front end either .NET or java?
« on: November 08, 2008, 06:16:21 PM »

Mountain View

Offline MrSpecialist

  • Sr. Member
  • *
  • Posts: 342
  • Karma: +1/-0
  • I'm an expert!
    • View Profile
Re: Creating cognos report front end either .NET or java?
« Reply #1 on: November 08, 2008, 06:24:28 PM »
Hello, i\'ve just learned that Cognos SDK is expected to be fully functional with either a .NET or Java interface. You may find an easier time implementing your solution with a Java solution only because the majority of the examples provided by Cognos are in Java. The backend architecture of Cognos is Java. However, you can also use SOAP calls to invoke your Cognos application and won\'t have to worry about adding .DLLs. I hope this answers your question dude. =)

 

Related Topics

  Subject / Started by Replies Last post
0 Replies
107 Views
Last post October 14, 2008, 05:26:10 PM
by h2obubbler
0 Replies
126 Views
Last post November 27, 2008, 03:00:28 PM
by Corps
0 Replies
70 Views
Last post April 02, 2009, 05:43:44 AM
by MrSpecialist
2 Replies
103 Views
Last post May 06, 2017, 11:20:01 PM
by CyborgRepublic
0 Replies
64 Views
Last post December 14, 2016, 10:20:26 AM
by MrSpecialist

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.