Topic
  • 8 replies
  • Latest Post - ‏2012-06-26T10:14:33Z by SeanBenton
SeanBenton
SeanBenton
5 Posts

Pinned topic Publishing a Cube Model causes other Cube Models to disappear.

‏2012-06-16T02:03:05Z |
Publishing a Cube Model causes other Cube Models to disappear.

We have multiple developers of Cube Models and Cubes each using Design Studio. However when developer A performs a "import cube model" within ISW Admin Console, it deletes the Cube Model of developer B and so deletes the Cube(s) which are running. The developers have different Cubeservers. Any help appreciated with thanks.
Updated on 2012-06-26T10:14:33Z at 2012-06-26T10:14:33Z by SeanBenton
  • LongSunLi
    LongSunLi
    14 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-18T02:13:14Z  
    Hi,

    Could you please provide some detail information about this.

    Like your ISW version, Cube Server Connection type(both local or something else). Admin Console metadata database is created by the current product or migrated from old one(like ISW 952-> ISW 972).
    Another root cause may be your WAS security setting. Your developers use different WAS account to log in ISW Admin Console, right?

    Thanks,
    Long Sun
  • SeanBenton
    SeanBenton
    5 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-20T16:02:34Z  
    • LongSunLi
    • ‏2012-06-18T02:13:14Z
    Hi,

    Could you please provide some detail information about this.

    Like your ISW version, Cube Server Connection type(both local or something else). Admin Console metadata database is created by the current product or migrated from old one(like ISW 952-> ISW 972).
    Another root cause may be your WAS security setting. Your developers use different WAS account to log in ISW Admin Console, right?

    Thanks,
    Long Sun
    Hi, thank you for the response.

    The version is 973.
    "Admin Console metadata database is created by the current product" . . .true, it is a new installation and we are new to the whole environment.

    We have created a DB2 connection to the actual database (where the Invoice and Orders data is stored), this is created using ISW Admin Console/Manage Connections Tab.

    To pull in the changes from a cube we use Design Studio and Export ... OLAP Metadata . . .and save the xml file. Then we use Admin Console to 'import cube model'

    We think it is something to do with multiple users using the same connection name or something like this.

    Thanks again
  • LongSunLi
    LongSunLi
    14 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-21T06:36:50Z  
    Hi, thank you for the response.

    The version is 973.
    "Admin Console metadata database is created by the current product" . . .true, it is a new installation and we are new to the whole environment.

    We have created a DB2 connection to the actual database (where the Invoice and Orders data is stored), this is created using ISW Admin Console/Manage Connections Tab.

    To pull in the changes from a cube we use Design Studio and Export ... OLAP Metadata . . .and save the xml file. Then we use Admin Console to 'import cube model'

    We think it is something to do with multiple users using the same connection name or something like this.

    Thanks again
    Hi, Thanks for your information.
    I just tried scenario with ISW 973:
    1. Create cube server "test" with connection type:local host
    2. With machine "A", log in admin console. Import cube model A and add cube a to cube server "test". Start cube a in the cube server
    3. With machine "B", log in admin console. Import cube model B.
    After this, both cube model A and B appear in the dialog. And running cube a work well in the cube server "test".

    The scenario is the same with yours?
  • SeanBenton
    SeanBenton
    5 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-21T07:36:47Z  
    • LongSunLi
    • ‏2012-06-21T06:36:50Z
    Hi, Thanks for your information.
    I just tried scenario with ISW 973:
    1. Create cube server "test" with connection type:local host
    2. With machine "A", log in admin console. Import cube model A and add cube a to cube server "test". Start cube a in the cube server
    3. With machine "B", log in admin console. Import cube model B.
    After this, both cube model A and B appear in the dialog. And running cube a work well in the cube server "test".

    The scenario is the same with yours?
    Hi
    No, when we import Cube Model B, the Cube from A vanishes from cubeserver test. Thanks for looking.
  • LongSunLi
    LongSunLi
    14 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-21T07:45:27Z  
    Hi
    No, when we import Cube Model B, the Cube from A vanishes from cubeserver test. Thanks for looking.
    You mean other steps are the same except vanish, right?
    This is really strange, the scenario works well in my Env.

    How about your WAS security setting? Developper A and B log in Admin Console using the same account?
  • SeanBenton
    SeanBenton
    5 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-24T10:56:52Z  
    • LongSunLi
    • ‏2012-06-21T07:45:27Z
    You mean other steps are the same except vanish, right?
    This is really strange, the scenario works well in my Env.

    How about your WAS security setting? Developper A and B log in Admin Console using the same account?
    Yes, the other steps are the same. We use our own (dfferent) logins for Admin Console. Thanks.

    We found that if we make the connection string different (so 1 wth IP address and one with ServerName) the 2 developers can import Cube Models without affecting each other but we will have more than 2 developers and probably many cubes.
  • LongSunLi
    LongSunLi
    14 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-25T02:02:41Z  
    Yes, the other steps are the same. We use our own (dfferent) logins for Admin Console. Thanks.

    We found that if we make the connection string different (so 1 wth IP address and one with ServerName) the 2 developers can import Cube Models without affecting each other but we will have more than 2 developers and probably many cubes.
    It seems like your two cube models using the same connection name. How about your cube model name? Cube Model name is the same? I just tried scenario:
    1.Import Cube model A(cube model name is "a") using connection name "connection"
    2.Import Cube model B(cube model name is "b") using connection name "connection"
    This could work as expected too.
    If 2 cube model name is the same, the older one maybe replaced with option selected.

    And I am a little confused about your connection string(IP address), you mean one connection named with ServerName and another named with IP address?
  • SeanBenton
    SeanBenton
    5 Posts

    Re: Publishing a Cube Model causes other Cube Models to disappear.

    ‏2012-06-26T10:14:33Z  
    • LongSunLi
    • ‏2012-06-25T02:02:41Z
    It seems like your two cube models using the same connection name. How about your cube model name? Cube Model name is the same? I just tried scenario:
    1.Import Cube model A(cube model name is "a") using connection name "connection"
    2.Import Cube model B(cube model name is "b") using connection name "connection"
    This could work as expected too.
    If 2 cube model name is the same, the older one maybe replaced with option selected.

    And I am a little confused about your connection string(IP address), you mean one connection named with ServerName and another named with IP address?
    Hi

    The Model Names (and Cube Names) are different.

    For the connections, we have created 2 different ones. The difference is that one uses the IP address of the server in the connection string, whereas the other connection uses the server name to connect. Thank you for your time, your help is appreciated.