Unable to Persistent ConnPool  & DS in config.xml created  dynamically.

Here is my scenario.
I am trying to create JDBCConnectionPools and JDBCDataSources dynamically from a StartupClass. The StartupClass is creating the ConnectionPool and DataSources but it is not persisting it to the config.xml. I tried using setPersistentEnaabled on JDBCConnectionPoolMBean and also used RepositoryMBean to persistent the domain, even then it is not working.
If I run the same code out side the server JVM it is working fine. Creating all JDBCConnectionPools and their associated DataSources and they are all getting persisted to the config.xml.
I want to know whether it is a feature of webloigc server or it is a bug in weblogic server.
My ENV:
Weblogic 8.1 SP3
Windows 2000.
JAVA - jdk142_04(which comes along the weblogic 8.1 SP3)
Thanks -
Siva

Hi,
Pls try application-config tag like this
  <application-config>
    <property name="PrivateSharingReference" value="com.sap.portal.htmlb">
    </property>
    <property name="SharingReference" value="com.sap.portal.runtime.application.soap">
    </property>
  </application-config>
Also check component tag is in this order
<component name="AddAccounts">
      <component-config>
        <property name="ClassName" value="Test">
        </property>
        <property name="JSP" value="pagelet/test.jsp">
        </property>
      </component-config>
      <component-profile>
        <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld">
        </property>
      </component-profile>
    </component>
regards,
Sujesh

