Recent Posts

Pages: [1] 2 3 ... 10
1
Administration and Security / Re: Cognos 11 Licensing
« Last post by MFGF on Today at 03:37:04 am »
What we have essentially is 4 sets of licenses:

1) An Analytics User PVU license which allows our user base to run reports and use some of the higher capabilities (QS, AS, Workspace etc). Not that we let everyone use the higher capabilities of course.

2) Analytics User Named Licenses. These are assigned to users on a needs must basis so they can UAT reports in Dev and Test environments.

3) Named Analytics Explorer - Advanced developers.

4) Named Admin licenses (enough for Prod, Dev and Test).

If you no longer need to license the 'Non-Production' environments then we would no longer need the Analytics User Named Licenses. This would save some significant cost as we are about to renew.

The trouble is that our asset management team have the relationship with IBM Account Manager. But they do not fully understand the complexities of the Cognos licensing model. So it is a bit like chinese whispers.

Hi,

You haven't specified whether your Analytics User PVU license is for a production instance or a non-production instance. I'm assuming production?

Your Analytics User "Named User" licenses allow these named users to use any of your instances of Cognos - including Dev, Test and Production (although the PVU license you have covers Production anyway.) If you remove these Analytics User "Named User" licenses from your license pool, and you don't have a non-production PVU license covering the server(s) Dev and Test are installed on, you are effectively taking away the ability for Analytics User access to anything apart from your PVU licensed production instance.

I'm not sure where you're getting the idea from that you no longer need to license Non-Production environments? If you're using the PVU model, you need to have PVU non-prod licenses for Dev and Test. If you're using the Named User model, your users are covered for all instances. You're currently using a mixed model, but you appear to have only one PVU license covering Production? This means you need your named user licenses for non-production access (Dev and Test).

I'm intrigued about your multiple Admin licenses though. Is this because you have multiple named users acting as Administrators? If it's just one person, you only need one license, and it covers him/her for all your Cognos instances.

I'd honestly recommend you find out who your IBM account manager is and reach out to him/her to discuss this.

Cheers!

MF.
2
instead of "?p_param?", use "#prompt('p_param','token','insertyourdefaultvaluehere')#", or promptmany in case of multiple value parameters.
3
Administration and Security / Re: Cognos 11 Licensing
« Last post by juetron on Today at 03:03:38 am »
What we have essentially is 4 sets of licenses:

1) An Analytics User PVU license which allows our user base to run reports and use some of the higher capabilities (QS, AS, Workspace etc). Not that we let everyone use the higher capabilities of course.

2) Analytics User Named Licenses. These are assigned to users on a needs must basis so they can UAT reports in Dev and Test environments.

3) Named Analytics Explorer - Advanced developers.

4) Named Admin licenses (enough for Prod, Dev and Test).

If you no longer need to license the 'Non-Production' environments then we would no longer need the Analytics User Named Licenses. This would save some significant cost as we are about to renew.

The trouble is that our asset management team have the relationship with IBM Account Manager. But they do not fully understand the complexities of the Cognos licensing model. So it is a bit like chinese whispers.


4
RAVE Visualizations / Re: Chart Size in percentage
« Last post by TreleMorele on Today at 02:32:10 am »
you can add via an html elemtent a jscript for using different sizes of charts depending on the resolution. but this is not something already implemented for users.
5
Dashboards / Re: Publish dashboard full screen without menu bar
« Last post by TreleMorele on Today at 02:02:05 am »
use the link used for embedding
6
Report Studio / How native SQL prepared in Cognos report studio
« Last post by ajskumar on Today at 12:52:18 am »
How the native SQL prepared in cognos report studio

Using 32 bit ODBC driver to connect to database (Jethro)

1. ODBC drivers provided by Database owner
2. IBM query engine (UDA)
3. Any other methodology

Please confirm.
7
Security / Due to Security - Report Run Time is increased
« Last post by Kiran Kandavalli on 23 Aug 2017 11:51:13 pm »
Team,

