If you are following the posts for the sample Cognos SDK solution then you won’t want to miss the last few posts that talk about the CognosSDK.cs class file. Follow the link below to take you to the Cognos SDK discussion about authenticating a user session.
http://bicentresdkguide.blogspot.com/2007/12/cognossdkcs-authentication.html
If you are following the posts for the sample Cognos SDK solution then you won’t want to miss the last few posts that talk about the CognosSDK.cs class file. Follow the link below to take you to the Cognos SDK discussion about authenticating a user session.
http://cognos8helpsdkguide.blogspot.com/2007/12/cognossdkcs-authentication.html
The Cognos 8 security model allows you to integrate directly into your existing user repositories, such as Active Directory, in order to handle authentication. It also maintains a granular authorization model that can be used directly for your BI solution.
| | | Content Manager Cognos Namespace Content Permissions | | |
| | --- | | |
| | Interface to Providers Authorization | | |
| | --- | | |
| | | | |
| | | | |
| | | | | |
| Authentication Providers | | Encryption Providers | | Certificate Authority |
| | | | | |
The Cognos 8 security model allows you to integrate directly into your existing user repositories, such as Active Directory, in order to handle authentication. It also maintains a granular authorization model that can be used directly for your BI solution.
| | | Content Manager Cognos Namespace Content Permissions | | |
| | --- | | |
| | Interface to Providers Authorization | | |
| | --- | | |
| | | | |
| | | | |
| | | | | |
| Authentication Providers | | Encryption Providers | | Certificate Authority |
| | | | | |
Have you ever wanted to query the Cognos 8 Content Store to retrieve a report’s attributes by using the Cognos 8 SDK?
Unfortunately, I have not been able to find a specific Cognos 8 SDK method that will handle this. However, there is a work around that you can use with the Cognos 8 SDK. You would retrieve the Cognos 8 Report Studio report xml schema by using the SDK and then in your SDK project you would parse the xml nodes for a series of specified report nodes. You would have to become familiar with the expected Cognos 8 report schema elements.
Have you ever wanted to query the Cognos 8 Content Store to retrieve a report’s attributes by using the Cognos 8 SDK?
Unfortunately, I have not been able to find a specific Cognos 8 SDK method that will handle this. However, there is a work around that you can use with the Cognos 8 SDK. You would retrieve the Cognos 8 Report Studio report xml schema by using the SDK and then in your SDK project you would parse the xml nodes for a series of specified report nodes. You would have to become familiar with the expected Cognos 8 report schema elements.
If you are having an issue being able to use View your Cognos Report Studio report in PDF or Excel, then you should check to see if your proxy server is blocking the required HTTP parameters. If HTTP_COOKIE, CRN_SESSION and HTTP_ACCEPT are missing, the request is blocked by the proxy server.
You could try to disable the Proxy Server in your browser settings, or modify the security policy to allow the HTTP_COOKIE, CRN_SESSION and HTTP_ACCEPT parameters to pass. Another option is to upgrade to the latest patch of Internet Explorer.
If you are having an issue being able to use View your Cognos Report Studio report in PDF or Excel, then you should check to see if your proxy server is blocking the required HTTP parameters. If HTTP_COOKIE, CRN_SESSION and HTTP_ACCEPT are missing, the request is blocked by the proxy server.
You could try to disable the Proxy Server in your browser settings, or modify the security policy to allow the HTTP_COOKIE, CRN_SESSION and HTTP_ACCEPT parameters to pass. Another option is to upgrade to the latest patch of Internet Explorer.
Hello, here is the initial Table of Contents for the upcoming BI Centre SDK Guide which will be available on http://bicentresdkguide.blogspot.com. If you have any questions or items that you would like to have covered in the Cognos SDK guide then feel free to email me at: BI Centre SDK Guide.
Table of Contents
Hello, here is the initial Table of Contents for the upcoming BI Centre SDK Guide which will be available on http://cognos8helpsdkguide.blogspot.com. If you have any questions or items that you would like to have covered in the Cognos SDK guide then feel free to email me at: BI Centre SDK Guide.
Table of Contents
When you are planning your BI reporting environment and are ready to start designing your reports you must ensure that you Identify security or user specific content that needs to be built into a report.
Often a single report is requested that will display different data or different layouts to different users or groups. This type of report should really be considered as two or more different reports layouts as requirements will need to be gathered for each layout and set of security requirements.
You will also need to identify the source of the security information that will be leveraged to satisfy these different layout rules. The layouts may be triggered by the user id session parameter although additional data and security restrictions may be contained within a database table that is keyed by the individual user ID. Also, depending on how the report is to be consumed you may be working with only the data from a security table such as with burst output as there are no session parameters available at the time that the burst report is executed.
When you are planning your BI reporting environment and are ready to start designing your reports you must ensure that you Identify security or user specific content that needs to be built into a report.
Often a single report is requested that will display different data or different layouts to different users or groups. This type of report should really be considered as two or more different reports layouts as requirements will need to be gathered for each layout and set of security requirements.
You will also need to identify the source of the security information that will be leveraged to satisfy these different layout rules. The layouts may be triggered by the user id session parameter although additional data and security restrictions may be contained within a database table that is keyed by the individual user ID. Also, depending on how the report is to be consumed you may be working with only the data from a security table such as with burst output as there are no session parameters available at the time that the burst report is executed.
When you are planning your BI reporting environment and are ready to start designing your reports you must ensure that you identify the required user interaction.
When you are planning your BI reporting environment and are ready to start designing your reports you must ensure that you identify the required user interaction.
Here is a Cognos SDK example of getting a report parameter’s type.
You would have to generate a C# class object that makes your Cognos SDK method calls. From your entry method you will reference the getReportParameters() method.
………….
baseParameter[] param = CogSDK.getReportParameters( "/content/package[@name='GO Sales and Retailers']/folder[@name='Documentation Report Samples']/report[@name='Order Method Between List']", reportService );
foreach( parameter p in param )
{
Console.WriteLine( "Name: {0}, Type: {1}", p.name, p.type );
}
……….
public baseParameter[] getReportParameters( string reportPath, reportService1 c8RS )
{
searchPathSingleObject cmReportPath = new searchPathSingleObject();
cmReportPath.Value = reportPath;
asynchReply gpReply = c8RS.getParameters( cmReportPath, new parameterValue[] {}, new runOption[]{} );
if ((gpReply.status != asynchReplyStatusEnum.complete)
&& (gpReply.status != asynchReplyStatusEnum.conversationComplete) )
{
while ( (gpReply.status != asynchReplyStatusEnum.complete)
&& (gpReply.status != asynchReplyStatusEnum.conversationComplete) )
{
gpReply = c8RS.wait(gpReply.primaryRequest,new parameterValue[] {}, new option[] {});
}
}
if (gpReply.details == null)
{
return null;
}
for (int i = 0; i < gpReply.details.Length; i++)
{
if (gpReply.details[i] is asynchDetailParameters)
{
return ((asynchDetailParameters)gpReply.details[i]).parameters;
}
}
return null;
}
Here is a Cognos SDK example of getting a report parameter’s type.
You would have to generate a C# class object that makes your Cognos SDK method calls. From your entry method you will reference the getReportParameters() method.
………….
baseParameter[] param = CogSDK.getReportParameters( "/content/package[@name='GO Sales and Retailers']/folder[@name='Documentation Report Samples']/report[@name='Order Method Between List']", reportService );
foreach( parameter p in param )
{
Console.WriteLine( "Name: {0}, Type: {1}", p.name, p.type );
}
……….
public baseParameter[] getReportParameters( string reportPath, reportService1 c8RS )
{
searchPathSingleObject cmReportPath = new searchPathSingleObject();
cmReportPath.Value = reportPath;
asynchReply gpReply = c8RS.getParameters( cmReportPath, new parameterValue[] {}, new runOption[]{} );
if ((gpReply.status != asynchReplyStatusEnum.complete)
&& (gpReply.status != asynchReplyStatusEnum.conversationComplete) )
{
while ( (gpReply.status != asynchReplyStatusEnum.complete)
&& (gpReply.status != asynchReplyStatusEnum.conversationComplete) )
{
gpReply = c8RS.wait(gpReply.primaryRequest,new parameterValue[] {}, new option[] {});
}
}
if (gpReply.details == null)
{
return null;
}
for (int i = 0; i < gpReply.details.Length; i++)
{
if (gpReply.details[i] is asynchDetailParameters)
{
return ((asynchDetailParameters)gpReply.details[i]).parameters;
}
}
return null;
}