Similar Messages

  • Manually edit config.xml

    Hi,
    I'm working with WL 8.1SP3, and I need to add the atribute 'StatementTimeout' to
    'JDBCConnectionPool' entry in config.xml.
    The weblogic console can not do the job, but manually edit config.xml work fine.
    Subsequently when I use WL console to make other changes, the system overwrite any manual previous changes.
    How can I make persistent manual changes in config.xml file?

    On the new machine I am trying to create a new set of servers to be added to the cluster. However I am running into errors, of which various post suggest changing some of the security stuff in the config. But I have not found a way to persist my modifications. Each time I restart it gets overwritten again.
    I am running in production mode, could this be the problem?
    I have tried stopping everything, delete all .lok files on both machines, and restarting everything. On startup the .lok files reappear and my changes are reverted.

  • Command line: Error: unable to open '/Applications/flex_sdk_4\frameworks\flex-config.xml'

    Hi,
    I am new to flex. I am trying to use the xmp sdk to create custom file info panels in photoshop.
    I am going through the example show in the adobe documentation 'Building a panel with Flex SDK'
    I got any running and I got all the files setup in the proper folders but I cannot for the life of me figure out why I keep getting this error.
    Buildfile: /Volumes/three/2011/XMP/test project/build.xml
    clean:
    buildPanel:
         [echo] --> Panel 'Test2'
        [compc] Adobe Compc (Flex Component Compiler)
        [compc] Version 4.5.1 build 21328
        [compc] Copyright (c) 2004-2011 Adobe Systems, Inc. All rights reserved.
        [compc] command line: Error: unable to open '/Applications/flex_sdk_4.5\frameworks\flex-config.xml'
        [compc] Use 'compc -help' for information about using the command line.
    BUILD FAILED
    /Volumes/three/2011/XMP/test project/build.xml:20: compc task failed
    Total time: 616 milliseconds
    thanks,
    digitalkyle

    can you tell us where your services-config.xml file is
    located. can you make sure it is right under the "src" folder of
    the Flex Builder project.
    Hope this helps.

  • Persisting Configuration in Config.xml, Using Administration MBeans

    Dear Friends,
    I am facing a problem on persisting the configuration, using the administration
    Mbeans.
    I am using weblogic 6.1 sp1 version. And i am running weblogic in production mode.
    i have made the AutoDeployEnabled=false in my config.xml file.
    In my program i am setting a target to one my EJB component. But the entry in
    the config.xml is not happening.
    If anyone could help me in this problem, it would be greatful, thanx in advance.
    I am attaching my code with here below.
    import javax.naming.Context;
    import java.util.Set;
    import java.util.Iterator;
    import java.util.Vector;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.WebLogicMBean;
    import weblogic.management.WebLogicObjectName;
    import weblogic.management.runtime.ServerRuntimeMBean;
    import weblogic.management.configuration.ApplicationMBean;
    import weblogic.management.configuration.ServerMBean;
    import weblogic.management.configuration.ComponentMBean;
    import weblogic.management.configuration.RepositoryMBean;
    import weblogic.management.configuration.AdminMBean;
    public class ListAllMbean{
    public static void main(String args[]) {
    String url = "t3://localhost:7001";
    String username = "system";
    String password = "security";
    try {
    //Obtaining an MBeanHome Using JNDI
    Environment env = new Environment();
    env.setProviderUrl(url);
    env.setSecurityPrincipal(username);
    env.setSecurityCredentials(password);
    Context ctx = env.getInitialContext();
    MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    ServerMBean serverMbean = null;
    Set targetMBeans = home.getMBeansByType("Server");
    for (Iterator itr = targetMBeans.iterator(); itr.hasNext(); ) {
    serverMbean = (ServerMBean)itr.next();
    Set allMBeans = home.getMBeansByType("Application");
    for (Iterator itr = allMBeans.iterator(); itr.hasNext(); ) {
    ApplicationMBean application = (ApplicationMBean)itr.next();
    // Getting all the components in the application
    ComponentMBean comp[] = application.getComponents();
    for ( int i = 0; i < comp.length; i++ ) {
    // Setting the target, to deploy the component
    if(comp.getName().equalsIgnoreCase("startup_ejbs_1")){
    comp[i].addTarget(serverMbean);
    // Using the repositaryMBean to persist, not sure this the right way
    RepositoryMBean repositorymbean = (RepositoryMBean)home.getMBean("Default",
    "Repository", "weblogic");
    repositorymbean.saveDomain(home.getActiveDomain().getName()) ;
    }catch(Exception e){
    System.out.println(e);
    Regards,
    Karthickraj.

    Hi Karthik,
    Why don't you post your question at http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.management.general_and_jmx&utag=
    This is a portal server group and a remote chance of getting reply on JMX here.
    Cheers
    Syed
    "Karthikraj" <[email protected]> wrote:
    >
    Dear Friends,
    I am facing a problem on persisting the configuration, using the administration
    Mbeans.
    I am using weblogic 6.1 sp1 version. And i am running weblogic in production
    mode.
    i have made the AutoDeployEnabled=false in my config.xml file.
    In my program i am setting a target to one my EJB component. But the
    entry in
    the config.xml is not happening.
    If anyone could help me in this problem, it would be greatful, thanx
    in advance.
    I am attaching my code with here below.
    import javax.naming.Context;
    import java.util.Set;
    import java.util.Iterator;
    import java.util.Vector;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.WebLogicMBean;
    import weblogic.management.WebLogicObjectName;
    import weblogic.management.runtime.ServerRuntimeMBean;
    import weblogic.management.configuration.ApplicationMBean;
    import weblogic.management.configuration.ServerMBean;
    import weblogic.management.configuration.ComponentMBean;
    import weblogic.management.configuration.RepositoryMBean;
    import weblogic.management.configuration.AdminMBean;
    public class ListAllMbean{
    public static void main(String args[]) {
    String url = "t3://localhost:7001";
    String username = "system";
    String password = "security";
    try {
    //Obtaining an MBeanHome Using JNDI
    Environment env = new Environment();
    env.setProviderUrl(url);
    env.setSecurityPrincipal(username);
    env.setSecurityCredentials(password);
    Context ctx = env.getInitialContext();
    MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    ServerMBean serverMbean = null;
    Set targetMBeans = home.getMBeansByType("Server");
    for (Iterator itr = targetMBeans.iterator(); itr.hasNext();
    serverMbean = (ServerMBean)itr.next();
    Set allMBeans = home.getMBeansByType("Application");
    for (Iterator itr = allMBeans.iterator(); itr.hasNext(); ) {
    ApplicationMBean application = (ApplicationMBean)itr.next();
    // Getting all the components in the application
    ComponentMBean comp[] = application.getComponents();
    for ( int i = 0; i < comp.length; i++ ) {
    // Setting the target, to deploy the component
    if(comp.getName().equalsIgnoreCase("startup_ejbs_1")){
    comp[i].addTarget(serverMbean);
    // Using the repositaryMBean to persist, not sure this the right
    way
    RepositoryMBean repositorymbean = (RepositoryMBean)home.getMBean("Default",
    "Repository", "weblogic");
    repositorymbean.saveDomain(home.getActiveDomain().getName())
    }catch(Exception e){
    System.out.println(e);
    Regards,
    Karthickraj.

  • Flex Compiler API Issue: Error: unable to open './flex-config.xml'

    1) I make a java struts(or a servlet) to build swf file
    dynamically when receiving the request from client. The struts
    source code please see the attached code. deploy the structs to the
    Tomcat
    2) then copy the <Flex_SDK>/frameworks to the
    <tomcat_home>/webapps/dozhang/WEB-INF
    3) then copy the all the libraries under the
    <Flex_SDK>/lib to the
    <tomcat_home>/webapps/dozhang/WEB-INF/lib
    4) Copy a test a.mxml to c:\
    5) Start up Tomcat , access the structs, I will get the
    Error: unable to open './flex-config.xml' in the tomcat log.
    Can anyone tell me how to specify the location of the
    flex-config.xml ?

    Ok, I solved it by myself
    I need to add the following codes when calling the Compiler
    API
    Configuration conf = application.getDefaultConfiguration();
    conf.setToken("flexlib", "path to the frameworks")
    applicaiton.setConfiguration(conf);
    Then it solved the problem

  • Unable to run Cache Factory JVM instance throws Missing POF config xml file

    I have configured three JVM instances in Eclipse using Run Configurations Menu
    - JUnit JVM
    -Default Cache Server JVM
    -Cache Factory JVM
    The configurations of Default Cache Server are
    Main Class : com.tangosol.net.DefaultCacheServer
    Arguments:
    -Dtangosol.coherence.cacheconfig=C:\..\resources\coherence-cache-config.xml
    -Dtangosol.coherence.distributed.localstorage=true
    -Dtangosol.coherence.management=all
    -Dtangosol.coherence.management.remote=true
    The Configurations for CacheFactory are
    Main Class: com.tangosol.net.CacheFactory
    Arguments:
    -Dtangosol.coherence.cacheconfig=C:\..\resources\coherence-cache-config.xml
    -Dtangosol.coherence.distributed.localstorage=false
    First i run Default Cache Server which runs successfully. Then i ran CacheFactory the console messages doesnt say that its refering to coherence-cache-config.xml
    Here is the snippet from console messages
    Oracle Coherence Version 3.5.1/461
    Grid Edition: Development mode
    Copyright (c) 2000, 2009, Oracle and/or its affiliates. All rights reserved.
    2009-10-29 09:57:07.028/5.266 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
    2009-10-29 09:57:07.105/5.343 Oracle Coherence GE 3.5.1/461 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=47
    2009-10-29 09:57:07.105/5.343 Oracle Coherence GE 3.5.1/461 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 19
    2009-10-29 09:57:07.495/5.733 Oracle Coherence GE 3.5.1/461 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Timestamp=2009-10-29 09:57:07.23, Address=165.137.250.122:8089, MachineId=54906, Location=site:cable.comcast.com,machine:PACDCL-CJWWND1b,process:5296, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) joined cluster "cluster:0xD1CB" with senior Member(Id=1, Timestamp=2009-10-29 09:54:18.406, Address=165.137.250.122:8088, MachineId=54906, Location=site:cable.comcast.com,machine:PACDCL-CJWWND1b,process:3236, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1)
    2009-10-29 09:57:07.744/5.982 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=n/a): Member 1 joined Service Management with senior member 1
    2009-10-29 09:57:07.744/5.982 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache with senior member 1
    2009-10-29 09:57:08.414/6.652 Oracle Coherence GE 3.5.1/461 <D5> (thread=Invocation:Management, member=2): Service Management joined the cluster with senior service member 1
    2009-10-29 09:57:09.582/7.820 Oracle Coherence GE 3.5.1/461 <D5> (thread=TcpRingListener, member=2): TcpRing: connecting to member 1 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/165.137.250.122,port=1383,localport=8089]}
    SafeCluster: Name=cluster:0xD1CBPlease note the following messages are missing from the above console messages which are present in Cache Server but not Cache Factory
    Oracle Coherence Version 3.5.1/461
    Grid Edition: Development mode
    Copyright (c) 2000, 2009, Oracle and/or its affiliates. All rights reserved.
    2009-10-29 09:54:17.062/13.141 Oracle Coherence GE 3.5.1/461 <Info> (thread=Main Thread, member=n/a): Loaded cache configuration from "jar:file:/C:/Software/coherence-v3.5.1b461/coherence/lib/coherence.jar!/reports/report-group.xml"
    2009-10-29 09:54:17.234/13.313 Oracle Coherence GE 3.5.1/461 <Info> (thread=Main Thread, member=n/a): Loaded cache configuration from "file:/C:/MyWorkspaces/EnterpriseServicesPlatform/ContractService/ServiceImpl/src/main/resources/coherence-cache-config.xml"

    The CacheFactory will not load the cache configuration until you use a cache related command the first time. For example:
    Map (?): cache test
    2009-10-30 09:18:47.847/8.164 Oracle Coherence GE 3.5/459 <Info> (thread=main, member=1): Loaded cache configuration from file "/Users/rob.misek/temp/new-cache-config.xml"
    <class-scheme>
    <scheme-name>default-backing-map</scheme-name>
    <class-name>com.tangosol.util.SafeHashMap</class-name>
    </class-scheme>
    Rob
    :Coherence Team:

  • Unable to read facec-config.xml in META-INF folder of webui-jsf.jar

    Hi
    I was getting following error when I placed webui-jsf.jar file in websphere 6.0 server
    /WEB-INF/lib/jsf-extensions-dynamic-faces-0.1.jar!/META-INF/faces-config.xml
    Digester E org.apache.commons.digester.Digester error Parse Error at line 24 column 14: Document is invalid: no grammar found.
    org.xml.sax.SAXParseException: Document is invalid: no grammar found.
    Do I need to add any other parser to read this file ?
    Thanks
    Himaja

    Your classpath is polluted with different JSF implementations/versions. Clean it up.

  • Oim-config.xml was not found in MDS Repository.

    Hi there,
    I'm trying to install Oracle Fusion Application (last version .5) but I can't go ahead becuase I got an error during the OIM Server installation.
    $ uname -a
    Linux server02 2.6.39-200.24.1.el6uek.x86_64 #1 SMP Sat Jun 23 02:39:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
    $ cd /repository/fusion/fmw/iam/bin/
    $ ./config.sh &
    Select only “OIM Server” [...] everything is going fine without error. I've re-started the AdminServer and started the OIM.
    If I try to open the browser http://<server>:14000 I got an Error 404
    Take a look at the log, there is an Error on oim-config.xml
    I was trying to find something on Google but all the forum talked about the missing security files.
    I tried to install again OIM but nothing happened.
    Someone could help me please?
    Thanks and best regards,
    Lain
    $ tail -f /repository/fusion/fmw//admin/IDMDomain/mserver/IDMDomain/servers/wls_oim1/logs/wls_oim1.log
    ####<Jan 30, 2013 1:24:15 AM CET> <Error> <Deployer> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66
    ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455419> <BEA-149205> <Failed to initialize the application 'oim [Version=11.1.1.3.0]' due to error oracle.iam.platform.uti
    ls.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    oim-config.xml was not found in MDS Repository.
    oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    oim-config.xml was not found in MDS Repository.
            at oracle.iam.platform.utils.OIMAppInitializationListener.preStart(OIMAppInitializationListener.java:145)
            at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
            at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
            at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
            at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    oim-config.xml was not found in MDS Repository.
           at oracle.iam.platform.utils.OIMAppInitializationListener.preStart(OIMAppInitializationListener.java:145)
            at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
            at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
            at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
            at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    ####<Jan 30, 2013 1:24:15 AM CET> <Warning> <Munger> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455586> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in /repository/fusion/fmw/iam/server/apps/spml-xsd.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    ####<Jan 30, 2013 1:24:15 AM CET> <Warning> <Munger> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455702> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in /repository/fusion/fmw/admin/IDMDomain/mserver/IDMDomain/servers/wls_oim1/tmp/_WL_user/spml-xsd/ahejq0/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    ####<Jan 30, 2013 1:24:15 AM CET> <Info> <WorkManager> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455706> <BEA-002903> <Creating WorkManager from "OIMUIWorkManager" WorkManagerMBean for application "spml-xsd">
    ####<Jan 30, 2013 1:24:15 AM CET> <Info> <WorkManager> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455706> <BEA-002903> <Creating WorkManager from "OIMMDBWorkManager" WorkManagerMBean for application "spml-xsd">
    ####<Jan 30, 2013 1:24:15 AM CET> <Info> <Deployer> <server02> <wls_oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <aa66ef4907f1903f:-58c6bc2b:13c88d5b7cb:-8000-0000000000000003> <1359505455718> <BEA-149059> <Module spml-xsd of application spml-xsd is transitioning from STATE_NEW to STATE_PREPARED on server wls_oim1.>

    Thanks for your support Rajiv Dewan and idamGod,
    I've just followed this metalink ID: “Easy step for Oracle Identity Manager 11g (OIM 11g) installation on Windows [ID 1234357.1]”
    In my case I don’t have this error:
    Unable to find keystore "default-keystore.jks" in <DOMAIN_HOME>/config/fmwconfig/.
    Unable to find keystore ".xldatabasekey" in <DOMAIN_HOME>/config/fmwconfig/.
    […]Maybe it’s the same root causes but I installed again the OIM without success. I can’t login to the OIM because I just back 404.
    I’m sorry but I didn’t understand what I can do.
    Thanks,
    Lain

  • How to configure CustomLoginModule in jps-config.xml

    Hi,
    How can we configure a Custom Login Module using jps-config.xml, as we do not want to use weblogic custom authentication provider as it needs application jars(which we require fo authenticating the user) to be kept in weblogic classpath.
    Is there any documentation on how to configure and use Custom Login Modules in jps-config.xml, I tried to create a LoginModule and specify it in jps-config.xml, but
    My LoginModule is not getting called.
    Jdev version: 11.1.1.3.0
    Server : weblogic
    my jps-config.xml is
                  <?xml version = '1.0' encoding = 'Cp1252'?>
    <jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd">
       <property value="doasprivileged" name="oracle.security.jps.jaas.mode"/>
       <property value="custom.provider" name="true"/>
       <propertySets/>
       <serviceProviders>
          <serviceProvider class="oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider" name="credstore.provider" type="CREDENTIAL_STORE">
             <description>Credential Store Service Provider</description>
          </serviceProvider>
          <serviceProvider class="oracle.security.jps.internal.login.jaas.JaasLoginServiceProvider" name="jaas.login.provider" type="LOGIN">
             <description>
                Login Module Service Provider
             </description>
          </serviceProvider>
          <serviceProvider class="oracle.security.jps.internal.idstore.xml.XmlIdentityStoreProvider" name="idstore.xml.provider" type="IDENTITY_STORE">
             <description>XML-based IdStore Provider</description>
          </serviceProvider>
          <serviceProvider class="oracle.security.jps.internal.policystore.xml.XmlPolicyStoreProvider" name="policystore.xml.provider" type="POLICY_STORE">
             <description>XML-based PolicyStore Provider</description>
          </serviceProvider>
       </serviceProviders>
       <serviceInstances>
          <serviceInstance provider="credstore.provider" name="credstore">
             <property value="./" name="location"/>
          </serviceInstance>
          <serviceInstance provider="jaas.login.provider" name="CustomLoginModule">
             <property value="SUFFICIENT" name="jaas.login.controlFlag"/>
             <property value="SEVERE" name="log.level"/>
             <property value="org.calwin.view.CustomLoginModule" name="loginModuleClassName"/>
          </serviceInstance>
          <serviceInstance provider="idstore.xml.provider" name="idstore.xml">
             <property value="./jazn-data.xml" name="location"/>
             <property value="OBFUSCATE" name="jps.xml.idstore.pwd.encoding"/>
             <property value="jps" name="subscriber.name"/>
          </serviceInstance>
          <serviceInstance provider="policystore.xml.provider" name="policystore.xml">
             <property value="./jazn-data.xml" name="location"/>
          </serviceInstance>
       </serviceInstances>
       <jpsContexts default="TestMultiDatasource">
          <jpsContext name="TestMultiDatasource">
             <serviceInstanceRef ref="idstore.xml"/>
             <serviceInstanceRef ref="credstore"/>
             <serviceInstanceRef ref="policystore.xml"/>
          </jpsContext>
          <jpsContext name="anonymous">
             <serviceInstanceRef ref="credstore"/>
          </jpsContext>
       </jpsContexts>
    </jpsConfig>My Login Module Class:
    package org.calwin.view;
    import java.io.IOException;
    import java.security.Principal;
    import java.util.Map;
    import javax.security.auth.Subject;
    import javax.security.auth.callback.Callback;
    import javax.security.auth.callback.CallbackHandler;
    import javax.security.auth.callback.NameCallback;
    import javax.security.auth.callback.PasswordCallback;
    import javax.security.auth.callback.UnsupportedCallbackException;
    import javax.security.auth.login.LoginException;
    import javax.security.auth.spi.LoginModule;
    import javax.servlet.http.HttpServletRequest;
    import weblogic.security.auth.callback.ContextHandlerCallback;
    import weblogic.security.principal.WLSUserImpl;
    import weblogic.security.service.ContextHandler;
    public class CustomLoginModule
        implements LoginModule
      // initial state
      private Subject subject;
      private CallbackHandler callbackHandler;
      // the authentication status
      private boolean succeeded = false;
      private boolean commitSucceeded = false;
      // username and password
      private String username;
      private String password;
      // testUser's SamplePrincipal
      private Principal userPrincipal;
       * Initialize this <code>LoginModule</code>.
       * <p>
       * @param subject the <code>Subject</code> to be authenticated. <p>
       * @param callbackHandler a <code>CallbackHandler</code> for communicating
       *      with the end user (prompting for user names and
       *      passwords, for example). <p>
       * @param sharedState shared <code>LoginModule</code> state. <p>
       * @param options options specified in the login
       *      <code>Configuration</code> for this particular
       *      <code>LoginModule</code>.
      public void initialize(Subject subject, CallbackHandler callbackHandler,
                             Map sharedState, Map options) {
        this.subject = subject;
        this.callbackHandler = callbackHandler;
       * Authenticate the user by prompting for a user name and password.
       * <p>
       * @return true in all cases since this <code>LoginModule</code>
       *    should not be ignored.
       * @exception FailedLoginException if the authentication fails. <p>
       * @exception LoginException if this <code>LoginModule</code>
       *    is unable to perform the authentication.
      public boolean login() throws LoginException {
        if (callbackHandler == null)
          throw new LoginException("Error: no CallbackHandler available " +
                                   "to garner authentication information from the user");
        Callback[] callbacks = new Callback[3];
        callbacks[0] = new NameCallback("user name: ");
        callbacks[1] = new PasswordCallback("password: ", false);
        callbacks[2]=new ContextHandlerCallback();
          try {
            callbackHandler.handle(callbacks);
          } catch (UnsupportedCallbackException uce) {
              throw new LoginException("Callback Not Supported");
          } catch (IOException ioe) {
              throw new LoginException("I/O Failed");
          username = ((NameCallback)callbacks[0]).getName();
          char[] tmpPassword = ((PasswordCallback)callbacks[1]).getPassword();
          if (tmpPassword == null) {
            tmpPassword = new char[0];
          password = new String(tmpPassword);
          ((PasswordCallback)callbacks[1]).clearPassword();
        // verify the username/password
        boolean usernameCorrect = true;
        boolean passwordCorrect = true;
        succeeded = true;
        return true;
       * <p> This method is called if the LoginContext's
       * overall authentication succeeded
       * (the relevant REQUIRED, REQUISITE, SUFFICIENT and OPTIONAL LoginModules
       * succeeded).
       * <p> If this LoginModule's own authentication attempt
       * succeeded (checked by retrieving the private state saved by the
       * <code>login</code> method), then this method associates a
       * <code>SamplePrincipal</code>
       * with the <code>Subject</code> located in the
       * <code>LoginModule</code>.  If this LoginModule's own
       * authentication attempted failed, then this method removes
       * any state that was originally saved.
       * <p>
       * @exception LoginException if the commit fails.
       * @return true if this LoginModule's own login and commit
       *    attempts succeeded, or false otherwise.
      public boolean commit() throws LoginException {
        if (succeeded == false) {
          return false;
        } else {
          userPrincipal = new WLSUserImpl(username);
          if (!subject.getPrincipals().contains(userPrincipal))
            subject.getPrincipals().add(userPrincipal);
          // in any case, clean out state
          username = null;
          password = null;
          commitSucceeded = true;
          return true;
       * <p> This method is called if the LoginContext's
       * overall authentication failed.
       * (the relevant REQUIRED, REQUISITE, SUFFICIENT and OPTIONAL LoginModules
       * did not succeed).
       * <p> If this LoginModule's own authentication attempt
       * succeeded (checked by retrieving the private state saved by the
       * <code>login</code> and <code>commit</code> methods),
       * then this method cleans up any state that was originally saved.
       * <p>
       * @exception LoginException if the abort fails.
       * @return false if this LoginModule's own login and/or commit attempts
       *    failed, and true otherwise.
      public boolean abort() throws LoginException {
        if (succeeded == false) {
          return false;
        } else if (succeeded == true && commitSucceeded == false) {
          // login succeeded but overall authentication failed
          succeeded = false;
          username = null;
          if (password != null) {
            password = null;
          userPrincipal = null;
        } else {
          // overall authentication succeeded and commit succeeded,
          // but someone else's commit failed
          logout();
        return true;
       * Logout the user.
       * <p> This method removes the <code>SamplePrincipal</code>
       * that was added by the <code>commit</code> method.
       * <p>
       * @exception LoginException if the logout fails.
       * @return true in all cases since this <code>LoginModule</code>
       *          should not be ignored.
      public boolean logout() throws LoginException {
        subject.getPrincipals().remove(userPrincipal);
        succeeded = false;
        succeeded = commitSucceeded;
        username = null;
        if (password != null) {
          password = null;
        userPrincipal = null;
        return true;
    }My adf-config.xml:
    <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
        <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
                                credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
        <sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
                                 jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
                                 authorizationEnforce="true"
                                 authenticationRequire="true"/>
      </sec:adf-security-child>My jazn.xml:
    <?xml version = '1.0' encoding = 'UTF-8' standalone = 'yes'?>
    <jazn-data xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/jazn-data-11_0.xsd">
      <jazn-realm default="jazn.com">
        <realm>
          <name>jazn.com</name>
        </realm>
      </jazn-realm>
    </jazn-data>My web.xml:
    <filter>
        <filter-name>JpsFilter</filter-name>
        <filter-class>oracle.security.jps.ee.http.JpsFilter</filter-class>
        <init-param>
          <param-name>enable.anonymous</param-name>
          <param-value>true</param-value>
        </init-param>
        <init-param>
          <param-name>remove.anonymous.role</param-name>
          <param-value>false</param-value>
        </init-param>
      </filter>
    <servlet>
        <servlet-name>adfAuthentication</servlet-name>
        <servlet-class>oracle.adf.share.security.authentication.AuthenticationServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
      </servlet>
    <servlet-mapping>
        <servlet-name>adfAuthentication</servlet-name>
        <url-pattern>/adfAuthentication</url-pattern>
      </servlet-mapping>
    <security-constraint>
        <web-resource-collection>
          <web-resource-name>adfAuthentication</web-resource-name>
          <url-pattern>/adfAuthentication</url-pattern>
        </web-resource-collection>
        <auth-constraint>
          <role-name>valid-users</role-name>
        </auth-constraint>
      </security-constraint>
      <login-config>
        <auth-method>FORM</auth-method>
        <form-login-config>
          <form-login-page>/login.html</form-login-page>
          <form-error-page>/error.html</form-error-page>
        </form-login-config>
      </login-config>
      <security-role>
        <role-name>valid-users</role-name>
      </security-role>weblogic.xml:
      <security-role-assignment>
        <role-name>valid-users</role-name>
        <principal-name>users</principal-name>
      </security-role-assignment>Regards,
    Saikiran

    Ours is not a Desktop Application, but we want to handle Authentication(Which authenticates the userid and password by making a Tuxedo call) and add the Principal to Subject in session, so that ADF Authorization and securityContext can be used as is,
    but doing this with Custom Authentication Provider in weblogic needs me to have a lot of Tuxedo Service related jars in weblogic/system classpath which i feel is not right thing to do, as the same jars are required in application also, which means i will have the jars in class path twice and i need to deploy the jars to both places everytime there is any change.
    Is there any way by which i can set Authenticated principal to Subject in the created session from within Application?

  • Scenario-config.xml file not found in CRM system

    Hi All,
    We are on SAP CRM 5.0 SP 12 (Java + ABAP stack) for our eCommerce Scenario (ISA u2013 B2B).
    Currently we are facing an issue where login to XCM (Extended Configuration Management) & the CRM B2B Webshop is giving an error.
    Error message : ISA Framework: No XCM application configuration has been passed and there is no default XCM application configuration defined. Check XCM configuration
    We are unable to login to the XCM as well for any further configuration.
    The root cause we found is that the scenario-config.xml is not there in the root/WEB-INF/xcm/sap/configuration folder.
    Can you please let me know how to get these files deployed. Can it be done thru the local NWDS or do we have to deploy some standard application?
    Thanks in advance lot for your inputs
    Rajeet

    Hi Ecommerce Developer,
    Thanks again for your prompt response.
    Please find below my answers to your questions:
    1 Have you first imported SCA files in Track and then deploy it on your Dev System?
    A)Yes, we imported the SCAs first, deployed in the track to the dev system then
    2 Have your developer has any open activity on their Local NWDS?
    I am checking that with the developers. Incase they are some, they will delete it asap. Also, when they are trying to release any open activity, theya re getting that xcm error as reported earlier. So, they are deleting the same.
    A) After deleting should i check in all the 3 standard components again to the Dev track {not to the consolidation track?}?
    3 I think you have imported SCA files in your eCommerce Developer track and then your developer sync. their code through NWDS and overright their changes and when they deploy it on Their Local or on Development Server Developer lost some of their customization. Is it right?
    A) Yes, absolutely right after the developers synced, they lost lots of customzing things and were able to see a mixed
    4 As you have written developer can see their code, where they can see their code on Local NWDS or in DTR Version History?
    A) They can see there code on there local NWDS system.
    5 Look and feel changed on Developer's local system and Development box or only on Developer Box?
    A) As I said, after the developers synced, they are able to see mixed hybrid webshop. This hybrid webshop has most of the custom code but the look and feel, the graphics, the images and all are missing.
    Also, one strange thing which we have noticed is.
    We had an old ear fille. When we deploy that ear file directly via sdm, the crm webshop on the dev box works fine.
    But when release the same activity from nwds and then deploy via NWDI to the same crm webshop on the dev box, i get the run time error? Why is this happening?
    Thanks again for your feedback.
    Eagerly awaiting your response.
    Regards,
    Rajeet
    +41 76 525 0440

  • OIM 11g installation: oim-config.xml was not found in MDS Repository

    Hi,
    I just installed Oracle Identity Manager 11g (the latest version) on out test system. The installation worked fine. I can start the admin server as well as the soa_server. But when I start the oim_server1, the deployment of oim fails with the following error message:
    ####<Aug 18, 2010 3:33:22 PM CEST> <Error> <Deployer> <oim11g> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1282138402834> <BEA-149205> <Failed to initialize the application 'oim [Version=11.1.1.3.0]' due to error oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    oim-config.xml was not found in MDS Repository.
    Unable to find keystore "default-keystore.jks" in <DOMAIN_HOME>/config/fmwconfig/.
    Unable to find keystore ".xldatabasekey" in <DOMAIN_HOME>/config/fmwconfig/.
    Password for OIMSchemaPassword is not seeded in CSF.
    Password for xell is not seeded in CSF.
    Password for DataBaseKey is not seeded in CSF.
    Password for JMSKey is not seeded in CSF.
    Password for .xldatabasekey is not seeded in CSF.
    Password for default-keystore.jks is not seeded in CSF.
    Password for SOAAdminPassword is not seeded in CSF.
    oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    oim-config.xml was not found in MDS Repository.
    Unable to find keystore "default-keystore.jks" in <DOMAIN_HOME>/config/fmwconfig/.
    Unable to find keystore ".xldatabasekey" in <DOMAIN_HOME>/config/fmwconfig/.
    Password for OIMSchemaPassword is not seeded in CSF.
    Password for xell is not seeded in CSF.
    Password for DataBaseKey is not seeded in CSF.
    Password for JMSKey is not seeded in CSF.
    Password for .xldatabasekey is not seeded in CSF.
    Password for default-keystore.jks is not seeded in CSF.
    Password for SOAAdminPassword is not seeded in CSF.
         at oracle.iam.platform.utils.OIMAppInitializationListener.preStart(OIMAppInitializationListener.java:145)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    Has anybody seen this error before or knows how to fix it? Thanks for your help in advance!
    Best regards
    Tom

    This also solved my issue. If you can backup the .xldatabasekey file before you reinstall this will allow the OIM application to read the OIM database. I was successfully able to run rm -Rf and wipe my entire Middleware directory. Then I reinstalled ALL of OIM and SOA back to the same VM. I saved the .xldatabasekey file before hand and dropped it right back to the same folder before I ran the rm -Rf command later after the OIM Domain was installed. Finally, as mentioned above, I logged into EM and found that I needed to add the .xldatabasekey "password" and simply used the same password that I entered during the OIM configure steps for the keystore. Remember the .xldatabasekey password IS NOT the xelsysadm password, but the KEYSTORE password. They are different. I am now able to log into OIM and I can see all the pre-existing users. Thanks for the help!

  • Updating defaultTimeout in adf-config.xml through WLST

    Hello,
    I hope i have this in the right area. I'm cross posting because I think I put it in the wrong place originally. If I get an answer, I'll cross link the two.
    I'm trying to change the default, min and maximum timeouts for portlets that come from our WSRP portlet producing application. The documentation I found on the time outs says to edit adf-config.xml 1 and when editing the adf-config.xml do that via WLST ^2^.
    1) portlet time out: [http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC|http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC]
    <adf-portlet-config>
    <defaultTimeout>5</defaultTimeout>
    <minimumTimeout>2</minimumTimeout>
    <maximumTimeout>100</maximumTimeout>
    <adf-portlet-config>
    2) editing adf-config.xml: [http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019|http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019]
    I can not find the MBean in the bean browser that seems to hold this setting.
    There is a bit of a conflicting message in the docs though. "If you must modify these properties, post deployment, you must edit adf-config.xml manually." But the doc that describes editing adf-config.xml says that using WLST are
    So... Questions:
    1) Are these three elements (defaultTimeout, minimumTimeout, and maximumTimeout) some exception to being set from WLST?
    2) If not, what is the MBean I should find this setting in?
    Thank you very much,
    Marc
    Edited by: MarcDavenport on Jun 26, 2012 12:37 PM

    Marc,
    This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
    http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
    This section of the doc seems to walk through an example setting properties in adf-config.xml
    I would interpret those instructions in the official doc to mean :
    1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
    2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
    (This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
    Now comes the conflicting parts :
    "If you must modify these properties, post deployment, you must edit adf-config.xml manually."
    I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
    Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
    So if we :
    set the timeout to 1 minute initially at design time,
    then change that to 5 minutes through WLST,
    and then edit adf-config again in Jdev to a 10 minute value and redeploy,
    the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
    MDS documents are always applied on top of the deployed stuff.
    The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
    does make a good explanation of how the changes persisted in MDS affects the final configuration.
    Hop that helps !

  • Can't setup PofAnnotationSerializer in pof-config.xml

    Hi,
    i have class annotated with @Portable and @PortableProperty, and pof-config.xml for setup serializer:
          <user-type>
             <type-id>1001</type-id>
             <class-name>entity.dto.base.EmployeeBaseDTO</class-name>
             <serializer>
                <class-name>com.tangosol.io.pof.PofAnnotationSerializer</class-name>
                    <init-params>
                    <init-param>
                        <param-type>int</param-type>
                        <param-value>1001</param-value>
                     </init-param>
                     <init-param>
                        <param-type>java.lang.Class</param-type>
                        <param-value>entity.dto.base.EmployeeBaseDTO</param-value>
                     </init-param>
                  </init-params>
             </serializer>
          </user-type>
    While starting Coherence 3.7.1 cluster, I get error:
    Unable to instantiate PofSerializer class: com.tangosol.io.pof.PofAnnotationSerializer (Config=...\pof-config.xml, Type-Id=1001,
    Class-Name=entity.dto.base.EmployeeBaseDTO))
    java.lang.InstantiationException: Could not find a constructor for com.tangosol.io.pof.PofAnnotationSerializer(java.lang.Integer, com.tangosol.run.xml.SimpleElement)
    Why second PofAnnotationSerializer contructor parameter is com.tangosol.run.xml.SimpleElement and not java.lang.Class ?
    BTW setup PofAnnotationSerializer programatically works fine:
    SimplePofContext pofCtx = new SimplePofContext();
    int typeId = 1001;
    pofCtx.registerUserType(typeId, EmployeeBaseDTO.class , new PofAnnotationSerializer<EmployeeBaseDTO>(typeId++, EmployeeBaseDTO.class, true));
    Thanks,
    L.V.

    OK, so to enable auto indexing then yes, you need to specify the serializer in the POF configuration, as it says in the documentation 19.3.3 Enabling Automatic Indexing.
    So in your case the configuration should look like this
          <user-type>
             <type-id>1001</type-id>
             <class-name>entity.dto.base.EmployeeBaseDTO</class-name>
             <serializer>
                <class-name>com.tangosol.io.pof.PofAnnotationSerializer</class-name>
                    <init-params>
                    <init-param>
                        <param-type>int</param-type>
                        <param-value>{type-id}</param-value>
                     </init-param>
                     <init-param>
                        <param-type>class</param-type>
                        <param-value>{class}</param-value>
                     </init-param>
                     <init-param>
                        <param-type>boolean</param-type>
                        <param-value>true</param-value>
                     </init-param>
                  </init-params>
             </serializer>
          </user-type>
    You do not replace the param-values that are inside { } or change the param-type values as these are macros that Coherence will automatically replace with the correct values.
    Regarding your error, I'm not sure if that is related to your original question/issue.
    JK

  • What is the rule for adding application elements to faces-config.xml

    I have posed this question before, but was unable to get an answer so here goes again.
    What is the rule for adding more than one application element to the faces-config.xml?
    The schema documents that 1-n are possible, but why and when should I do this?
    --W                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    sorry if you don't login in tomcat administration before. you must enter login and password of a manager user on tomcat .
    The user is the one you give when installing tomcat.
    If you have forgotten it : see it to: C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\tomcat_users.xml
    and choose one whop have role='manager'

  • Possible to add and persist elements in server config, for use by cons ext?

    I'm considering what will be my obstacles if I try to write a console extension that we would use to view excerpts of an application log file, the application of which is deployed to each server in our domain(s). It doesn't log to the WebLogic server log, it writes it to an external log file (through log4j), and each server (several servers on each box) uses a slightly different path to its log file.
    One issue that I'll have is getting the console extension to know what the path to the log file is. I think the best way, over all, is just to have the user enter the path in the form presented by the console extension. My problem is how to persist that setting, because I'd prefer they didn't have to enter that every time they entered the form.
    Several years ago, I wrote a console extension for WL 8.1.4 which had a similar issue. I ended up simply writing the setting into a properties file inside the extension WAR. This only works (I believe) if the WAR is deployed exploded. I could do that, but I don't like that idea very much.
    What would be nice is if I could "extend" the server config.xml with an additional element in the "Server" element, where I could store this information. Unfortunately, I don't see any support for doing something like that.
    Another alternative I'm considering is whether it's possible to extend the "Summary of Log Files" page in "Diagnostics" with an application-specific log file, but I don't see any way to do that.

    Well, I appreciate the suggestion, but it's not exactly a secret, to me at least. I've used it for human-readable things recently. It occurred to me that that might be my only option, but I certainly wasn't going to assume that. As it seems like this is likely my only option, I guess I can see some interesting conventions for dealing with this. You have to assume that the field could be written to by other code, and that code would have to make the same assumption. I guess I'd have to define a certain XML element as the root of my structure. If I find it, that region between the start and end element is mine to use and modify. If I don't find it, I'll insert my element at the end of the field value.

Maybe you are looking for