JDK Logging configuration

Hi ,
trying to configure logging for an EAR application.
Environment:
============
Oracle fustion middlware 11g (Weblogic 10.3)
OS: 64bit RH linux
Deployment target for the application is the AdminServer in the ECM domain. This domain constains the managed server UCM_server1 and IBR_server1.
WL Startup params for logging:
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
-Djava.util.logging.config.file=/opt/oracle/middleware/user_projects/domains/ecm_domain/logging.properties
admin console settings:
==============================
Environment->Servers->AdminServer->Logging the logging implementation is set to JDK
logging.properties
==================
handlers=weblogic.logging.ServerLoggingHandler,java.util.logging.FileHandler
.level=INFO
#default file output is in user's home directory.
java.util.logging.FileHandler.pattern = /opt/oracle/middleware/user_projects/domains/ecm_domain/cust.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
# Limit the message that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
weblogic.logging.ServerLoggingHandler.level=FINE
# set 3rd party libs to SEVERE
org.apache.commons.level=SEVERE
org.apache.commons.httpclient.level=SEVERE
httpclient.wire.level=SEVERE
org.apache.struts2.level=SEVERE
# com.opensymphony.level=SEVERE
com.opensymphony.level=SEVERE
org.apache.tiles.level=SEVERE
org.apache.axis.level=SEVERE
org.apache.tiles.level=SEVERE
freemark.level=SEVERE
com.<our own package>.level=FINE
com.<our other package>.level=INFO
jar file setup: (according to doc http://download.oracle.com/docs/cd/E14571_01/web.1111/e13739/config_logs.htm#i1015532)
===============
placed
com.bea.core.apache.commons.logging_1.1.0.jar (found this file in modules, although the docs say wl does not ship these . . . )
com.bea.core.weblogic.commons.logging_1.4.0.0.jar (the documentation specified 1.3.0.0 but i couldn't find that one)
checked that the wlcommons-logging.jar exists in /opt/oracle/middleware/wlserver_10.3/server/lib
The deployment unit is a standard EAR file with WEB and EJB modules. Packages within APP-INF/lib and WEB-INF/lib
are various thirdparty jars (commons, struts, tiles etc.)
Unfortunately, I don't see any of the FINE (commons.Logger.debug) messages. All messages from the 3rd party packages seem to be ignored, when the severity levels were set to INFO, FINE etc.
What am i missing something in the configuration ? Are the messages (debug,info, 3rd party messages) written to another logfile ? I've checked
the console, the AdminServer.log and the cust.log files.
thanks
Michael

Hi,
i gave up on jdk logging and attepted log4j.
Found an interesting article: http://www.theserverlabs.com/blog/2010/04/22/dynamically-changing-log-level-with-weblogic-log4j-jmx-and-wlst/
and forcing JCL and log4j to read from the app classpath worked.
in the weblogic-application.xml
     <wls:prefer-application-packages>
<wls:package-name>org.apache.commons.logging.*</wls:package-name>
          <wls:package-name>org.apache.log4j.*</wls:package-name>
     </wls:prefer-application-packages>
basically this works (haven't tried the dynamic changing of loglevels). But this led to further problems.
I'm using struts2 (2.2.1) with tiles (2.0.6) plus various other 3rd party libraries. One of these libs depends on an XML implementation (xerces). When deploying with the above configuration deployment failed when the tiles container tried to initialise the definitions while reading the tiles.xml file. The problem was that it was loading the xercesImpl.jar shipped for one of the 3rd party apps.
Removing xercesImpl.ja from APP-INF/lib fixed that problem but caused the 3rd party app to fail. Upgrading the xercesImpl caused the deployment to fail (stacktrace below)
I guess i'm delving into the reamlms of classloading within weblogic. What i don't quite understand yet is if the packages org.apache.commons, and log4j where specified as those to be preferred from the local classpath why would that effect the loading of the XML parser ?
I would have thought that the instructiosn above mean 'only prefer those packages from the APP-INF/lib dir' ...
any help in this matter would be greatly appreciated.
thanks,
Michael
weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:188)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
     Truncated. see log file for complete stacktrace
Caused By: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:69)
     at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
     at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:111)
     Truncated. see log file for complete stacktrace
