CWWIM6109E Property extension repository is not defined - Websphere

This is a discussion on CWWIM6109E Property extension repository is not defined - Websphere ; I am running the 'ConfigEngine.bat wp-configure-la-complete -DWasPassword=******' task as per the 'Configuring a property extension database on Windows' instructions on located at: http://publib.boulder.ibm.com/infoce...kaside_db.html Upon running this config engine task i am receiving the following error: [wplc-add-property] [11/30/09 11:12:14.975 EST] Config ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: CWWIM6109E Property extension repository is not defined

  1. CWWIM6109E Property extension repository is not defined

    I am running the 'ConfigEngine.bat wp-configure-la-complete -DWasPassword=******' task as per the 'Configuring a property extension database on Windows' instructions on located at: http://publib.boulder.ibm.com/infoce...kaside_db.html

    Upon running this config engine task i am receiving the following error:

    [wplc-add-property] [11/30/09 11:12:14.975 EST] Config schema registered.
    [wplc-add-property] com.ibm.websphere.wim.exception.DynamicUpdateConfi gException: CWWIM6109E Property extensio
    n repository is not defined.
    [wplc-add-property] at com.ibm.ws.wim.SchemaManager.createSchema(SchemaMa nager.java:1527)
    [wplc-add-property] at com.ibm.websphere.wim.ServiceProvider.createSchema (ServiceProvider.java:175)
    [wplc-add-property] at com.ibm.websphere.wim.ejb.WIMServiceBean.createSch ema(WIMServiceBean.java:119)
    [wplc-add-property] at com.ibm.websphere.wim.ejb.EJSRemoteStatelessWIMSer vice_a12c79ef.createSchema(Unknow
    n Source)
    [wplc-add-property] at com.ibm.websphere.wim.ejb._EJSRemoteStatelessWIMSe rvice_a12c79ef_Tie.createSchema(_
    EJSRemoteStatelessWIMService_a12c79ef_Tie.java:237 )
    [wplc-add-property] at com.ibm.websphere.wim.ejb._EJSRemoteStatelessWIMSe rvice_a12c79ef_Tie._invoke(_EJSRe
    moteStatelessWIMService_a12c79ef_Tie.java:152)
    [wplc-add-property] at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHa ndler(ServerDelegate.java:627)
    [wplc-add-property] at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerD elegate.java:480)
    [wplc-add-property] at com.ibm.rmi.iiop.ORB.process(ORB.java:512)
    [wplc-add-property] at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571)
    [wplc-add-property] at com.ibm.rmi.iiop.Connection.respondTo(Connection.j ava:2719)
    [wplc-add-property] at com.ibm.rmi.iiop.Connection.doWork(Connection.java :2584)
    [wplc-add-property] at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl. java:62)
    [wplc-add-property] at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.ja va:118)
    [wplc-add-property] at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1497)

    BUILD FAILED
    D:\IBM\WebSphere\wp_profile\ConfigEngine\config\ac tions\wp_security_pub.xml:1285: Add LA properties failed.



    My environment is Windows Server 2003, SQL Server 2005. I have a single node cluster with federated deployment manager.

    Any assistance to resolve this issue and to add a new property to the property extension configuration would be greatly appreciated.

  2. Re: CWWIM6109E Property extension repository is not defined

    This looks like output from the "wp-add-la-property" ConfigEngine script, not the "wp-configure-la-complete" script. Could you please upload the ConfigTrace.log file?

    wp_profile/ConfigEngine/log/ConfigTrace.log

    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

  3. Re: CWWIM6109E Property extension repository is not defined

    Hi httweed

    yes, you are correct - thanks for the pick up, the command that is failing is:
    ConfigEngine wp-add-la-property -DWasPassword=********

    Here is the config file you have requestsd

  4. Re: CWWIM6109E Property extension repository is not defined

    Thanks for sending.

    That exception typically means that wp-configure-la-complete has not completed successfully, because it is what creates the "Property Extension repository" that wp-add-property is complaining about.

    In your case though, I can see that wp-configure-la-complete completed successfully and it appears to have created the Property Extension repository:

    [wplc-create-la-repository] Instance attributes (Set 1 of 1):
    [wplc-create-la-repository] JDBCDriverClass="com.microsoft.sqlserver.jdbc.SQLServerDriver"
    [wplc-create-la-repository] attribute=[
    [wplc-create-la-repository] [ dbAdminId="wpsdbusr" ]
    [wplc-create-la-repository] [ dbAdminPassword="PASSWORD_REMOVED" ], ]
    [wplc-create-la-repository] databaseType="sqlserver"
    [wplc-create-la-repository] customproperty=[ *** NONE_SPECIFIED *** ]
    [wplc-create-la-repository] dataSourceName="jdbc/WASvmmladbDS"
    [wplc-create-la-repository] dbURL="jdbc:sqlserver://g-s-c-db01.core.ournet:1434;DatabaseName=prd_VMM"
    [wplc-create-la-repository] ignoreDuplicateIDs= *** NOT_SPECIFIED ***
    [wplc-create-la-repository] entityRetrievalLimit="50"
    [wplc-create-la-repository] trimSpaces= *** NOT_SPECIFIED ***
    Result: [CWWIM5028I The configuration is saved in a temporary workspace. You must use the "$AdminConfig save" command to save it in the master repository.]
    [wplc-create-la-repository] LA repository was created successfully.
    [wplc-create-la-repository] Status = Complete
    Target finished: wp-la-repository

    Although it's strange that it says the configuration is saved in a temporary workspace. I don't have a successful copy around to compare, so I'm not sure if that's normal. In any case, did you do all of the following:

    1. Ensure the dmgr was running at the time the script as executed
    2. Synchronize and restart the dmgr, nodeagent, and Portal servers after the wp-configure-la-complete script completed


    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

  5. Re: CWWIM6109E Property extension repository is not defined

    HT, this worked, i followed your recommendation.

    Synchronize and restarted the dmgr, nodeagent, and Portal servers - then ran the command. It worked.

    thankyou very much.

+ Reply to Thread