Topic
  • 3 replies
  • Latest Post - ‏2014-06-06T19:43:03Z by wprater
vidyabharati
vidyabharati
8 Posts

Pinned topic Merge/Extract workspaces: Libnet schema & improving merge/ extract speed

‏2010-04-01T03:45:25Z |
Hi,
We have recently merged many encylopedias into a single enterprise encyclopedia.

1) I encountered this error during the process of merge/ extract: "Upgrading to Libnet Schema" - does anyone know what this means and how to solve this?

2) Is there a way to improve merge/ extract speed (between workspaces) with a huge encyclopedia?

Thanks!
Vidya
Updated on 2010-04-22T21:22:35Z at 2010-04-22T21:22:35Z by vidyabharati
  • sharmishtha chatterjee
    1 Post

    Re: Merge/Extract workspaces: Libnet schema & improving merge/ extract speed

    ‏2010-04-05T08:53:16Z  
    Hi Vidya

    I found this technote on the IBM website for the question, "Why does System Architect throw the following error: Upgrading encyclopedia to libnet schema, when the user tries to open the upgraded encyclopedia in SA v11.3.1?"
    which explains why this error occurs and what should be done to eliminate it.

    Answer: The message "Upgrading encyclopedia to libnet schema" occurs because the encyclopedia upgradation process might have been in progress or crashed during libnet schema operation.

    Hence, you may have to turn off libnet schema and try to convert again to see if it finishes successfully.

    To do this, you will have to do the following.

    1. Navigate to "C:\Documents and Settings\Administrator\Local Settings\Application
    Data\Telelogic\System Architect" and open the SA2001.ini file.
    In sa2001.ini file, set the following

    System Architect
    OverrideOptimizedXTReader=Y
    2. Launch System Architect Encyclopedia Manager SAEM and restore the encyclopedia backup file.
    3. Then click on "Tools" >> "Encyclopedia schema". Uncheck the option "OptimizedXTReader
    schema". Click OK

    4. Once again login into System Architect Encyclopedia Manager SAEM >> Tools >> Encyclopedia
    Schema, and check the option "OptimizedXTReader" . Click ok
    .
    5. You would get a prompt that previous instance of SA application should be closed. Click OK on this dialog
    6. Ensure that the upgradation process finishes successfully.
    NOTE: Before performing the above steps, close System Architect application
    Another approach that could be tried is that we can open the encyclopedia in the original version, export usrprops of the encyclopedia as well as the entire encyclopedia contents in XML format.

    Then, create a new encyclopedia in the target version (which will have all the latest configurations). Then then import the XML and the usrprops (if required)

    Hope this info helps.

    Regards
    Sharmishtha
  • vidyabharati
    vidyabharati
    8 Posts

    Re: Merge/Extract workspaces: Libnet schema & improving merge/ extract speed

    ‏2010-04-22T21:22:35Z  
    Thanks! It works...

    Just wondering if anyone has merged all encyclopedias into an Enterprise Encyclopedia and face issues with speed?

    Thanks..
  • wprater
    wprater
    1 Post

    Re: Merge/Extract workspaces: Libnet schema & improving merge/ extract speed

    ‏2014-06-06T19:43:03Z  
    Thanks! It works...

    Just wondering if anyone has merged all encyclopedias into an Enterprise Encyclopedia and face issues with speed?

    Thanks..

    Hi.  I was doing some research on developer works and noticed your problem.  We have not experienced your problem, but we are attempting to manage an integrated dev environment.  I am curious how your encyclopedia environment is set up.  We have 2 high level requirements.  1.  Support many functional area architectures which have many architecture projects, and 2.  Have a single, integrated architecture used by decision makers.  To date, we have had all our architects working from a single encyclopedia.  But it is proving to be more difficult as we grow.  We are identifying what the options are to accomplish both of our requirements.  1.  Stay with a single encyclopedia that everyone works from.  2.  Use 'sandbox' encyclopedias for each architecture project.  Then merge the architecture content into a single, integrated encyclopedia when it is approved and becomes baseline.  3.  use IBM's workspaces.   We are not familiar with workspaces at all and not sure of the benefits, other than a single usrprops file.

    If this sounds familiar to you, I would appreciate to hear how you handle it and how successful you have been.

    Thanks,

    Will Prater