I have Two Dimensions and a Fact Tables which are driving my Reports. I need to apply security based on AD Groups created.

We have a Lookup Security Table which is 'Security Table' in the below code

In the Framework Model --> Database Layer --> Using Native SQL using a query we are applying the Filter Conditions on the Fact Table as below. The Report use to Run for 10 Secs and after implementing the Security in FM the Report is Running for 1 minute.

Please let me know if I need to change the below SQL, to improve the performance.

Code: [Select]
select f.* from FactTable f
join DIMTable1 p on p.PCCode = f.PCCode
where exists (
    select distinct 1 from SecurityTable s
        join DIMTable2 c on c.CCode = s.N_KEY
    where s.line_of_biz = 'MF' and s.active_ind = 'Y'
    and (
        case
            when s.ldap_DSC = 'GROUP_NAME' and s.ldap_common_name in ( #CSVIdentityNameList()# ) then f.CCode = s.N_KEY
            when s.ldap_DSC = 'USER_NAME' and s.ldap_common_name = #sq($account.personalInfo.userName)# then f.CCode = s.N_KEY
        end
    )
)
union
select f.* from FactTable f
where exists (
    select distinct 1 from SecurityTable s
        join DIMTable1 p on p.PCCode = s.N_KEY
    where s.line_of_biz = 'MF' and s.active_ind = 'Y'
    and (
        case
            when s.ldap_DSC = 'GROUP_NAME' and s.ldap_common_name in ( #CSVIdentityNameList()# ) then f.PCCode = s.N_KEY
            when s.ldap_DSC = 'USER_NAME' and s.ldap_common_name = #sq($account.personalInfo.userName)# then f.CCode = s.N_KEY
        end
    )
)

Thanks!
Kiran
8
Framework Manager / Re: Merge query subject versus create model query subject.
« Last post by Penny on 23 Aug 2017 02:49:04 pm »
Answer:

I see now that the individual query items show the namespace that the item is derived from (the layer name).  Don't know how I missed that.  Guess I had a good vacation.
9
Framework Manager / Merge query subject versus create model query subject.
« Last post by Penny on 23 Aug 2017 02:35:09 pm »
Hi everyone
This may be a silly question, but I just want to confirm my understanding.  I am modelling against a relational database using Cognos Framework Manager 11.0.6.  The model has four layers:
   database layer - database query subjects from data source, all are select * from tablename
   consolidation layer - model query subjects created from database layer - all joins are here
   business layer - model query subjects created from consolidation layer - no joins are here, but there is some merging, calculations, renaming etc.
   presentation layer - all shortcuts to the business layer

1.  The database layer has database query subjects created with the metadata wizard using the data source (an Oracle database) as the metadata source.  These query subjects show up with the little database icon.

2.  In the consolidation layer, we have created model query subjects and used the database query subject as the source.  These query subjects show up with no database icon.

3.  In the business layer, we have created model query subjects and used the model query subject from the consolidation layer.

My questions:

If we 'merge in new query subject' from the database layer, creating a new query subject and answer no to the question 'Do you want to recreate these relationships with the new query subject?', the new query subject is sitting in the database layer, has no database icon, is named TABLENAME_TABLENAME.  If I move this to the next layer (business layer) by dragging and dropping, is this the same as result as step 2 above?

How can I tell afterwards what model source a query subject used ie. which layer.  The sql for both look the same, the icons are the same and I don't see a property that indicates the answer.

Thanks in advance for any comments/advice you may be willing to share with me.
10
Report Studio / Re: crosstab space height
« Last post by Michael75 on 23 Aug 2017 12:55:00 pm »
Hi,

A kind moderator has moved further discussion in thus topic to here, if you're interested: http://www.cognoise.com/index.php/topic,33483.0.html
Pages: [1] 2 3 ... 10

       
Twittear