>
<09.05.2011 10:17 Uhr MESZ> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1304929068317' for task '0'. Error is: 'weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered'
weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:188)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
     Truncated. see log file for complete stacktrace
Caused By: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:69)
     at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
     at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:111)

Similar Messages

  • How to configure WL 10.3 to used log4j instead of jdk logging

    Hi,
    How can I configure WL 10.3 to use log4j instead of jdk default logging. I did changed the logging to log4j through the console for the AdminServer and one of the Managed Instance. I try to deploy axis2.war but it fails and complains about apache logger class not found. So wondering what other settings do I need. I even copied log4j-1.2.15.jar & wllog4j.jar in WL_DOMIAN\lib and restaretd the server but still gets the following error is
    'weblogic.application.ModuleException: [HTTP:101216]Servlet: "AxisServlet" failed to preload on startup in Web application: "axis".
    java.lang.ExceptionInInitializerError
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.servlet.internal.WebComponentContributor.getNewInstance(WebComponentContributor.java:223)
         at weblogic.servlet.internal.WebComponentContributor.createServletInstance(WebComponentContributor.java:247)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:255)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1913)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1887)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1805)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3041)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1374)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:452)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:629)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:206)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:40)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger))
         at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
         at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
         at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
         at org.apache.axis2.transport.http.AxisServlet.<clinit>(AxisServlet.java:83)
         ... 50 more
    Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger)
         at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413)
         at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
         ... 54 more
    Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
         at java.lang.Class.getDeclaredConstructors0(Native Method)
         at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
         at java.lang.Class.getConstructor0(Class.java:2699)
         at java.lang.Class.getConstructor(Class.java:1657)
         at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410)
         ... 55 moreThanks

    Go to Environments >> servers>> adminServer >> logging >> advanced
    change the default JDK logging to log4j
    by default weblogic provides two types of logging JDK and log4j

  • Configure JDK logging per EAR

    I try to find out how to configure the JDK logging for one application (EAR). You can't initialize it your own because you don't have a main method or something similar. Is there any configuration option to set environment settings for an application, or how to configure logging for one application.

    Hi Jan,
    thanks for your answer. I've already read these, but I can't exactly see how it helps me, so I redefine my needs:
    - the application already has some logging implemented (using various log levels),
    - I don't have admin access to the target OC4J(s),
    - I'd like to define default logging levels per package, so that after deployment no configuration will be needed.
    Is it possible, e.g. by packaging j2ee-logging.xml into the EAR? (I've already tried that without success.)
    Thanks,
    Patrik

  • Can not find Save botton in log configure.

    Hi,
    I want to change the log severity level from some application. I went to log configuration and I clicked the button for "change on selected node". However, I could not find any "Save" or "Apply" button. When I exit the page, system showed me "you will lost the unsaved data". Does anybody know how to save it? Thank you.

    Hi,
    Which SP level you are on? If you are on NW04 SPS12 or NW04s SPS02 or below upgrade that to NW04 SP 13 of the J2EE Engine 6.40 or NW04s SPS 03 of the J2EE Engine 6.40s or higher level.
    If it is not possible due to any reason apply sap.com_tclmwebadminlog_configwd.sda
    by following  the note 656711.
    Reward points for useful answers
    Regards,
    Phani

  • How to log to a file using the log-configuration.xml?

    Hello *,
    I created following log-configuration.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
    <log-configuration>
         <log-formatters>
              <log-formatter name="DefaultFormatter" pattern="%25d %-60l %s: %m" type="TraceFormatter"/>
         </log-formatters>
         <log-destinations>
              <log-destination count="10" effective-severity="ALL" limit="1000000" name="DefaultDestination" pattern="FDLB_GUI.%g.trc" type="FileLog">
                   <formatter-ref name="DefaultFormatter"/>
              </log-destination>
         </log-destinations>
         <log-controllers>
              <log-controller effective-severity="ALL" maximum-severity="FATAL" minimum-severity="DEBUG" name="DefaultController">
                   <associated-destinations>
                        <destination-ref association-type="LOG" name="DefaultDestination"/>
                   </associated-destinations>
              </log-controller>
         </log-controllers>
    </log-configuration>
    From a Web Dynpro view I want to use the log-controller. I'm using the default logger:
    Logging location.
      private static final com.sap.tc.logging.Location logger =
        com.sap.tc.logging.Location.getLocation(EinstiegView.class);
    In the wdInit method I want to log a simple message:
      public void wdDoInit()
        //@@begin wdDoInit()
        logger.setEffectiveSeverity(com.sap.tc.logging.Severity.ALL);
        logger.fatalT("test logging to new file logger");
        //@@end wdDoInit()
    I see the message in the defaultTrace.0.log, but my own log file doesn't appear.
    How to address the log-controller of my log-configuration.xml?
    Thanks in advance,
    Jürgen Dufner

    Hi,
    I guess the follwing part of your log-configuration is wrong:
    <log-controller
    effective-severity="ALL"
    maximum-severity="FATAL" m
    nimum-severity="DEBUG"
    name="DefaultController">
    Try to change in log-configuration the value for name in <log-controller> to the start sequence of the packages to be logged. E.g., all our packages should start with com.yourcompanyname.projectname
    To log all messages from classes in these packages make the name = com.yourcompanyname.projectname.
    Hope that helps,
    Regards, Astrid
    Therefore I list

  • Java.lang.NoClassDefFoundError: com/sap/tc/logging/Configurator

    I have installed this NWDS 2.0.12. When I click on the icon from desktop, I see a splash screen for a second and then immediately an error message saying 'Problem during startup. Check the .log file in .metadata folder of your workspace.'
    Following is the log file
    !SESSION -
    !ENTRY org.eclipse.core.launcher 4 0 Jun 29, 2006 16:09:37.302
    !MESSAGE Exception launching the Eclipse Platform:
    !STACK
    java.lang.NoClassDefFoundError: com/sap/tc/logging/Configurator
         at java.lang.Class.getDeclaredConstructors0(Native Method)
         at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
         at java.lang.Class.getConstructor0(Class.java:1930)
         at java.lang.Class.getConstructor(Class.java:1027)
         at org.eclipse.core.internal.plugins.PluginDescriptor.internalDoPluginActivation(PluginDescriptor.java:709)
         at org.eclipse.core.internal.plugins.PluginDescriptor.doPluginActivation(PluginDescriptor.java:188)
         at org.eclipse.core.internal.plugins.PluginClassLoader.activatePlugin(PluginClassLoader.java:112)
         at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java:185)
         at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java:485)
         at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:882)
         at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:862)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
         at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:130)
         at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:167)
         at org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:103)
         at org.eclipse.core.internal.runtime.InternalPlatform.loaderGetRunnable(InternalPlatform.java:578)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.eclipse.core.internal.boot.InternalBootLoader.getRunnable(InternalBootLoader.java:471)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:854)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:784)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:602)
    Can somebody help me to resolve this? What should be the potential cause for the error?

    java.lang.NoClassDefFoundError: <b>com/sap/tc/logging/Configurator</b>
    Either a missing jar or the classpath is not defined right.

  • E-Commerce Catalog error and log configurator probelm?

    Hello,
    I am trying to browse a B2B shop (http://server:port/b2b/b2b/init.do) in CRM 5.0 and getting following error message:
    The catalog that you have selected is currently unavailable; try again later
    I am using CRM 5.0 System (IDES Client) and basically trying to setup a E-Commerce development environment.
    Following are the steps i have done so far for E-Commerce configuration:
    1. Configured ISADMIN (http://server:port/isauseradm/admin/xcm/init.do).
    1.1 Changed following params for Start->General Application Settings->Customer->isauseradm->isauseradmconfig:
    >> SSLEnabled: false
    >> appinfo: true
    >> show start.jsp: true
    >> AddUserToPartner: true
    >> AcceptExistingUser: true
    1.2 Created a new JCo connection under Start->Components->Customer->jco and entered my back end CRM System details and saved it as CRM_800_JCO. I also did Run Test which was successful.
    1.3 Created a new JCo connection under Start->Application Configurations->Customer and entered following params and saved it with name CRM_800_ISAUSERADMSTD:
    >> Base configuration: isauseradmStandard
    >> default configuration: X
    >> active configuration: X
    >> jcodata: CRM_800_JCO
    >> backendtype: crmdefault
    >> usertype: CRM_Standalone
    >> uidata: default
    2. Configured B2B (http://server:port/b2b/admin/xcm/init.do).
    2.1 Changed following params for Start->General Application Settings->Customer->b2b->b2bconfig:
    >> SSLEnabled: false
    >> appinfo: true
    >> show start.jsp: true
    2.2 Created a new JCo connection under Start->Components->Customer->jco and entered my backend CRM System details and saved it as CRM_800_JCO. I also did Run Test which was successful.
    2.3 Created a new JCo connection under Start->Application Configurations->Customer and entered following params and saved it with name CRM_800_B2BCRMSTD:
    >> Base configuration: b2bcrmstandard
    >> default configuration: X
    >> active configuration: X
    >> jcodata: CRM_800_JCO
    >> usertype: CRM_Standalone
    3. I was really not sure if ShopAdmin config is required or not but i did it. Configured SHOPADMIN (http://server:port/shopadmin/admin/xcm/init.do).
    3.1 Changed following params for Start->General Application Settings->Customer->shopadmin->shopadminconfig:
    >> SSLEnabled: false
    >> appinfo: true
    >> show start.jsp: true
    3.2 Created a new JCo connection under Start->Components->Customer->jco and entered my backend CRM System details and saved it as CRM_800_JCO. I also did Run Test which was successful.
    3.3 Created a new JCo connection under Start->Application Configurations->Customer and entered following params and saved it with name CRM_800_CRMSHOP:
    >> Base configuration: crmshop
    >> default configuration: X
    >> active configuration: X
    >> jcodata: CRM_800_JCO
    4. Restarted CRM J2EE.
    5. Setup TREX 7.0.
    5.1 From TREX Administration, created a new connection (Type A, i.e., using System Number and Application Server Host) for CRM System and also RFC Dest. (sm59) in CRM System.
    5.2 Restarted TREX and connected this connection.
    5.3 Following are the visible column values for this connection in TREX Administration:
    >> Connection Status: <connected>
    >> Configuration Satus: Green
    >> SAP System: CRM
    >> RFC Destination: TREX_DEFAULT
    >> Gateway: local
    >> RfcServer Instances: 1 (no automatic changes)
    >> TREXRfcServer Processes: 1
    >> Workprocesses: 6 (4 DIA, 2BGD)
    5.4 Did a RFC Connection test in CRM System using SM59 which was successful as well.
    5.5 Using Transaction SRMO (Retrieval : Search Server Relation Monitor) in CRM System changed the RFC Destination for Search server ID DRFUZZY (for both I and S type RFC Server destination action) to TREX_DEFAULT. Did a connection test for this and it was successful.
    6. Initiated Replication using transaction COMM_PCAT_IMS_INIT with following params:
    >> Product Catalog: PCSHOP
    >> Variant: VAR_EN
    >> Search Server Relation:  DRFUZZY
    >> Publishing Computer ID:
    >> Allows Parallel Processing:
    >> Publish Documents via HTTP:
    >> Transfer Document Content: X
    >> Package Size of Indexing: 5,000
    >> Processing Existing Indexes: Overwrite Index Only When OK
    >> Behavior when Error Messages Occur: Cancel Variant Replication
    7. Logged into ISADMIN User Config (http://server:port/isauseradm/useradmin/init.do) and created a new user using the option New User and New Contact Person with an existing company of type Sold-To Party and which belongs to the sales area that is linked with PCSHOP Product Catalog (from IDES data).
    Now, when i log into B2B Page (http://server:port/b2b/b2b/init.do) using the newly created user and click on the shop PC4BIZ_EN i get following error message:
    The catalog that you have selected is currently unavailable; try again later
    I also created a new Product Catalog and did the Initial Replication still getting the same above error message.
    Can anyone please tell me what am i missing or what mistake i have done?
    I even restarted CRM System, but the result is still the same.
    Also, how do i check the log files for B2B? I checked the E-Commerce Admin Console (http://server:port/b2b/admin/index.jsp) and clicked on the logging link, but i get the following message:
    Logging is now configured centrally in the J2EE Engine Visual Administrator (server service: Log Configurator)
    How exactly do i configure and what is the right path for B2B Logging in J2EE Visual Administrator? And where will the log files for B2B be stored on the server?
    I would really appreciate (and of course award points) for your help on this.
    thanks and regards,
    Vasu

    Thanks for the Note reference. I will go through it now and try to check the log files.
    And regarding the error message i don't think it could be because of The Catalog variant is not set right in the Shopadmin application as all the values in Shopadmin seem to be correct. Anyhow following are the current values selected for the custom Product Catalog I created:
    Shop Id: ZTEST
    General Information
    --> Usage
    > Business Scenario: Internet Sales B2B
    --> Authorizations
    > Authorization Group: <blank>
    --> User Administration
    > Partner Function Contact Person: 00000015
    > Country Group: <blank>
    --> Billing Documents
    > Display of Billing Documents: No Billing Documents
    --> Store Locator
    > Display Store Locator: <blank>
    Catalog
    --> Product Catalog
    > Catalog Search: <blank>
    > Catalog: ZTEST
    > Catalog Variant: VAR_EN
    > Catalog View: <blank>
    > Hide Internal Catalog: <blank>
    > Controlling Price Determination in the Catalog: via IPC
    > Profile group for pricing related attributes for exchange products: <blank>
    Transactions
    --> General
    > Allow transaction management for other business partners in hierarchy: <blank>
    > Large Documents: Display All Items
    > Document type can be chosen late: <blank>
    > Batch Processing Permitted: <blank>
    > Display product determination information: X
    --> Order
    > Choose Order Types: Order Type
    > Order Type: ISBB
    --> Order Template
    > Order Templates Allowed: X
    > Order Type: ISBB
    --> +Quotations
    > Creating a Quotation: No Quotation
    --> Contracts
    > Contract Determination: <blank>
    --> Contract Negotiations
    > Allow Contract Negotiations: <blank>
    Marketing
    --> Global Product Recommendation
    > Display Global Product Recommendation: <blank>
    --> Personalized Product Recommendation
    > Display Personalized Product Recommendation: <blank>
    --> +Product-Related Proposals +
    > Display Product-Related Proposals: <blank>
    --> +Campaigns +
    > Allow manual entry of campaigns: <blank>
    Auction
    --> Auction
    > Auctions allowed: <blank>
    Regarding the reason "The Catalog was not replicated properly and is hence unavailable on TREX", is there any way to verify this? When i ran Initial Replication (transaction COMM_PCAT_IMS_INIT with the values i said in my first post) everything was green.
    Also, how do i clear the Catalog Cache? Is it the same as clearing the Catalog Cache Statistics in E-Commerce Administration Console (http://server:port/b2b/admin/index.jsp)?
    Thanks and Regards,

  • Logging configuration problem

    Hi all
    I am working with JRun4. My problem is logging.
    logging mechanism can send messages to these destinations:
    1) The console screen
    2) The Log file.
    In both cases , logging information is obtained. but The console screen shows information which i print by System.out.println() , and The log file shows information which is Event generated. I want to store information in a file , which is given by System.out.printlln().
    I have done entries in jrun.xml as
    <service class="jrunx.logger.LoggerService" name="LoggerService">
    <attribute name="format">{server.date} {log.level}{log.exception}</attribute>
    <attribute name="errorEnabled">true</attribute>
    <attribute name="warningEnabled">true</attribute>
    <attribute name="infoEnabled">true</attribute>
    <attribute name="debugEnabled">false</attribute>
    <attribute name="metricsEnabled">true</attribute>
    <attribute name="metricsLogFrequency">60</attribute>
    <attribute name="metricsFormat">Web threads(busy/total): {jrpp.busyTh}/{jrpp.totalTh} Sessions: {sessions} Total Memory={totalMemory} Free={freeMemory}</attribute>
    <service class="jrunx.logger.ThreadedLogEventHandler" name="ThreadedLogEventHandler" >
    <service class="jrunx.logger.ConsoleLogEventHandler" name=":service=ConsoleLogEventHandler"/>
    <service class="jrunx.logger.FileLogEventHandler" name="FileLogEventHandler">
    <attribute name="filename">{jrun.rootdir}/logs/{jrun.server.name}-event.log</attribute>
    <attribute name="rotationSize">200k</attribute>
    <attribute name="rotationFiles">3</attribute>
    <attribute name="closeDelay">5000</attribute>
    <attribute name="deleteOnExit">false</attribute>
    </service>
    </service>
    </service>
    what should i do for this?
    Please guide me.

    You should put it in the root of your classes (Ex: with JBuilder is
    $projecthome/classes)
    Alexp wrote:
    Hi !
    I have a problem with the logging configuration.
    What is the right place for the log4j.properties file?
    Thanks a lot for cooperation,
    Alex.

  • Pi 7.1 ehp1 log-configuration.xml, howto create/edit in NWDS?

    Hello,
    In NWDS 2.0 You have a special mode in NWDS  to edit the file. You get tabs with Log Formatter, Log Destination, Log Controller and Source.
    How does it work in NWDS 7.1 EHP1?
    The log-configuration shipped with the example module is packed inside the sample adapter module jar. This seems not right? It should be in the ear?
    In nwds I create an ear, and then use the nwpacktool to repack it as an sda to be able to deploy with jspm. There is a firewall so I can't deploy from nwds.
    I'm building an adapter module. It works fine besides that the logcontroller doesn't display in the nwa, and I can't set the log levels.
    I've tried placing the log-configuration.xml both in the META-INF of the jar and the META-INF of the ear but it still doesn't work.
    Thanks for your help.
    Best regards
    Otto Frost

    Hello,
    The NWDS 7.1 EHP1 doesn't recognize the file in the META-INF.
    In 7.11 the log-configuration.xml isn't used anymore according to SAP.
    When the module is started the tracing location is displayed in the log-configurator automagically.
    My module wasn't started after deployment.
    To start it I had to go into the NWA - Operation Management -
    Systems - Start&Stop - Java EE applications - myPiModule
    It was stopped, but started up when I clicked the "Logs" link.
    After this it is visible in the tracing locations in the nwa log configurator.
    Best regards
    Otto Frost

  • Log-configuration.xml How to use it

    I am trting to use the logging xcapabilities by usinmg log-configuration.xml but is unable to do so by simply configuring it. If I do using using coding i.e by adding in code location and filelog in code I am able to log. But instead of it I am more intrested to use log-configuration.xml. So please provide me with exact steps that need to be done for configuraing it rightly with category defined as well and using a fileLog as an example.

    I am trting to use the logging xcapabilities by usinmg log-configuration.xml but is unable to do so by simply configuring it. If I do using using coding i.e by adding in code location and filelog in code I am able to log. But instead of it I am more intrested to use log-configuration.xml. So please provide me with exact steps that need to be done for configuraing it rightly with category defined as well and using a fileLog as an example.

  • Oblix_OBWebGate_AuthnAndAuthz: ..- Unable to read log configuration file.

    Hi All,
    I have a painful problem with Oracle 10g Webgate. I am using Oracle_Access_Manager10_1_4_3_0_linux64_APACHE22_WebGate to procted Apache resource. I have some problem in Custom Authentication plugin. which is not still resolve(https://forums.oracle.com/thread/2549716).   
    Now I have apply patch BP9 (Oracle_Access_Manager10_1_4_3_0_BP09_Patch_linux64_APACHE22_WebGate) for Webgate, Now I have a new issue, I am unable to get the logon page of OAM when I try to access my Apache resource.
    The Error Message in the browser is:
    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
    More information about this error may be available in the server error log.
    Apache/2.2.3 (Oracle) Server at apache.tigerit.com Port 80
    In the error log file of  Apache I have found
    [Sun Jun 23 11:53:17 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    [Sun Jun 23 11:53:17 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    [Sun Jun 23 11:53:20 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    [Sun Jun 23 11:53:35 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    [Sun Jun 23 11:53:35 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    [Sun Jun 23 11:53:35 2013] [error] [client 192.168.1.156] Oblix_OBWebGate_AuthnAndAuthz:  Error: /opt/netpoint/webgate/access/oblix/config/oblog_config_wg.xml - Unable to read log configuration file.
    Can Anyone help me regarding this issue...
    Thanks
    Tamim Khan

    Hi Colin,
    Thanks for your help, You are right I have change the permission of /opt/netpoint/webgate/access/oblix/lib/libxmlengine.so.
    Now I am able to access the logon page of the access manager.
    But the problem as I mention in (https://forums.oracle.com/thread/2549716) my ObSSOCookie value is still loggedcontinue.
    My Authentication return (ExecutionStatus.SUCCESS) Successful from the Java Code , and I am unable to login in the application. The thing is I can't manipulate ObSSOCookie from Java code.
    I have apply Patch 12363955 to resolve this issue. But this patch is now to resolve this issue.
    Have you any idea how to resolve this issue.
    Thanks
    Tamim Khan

  • Cisco ISE log configuration commands enetered on routers

    Hello,
    I am trying to migrate from Cisco ACS to ISE.
    I want to log configuration commands entered on routers.
    I have configured the routers to send accounting radius to ISE but ISE sees the messages as:
    "22003  Missing attribute for authentication
    11014  RADIUS packet contains invalid attribute(s)"
    Can I configure ISE to receive radius accounting messages ?
    Is there another way to configure ISE to log configuration commands ?
    Another way would be to send syslog messages using the archive configuration on routers, but I cannot find the syslog mesages on ISE.
    Regards,
    Bogdan

    You should post your question on the AAA forum
    https://supportforums.cisco.com/community/netpro/security/aaa
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • Log configuration changes to syslog on Nexus 7000?

    I need to be able to log any configuration changes to syslog on our Nexus switches. On IOS this is easy with the archive commands, but I'm a little stuck trying to do this on our Nexus gear. On the IOS gear I run the commands:
    archive
    log config
    logging enable
    logging size 100
    hidekeys
    notify syslog
    How do I do the equivalent on NX-OS?

    ​Cisco NX-OS can log configuration change events along with the individual changes when AAA command accounting is enabled.
    With command accounting enabled, all CLI commands entered, including configuration commands, are logged to the configured AAA server. Using this information, a forensic trail for configuration change events along with the individual commands entered for those changes can be recorded and reviewed.
    Because of this capability, it is strongly advised that AAA command accounting be enabled and configured.
    Refer to the “TACACS+ Command Accounting” section of this document for more information.
    The Nexus 7000, by default keeps a local accounting log of all the configuration commands entered on the device; you can view this with the 'show accounting log' command.
    In NX-OS, we changed the way logging works.  We keep a local accounting log of all the
    configuration changes ("show accounting log"), but if you want to send those logs to a
    server, it must be done with through a TACACS server.  Please see the below documentation:
    Configuring AAA on Nexus
    TACACS command accounting
    -Thanks
    Vinod
    **Encourage Contributors. RATE Them.**

  • New handlers for JDK Logging

    Does anyone know of any OpenSource Handlers for JDK Logging such as a JMS Handler, JDBC Handler, SMPT Handler or Daily Rolling File Handler? I would love to use JDK instead of Log4J, but the latter supplies these handlers (appenders) out of the box.

    Huh?
    If you are looking for open source anyways then why not just use log4j?

  • Deployment of Logging configuration

    Hi,
    I have a problem, when I deploy an EAR-DC with a log-configuration.xml.
    I cant see in the Visual Administrator (under Cluster->J2E->Server 0
    0_..->Services->Deploy) the log configuration deployment. There was no
    error/warning after the deployment in the console.
    I have another EAR-DC and there I configured this xml-File similar and everything works fine.
    Regards,
    Trian

    I'm not sure whether you have the same problem as I have:
    I deployed EAR from NWDS and log configuration didn't change even if I had created log-configuration.xml. Then I found this file in root of EAR instead of inside META-INF folder. I made manual modificaton to that and manually deployed. And configuration worked. Still I want to have correct deployment automatically from NWDS.

Maybe you are looking for