ODI console: error 404

Hello
I have an issue with WebLogic and ODI console.
I don't know WebLogic so I hope anyone can help.
Weblogic server administration console has the following address: http://localhost:7001/console
ODI console has this address :http://localhost:7001/odiconsole
Launching the command file "startWebLogic" that is under the following path:
C:\Oracle\Middleware\user_projects\domains\odi_11g
everything works fine.
I've tried to set up the server as a Windows Service.
When I start the service the WebLogic administration console starts, while Odi console gives the following error:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
The script I wrote to create the service is the following:
SETLOCAL
set DOMAIN_NAME=odi_11g
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\odi_11g
set SERVER_NAME=AdminServer
set WLS_USER=weblogic
set WLS_PW=<adminpassword>
set PRODUCTION_MODE=true
set MEM_ARGS=-Xms40m -Xmx250m
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
Anyone can help?
Regards,
Stefania

Hello Rickson, thank you for your answer.
I tried restarting the machine but it didn't work.
I checked the log and here is what I found:
####<Jun 11, 2012 6:07:33 PM CEST> <Info> <netuix> <ASOS021> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <d90df5a0fd2bc5c7:-590296c1:137dc43d945:-8000-0000000000000016> <1339430853016> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<Jun 11, 2012 6:07:33 PM CEST> <Info> <netuix> <ASOS021> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <d90df5a0fd2bc5c7:-590296c1:137dc43d945:-8000-0000000000000016> <1339430853720> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
####<Jun 11, 2012 6:07:33 PM CEST> <Info> <netuix> <ASOS021> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <d90df5a0fd2bc5c7:-590296c1:137dc43d945:-8000-0000000000000016> <1339430853798> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
I really don't know WebLogic, so I don't know what to do...
Regards,
Stefania

Similar Messages

  • Error 404 while trying to access eas console

    We are getting error 404 all of a sudden when trying to access eas console. We have checked to make sure that all the services are up and running, and the port(10080) is up and running.
    We had a similar error with workspace a while back, and we had to modify port numbers on the mod_wl_ohs.conf file.
    But we find that the port numbers are unchanged this time in the conf file.
    Is there any other port we can use for eas console? http://<servername>:10080/easconsole/console.html
    All other services that sit on the same server work fine.(workspace, APS etc)
    Has anybody seen this kind of problem before?
    Thanks.

    If you are using 11.1.2 search for 404 in the EPM readme at: http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_1112000_readme.pdf
    What happens if if the install user logs into the machine and then out temp files in use by the application are removed; out of the box the user temp variables are used during deployment; there is a work-around to turn off terminal service feature to delete files on exist.
    In addition to confirming the service is up and running and the port answers you should review the syserror and sysout files which for 11.1.1.X are located in <HYPERION_INSTALL_DRIVE>\Hyperion\logs\services and in 11.1.2.X are located in <ORACLE_INSTALL_DRIVE>\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services
    Regards,
    John A. Booth
    http://www.metavero.com

  • Error 404 -- Not Found while accessing weblogic console

    Hi
    I get Error 404 Not Found while accessing the console or any other application
    which is deployed on the server
    while the server is running even i have restarted my server
    it shows server running in the log files as well as on the command console .
    but when i try to access console or any other application it gives me error page
    404 Not Found
    I am using weblogic 7 with SP2 on solaris
    So please help me in debugging the problem
    Thanks in advance....
    Pratap

    Hi
    I get Error 404 Not Found while accessing the console or any other application
    which is deployed on the server
    while the server is running even i have restarted my server
    it shows server running in the log files as well as on the command console .
    but when i try to access console or any other application it gives me error page
    404 Not Found
    I am using weblogic 7 with SP2 on solaris
    So please help me in debugging the problem
    Thanks in advance....
    Pratap

  • Ent 9 - Can't run mgmt console - admin.cwr gives Error 404: page not found

    Post Author: Alan Weiner
    CA Forum: Deployment
    We just did a fresh install of Crystal Enterprise 9.  When we try to run the Management console, we get an "Error 404: page not found"
      http://wdcwfc80/crystal/enterprise9/admin/en/admin.cwr
      Error 404: The page cannot be found

    Post Author: Alan Weiner
    CA Forum: Deployment
    From the server (although, it uses a browser to connect)
    colin mackenzie:
    Hi Alan Weiner.
    Do you get this message when you run this from the server? or just the workstation / client browser?

  • Error 404 not found for PAPIWS Console deployed in WLS

    Hi, All,
    I created 07-papiws-wls103-XAFDIDS.ear in OBPM 10.3.1 Admin Center, and deploy it to WLS 10.3 successfully.
    The problem is when I try to access PAPIWS console by http://192.168.48.1:8901/papiws/PapiWebService, Error 404 not found reported.
    Any ideas? Thanks in advanced.
    Best Regards,
    Bill

    Let's start by clearing up some confusion.
    PORTS
    In version 11.1.1.x here are how the common ports are defined by default:
    1. HTTP Server - 8888
    2. WLS_FORMS - 9001
    3. WLS_REPORTS - 9002
    4. WLS Admin Server - 7001
    So, if you understand how ports work in general, you should see that there are two ways to run a form. You can either go through HTTP Server or call WLS_FORMS directly. This means that both of the following would work, although one would be a direct path and the other would route the request through the HTTP Server:
    <li>http://ie1fdtfc5zl1s:9001/forms/frmservlet?config=frmdemo
    <li>http://ie1fdtfc5zl1s:8888/forms/frmservlet?config=frmdemo
    Port 7001, will always be the Admin Server port by default for the Classic domain. By default, the only thing you can do from here is access EM or WLS Console.
    As for the tns issue, by default, both the Builder and runtime will expect to find tnsnames.ora in the Instance Home \config so be sure you are adding the correct entries to the correct file.
    You can hard code a path to the file which you prefer be used by setting TNS_ADMIN in default.env (e.g. TNS_ADMIN=C:\Oracle\mytnsdirectory). This will apply only to running forms and not the Builder.
    Also, here is something which often is confusing to many people.... just because you launched your form from the Builder does not mean that the running form has anything to do with the Builder at that point. In other words, when you click on the RunForm button in the builder all you are doing is passing a url to a browser. The browser and the form are not using any of the Builder's settings except those which may have been passed in the URL (e.g. username/password). ALL running forms are considered "runtime". This means all of the environment configuration information for a running form will need to be set in default.env. The Builder, on the other hand will rely on the System variable, Windows Registry (or shell if on Unix).

  • While opening em console for soa --  Error 404--Not Found

    Hi Gurus,
    i installed SOA 11.1.1.5.0 wilh admin server ,soa_server,bam_server.
    while opeing the fm control using http://<hostname>.<domainname>:7001/em.
    the below error message is displaying .
    but i am able to open with http://<hostname>.<domainname>:7001/console.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Please can someone guide me how to resolve this.
    Thanks
    San

    While opening em console for soa --  Error 404--Not Found
    Regards,
    Anuj

  • Error 404 when opening CUCM Console Help

    Hi all:
    From some time back, I'm receiving this error message everytime I try to open Help in the CUCM 6.0
    type Status report
    message /ccmadmin/Help/es_UY/ccm/index.html
    description The requested resource (/ccmadmin/Help/es_UY/ccm/index.html) is not available.
    I have uninstalled IE and reinstalled and it is the same. I have tried with same IE version on another PC and it is working
    Any ideas?
    Thanks
    W.

    Hi Walter,
    I think you are hitting this Bug;
    You are hitting this bug;
    CSCsi48388 Bug Details
    Workaround: Set Browser to en-US
    JPN: CM Admin online help refers to ja, which results HTTP 404
    Symptom:
    HTTP 404 error occurs when trying to open online help from Cisco Unified Communications Manager Administration page in case the browser locale is Japanese.
    Conditions:
    Cisco Unified Communications Manager 6.0(1)
    Workaround:
    Change the browser locale to en-us and try to open the online help.
    1st Found-In
    6.0(0.9971.2)
    Fixed-In
    6.0(0.9901.234)
    6.0(0.9901.235)
    6.0(1.2118.1)
    6.1(1.1000.11)
    Related Bugs
    Help page won't display if browser has language different than English
    Symptom: From Cisco Unified CM Administration, click 'Help --> Contents' or 'Help --> This page'. A new page will be opened but producing HTTP Error 404. This happen if the browser has a language other than English US If GUI does not have localization for those pages, we should anyway point to the English version rather than producing an error, as it happens in earlier versions (5.x) Conditions: CCM 6.0.1 Administration web page. IE 6 with language other than English US
    Workaround: From IE Tools --> Internet Options --> Languages, remove the different language or leave it there but move English US on top. Further Problem Description: The page opened with languages installed other than Engish US, will point to URL: https:///Help//ccm/index.html where can be en_US (English USA), no (Norwegian), etc. If you instead use the following: https:///Help/en_US/ccm/index.html it will redirect to the following one and it's working: https:///Help/en_US/ccm/wwhelp/wwhimpl/common/html/frameset.htm - It does nott happen from Serviceability, OS or DRS. From there the URL point always to the URL with 'en_US' - It does not have regression: on CCM 5.x the URL is different and does not include localization - Reproducible also with browser different than IE (e.g. Firefox)
    Hope this helps!
    Rob

  • EPM 11.1.2.3 ,Error 404 - Not Found

    Hi All,
    I am getting the following error after my installation and configuration of EPM 11.1.2.3 and when I try to access the Workspace URL.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol --
    HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the
    Request-URI. No indication is given of whether the condition is temporary or
    permanent.
    If the server does not wish to make this information available to the client,
    the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code
    SHOULD be used if the server knows, through some internally configurable
    mechanism, that an old resource is permanently unavailable and has no forwarding
    address.
    I installed 11.1.2.3 in windows 7 ultimate OS and 64 bit and using sql server 2005 Database and configured Essbase,planning, hfm, arm, fcm,fdm ,hpcm, , everything was configured successfully but when I open the workspace URL it is throwing "Error 404 not found"
    I tried accessing http://machinename:7001/console (I replaced machinename with my machinename)
    even here I am getting the same error, but I checked the database and it has the table hss_component_types and it is populated with the various products.
    could you guide me
    Regards,
    SG
    The following is the error I am getting in C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jul 9, 2013 7:30:18 PM CDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\audit-client.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\css.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\ctg_custom.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\ldapbp.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\opencsv-1.8.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\registry-api.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\wlpool.jar>
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.2.5-50-153520-1.6.0_37-20121220-0844-windows-x86_64 from Oracle Corporation>
    <Jul 9, 2013 7:30:47 PM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Jul 9, 2013 7:30:57 PM CDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://SUBHASUBBU:7001.>
    <Jul 9, 2013 7:30:57 PM CDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jul 9, 2013 7:30:57 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jul 9, 2013 7:30:57 PM CDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log00002. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log.>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log is opened. All server side log events will be written to this file.>
    OracleFileSSOWalletImpl.getWalletData: enter...
    OracleFileSSOWalletImpl.getWalletData: System.getProperty(user.name)=SUBHASUBBU$
    OracleFileSSOWalletImpl.getWalletData: locking (shared) dummy sso file..
    OracleFileSSOWalletImpl.getWalletData: locking (shared) sso file..
    Oracle Wallet: wallet size 8349
    OracleWallet: getSecretStore
    OracleSecretStore: loading wallet from stream
    OracleSSOKeyStoreImpl: engineLoad
    OracleKeyStoreSpi: Loading wallet from stream
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    Processing TP 0
    Storing TP 0 as CN=Entrust.net Secure Server Certification Authority
    Processing TP 1
    Storing TP 1 as CN=Entrust.net Secure Server Certification Authority 1
    Processing TP 2
    Storing TP 2 as CN=Entrust.net Certification Authority (2048)
    Processing TP 3
    Storing TP 3 as CN=GTE CyberTrust Global Root
    Processing TP 4
    Storing TP 4 as OU=Secure Server Certification Authority
    Processing TP 5
    Storing TP 5 as OU=Class 1 Public Primary Certification Authority
    Processing TP 6
    Storing TP 6 as OU=Class 2 Public Primary Certification Authority
    Processing TP 7
    Storing TP 7 as OU=Class 3 Public Primary Certification Authority
    OracleKeyStoreSpi: Storing Secret0
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret1
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret2
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret3
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Keystore Loaded
    OracleWallet: getSecretStore
    OracleFileSSOWalletImpl.getWalletData: enter...
    OracleFileSSOWalletImpl.getWalletData: System.getProperty(user.name)=SUBHASUBBU$
    OracleFileSSOWalletImpl.getWalletData: locking (shared) dummy sso file..
    OracleFileSSOWalletImpl.getWalletData: locking (shared) sso file..
    Oracle Wallet: wallet size 3941
    OracleWallet: getSecretStore
    OracleSecretStore: loading wallet from stream
    OracleSSOKeyStoreImpl: engineLoad
    OracleKeyStoreSpi: Loading wallet from stream
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    Processing TP 0
    Storing TP 0 as OU=Class 1 Public Primary Certification Authority
    Processing TP 1
    Storing TP 1 as CN=GTE CyberTrust Global Root
    Processing TP 2
    Storing TP 2 as OU=Class 2 Public Primary Certification Authority
    Processing TP 3
    Storing TP 3 as OU=Class 3 Public Primary Certification Authority
    OracleKeyStoreSpi: Storing Secret0
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret1
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret2
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret3
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Keystore Loaded
    OracleWallet: getSecretStore
    <Jul 9, 2013 7:31:19 PM CDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jul 9, 2013 7:31:19 PM CDT> <Notice> <Security> <BEA-090083> <Storing boot identity in the file: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\security\boot.properties>
    <Jul 9, 2013 7:31:41 PM CDT> <Warning> <JTA> <BEA-110503> <The migrator(the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS of EPMServer0 has been migrated to backup server and the backup server is accessing the TLOG of EPMServer0. More safety can be achieved by setting isStrictOwnershipCheck to [true].>
    <Jul 9, 2013 7:31:42 PM CDT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jul 9, 2013 7:31:42 PM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log00002. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log.>
    <Jul 9, 2013 7:32:18 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jul 9, 2013 7:32:18 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    Using OraclePKI Provider
    javax.net.ssl.TrustManagerFactory supported
    javax.net.ssl.KeyManagerFactory supported
    Using OracleJSSE103 Provider
    <Jul 9, 2013 7:32:21 PM CDT> <Warning> <JDBC> <BEA-001552> <The logging last resource (LLR) data source accountreconciliation_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <Jul 9, 2013 7:32:21 PM CDT> <Warning> <JDBC> <BEA-001552> <The logging last resource (LLR) data source financialclose_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <Jul 9, 2013 7:33:42 PM CDT> <Warning> <Security> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    <Jul 9, 2013 7:33:47 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ACCOUNTRECONCILIATION [Version=11.1.2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
    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)
    Truncated. see log file for complete stacktrace
    >
    <Jul 9, 2013 7:34:12 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RuleService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:34:12 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RuleService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:34:13 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\aps\AppServer\InstallableApps\Common\aps.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.>
    <Jul 9, 2013 7:34:13 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\APS_11.1.2.0\mizf54/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.>
    <Jul 9, 2013 7:35:15 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FINANCIALCLOSE [Version=11.1.2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
    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)
    Truncated. see log file for complete stacktrace
    >
    <Jul 9, 2013 7:35:44 PM CDT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: com/oracle/adfm, Specification-Version: 1, referenced from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\FMADFWEB_11.1.2.0\nw1g9o]. Make sure the referenced optional package has been deployed as a library.>
    <Jul 9, 2013 7:35:49 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'ActionsService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:35:49 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'ActionsService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:36:57 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\SHAREDSERVICES_11.1.2.0\dt7o9d\interop.war/WEB-INF/web.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.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\odi\setup\manual\oracledi-agent\oraclediagent.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.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y/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.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.bam.odi.library, Specification-Version: 11.1.1, referenced from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y]. Make sure the referenced optional package has been deployed as a library.>
    <Jul 9, 2013 7:38:13 PM CDT> <Emergency> <Deployer> <BEA-149259> <Server 'EPMServer0' in cluster 'EPMServer' is being brought up in administration state due to failed deployments.>
    Hyperion Provider Services - Release 11.1.2.3.4408
    Copyright (c) 1991, 2013 Oracle and / or its affiliates. All rights reserved.
    connection mode : HTTP
    essbase.properties: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0/bin/essbase.properties
    java System properties -DESS_ES_HOME: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0
    Mode: Non Fusion read from Registry
    registry.isRegistryDatabaseCreated()true
    Registry was initialized sucessfully
    Component was found from component type DISC_MAN_PRODUCT
    Updating version Disclosure_dbVersion with DISC_MAN_PRODUCT
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 46
    Essbase® Administration Services - Version  11.1.2.3.000.4415
    Copyright © 1991, 2013 Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the recipient's personal use, without the express written permission of Oracle.
    US Patent Number 5,359,724
    US Patent Number 6,317,750
    Current time stamp: Tue Jul 09 19:38:54 CDT 2013
    Server started successfully
    Waiting for client requests
    HRContextListener::contextInitialized
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 203
    - WEBLOGIC
    null
    - The AMHM configuration file path is..nullconf
    -  getting attributes for bsp.jsr: [Migration, Ant-Version, Manifest-Version, Created-By, Version]
    -  going to get value for Migration attribute
    -  Encryption Type : AES
    - Invocation of generateSecurityFile Successful
    - userName :
    - ServiceID :
    - applicationName :
    - Configuration File (config.xml) does not exist under C:\Oracle\Middleware\user_projects\epmsystem1\Planning\planning1\config.xml Process aborted.
    - Migration Failed
    Utf8Filter: forceRequestCharacterEncoding set to true (init-param=true)
    Utf8Filter: repairRequestParameters set to false (init-param=false)
    Utf8Filter: rebuildPathInfo set to false (init-param=false)
    Utf8Filter: revertRequestURI set to true (init-param=true)
    Utf8Filter: settings are true/false/false/true
    Initializing CORBA ORB.
    CORBA ORB initialization complete.
    Loading configuration from registry
    WSBaseServlet.setDefaultGSMContext(): Servlet GSM context. host=192.168.204.1:6800
    Log configuration: file:/C:/Oracle/Middleware/user_projects/epmsystem1/ReportingAnalysis/RAFrameworkWebapp/WEB-INF/logging.properties
    <Jul 9, 2013 7:39:39 PM CDT> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Jul 9, 2013 7:39:39 PM CDT> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EPMServer.>
    <Jul 9, 2013 7:39:44 PM CDT> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on fe80:0:0:0:0:5efe:c0a8:ed01:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[9]" is now listening on fe80:0:0:0:0:100:7f:fffe:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[13]" is now listening on 0:0:0:0:0:0:0:1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:cc01:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:0:5efe:c0a8:7:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[12]" is now listening on 127.0.0.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[8]" is now listening on fe80:0:0:0:3415:3499:e650:c29e:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[10]" is now listening on fe80:0:0:0:2d02:d309:55d5:a150:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[11]" is now listening on fe80:0:0:0:5894:d88c:c022:f32b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.204.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.0.7:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on fe80:0:0:0:c885:cffb:be7a:3e0b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:1d4d:5292:d06b:f62b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.237.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EPMServer0" for domain "EPMSystem" running in Production Mode>
    <Jul 9, 2013 7:40:09 PM CDT> <Warning> <Server> <BEA-002611> <Hostname "SUBHASUBBU", maps to multiple IP addresses: 192.168.204.1, 192.168.237.1, 192.168.0.7, fe80:0:0:0:c885:cffb:be7a:3e0b%18, fe80:0:0:0:1d4d:5292:d06b:f62b%20, fe80:0:0:0:3415:3499:e650:c29e%15>
    <Jul 9, 2013 7:40:09 PM CDT> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
    <Jul 9, 2013 7:40:11 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jul 9, 2013 7:40:11 PM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
    <Jul 9, 2013 8:11:16 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSS_COMPONENT_TYPES WHERE 1 = 0" set up for pool "EPMSystemRegistry" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:11:16 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM V8_VERSION WHERE 1 = 0" set up for pool "raframework_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:11:54 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,190 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:04 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,198 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:19 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 0:0:0:0:0:0:0:1:54,216 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSS_COMPONENT_TYPES WHERE 1 = 0" set up for pool "EPMSystemRegistry" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM ARM_ATTRIBUTES WHERE 1 = 0" set up for pool "accountreconciliation_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM AIF_LOOKUP_MAPPINGS WHERE 1 = 0" set up for pool "aif_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM CALCMGRCONFIG WHERE 1 = 0" set up for pool "calc_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DISCMAN_COUNTER WHERE 1 = 0" set up for pool "discman_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM SERVERLOGID WHERE 1 = 0" set up for pool "eas_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM FCC_USER_ATTRIBUTES WHERE 1 = 0" set up for pool "financialclose_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver]Object has been closed.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REPW" set up for pool "odiWorkRepository" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSPSYS_CLUSTER WHERE 1 = 0" set up for pool "planning_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HPM_APPLICATION WHERE 1 = 0" set up for pool "profitability_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:18:49 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,579 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:22:29 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,820 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:29:44 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:55,178 during the configured idle timeout of 5 secs>

    First of all "I installed 11.1.2.3 in windows 7 ultimate OS", it is not a supported OS so if you want assistance problem solving you should stick with a supported OS.
    It also looks like you have installed a whole range of products some requiring additional configuration and the requirement of SOA.
    I recommend starting with a support OS and only install products that are required.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • ODI Console deployment failed

    Hi guys,
    I've configured ODI console as Managed Server and can start it successfully from Weblogic Admin console. However in the "Deployments" tab its status is failed. That's how I receive the "Error 404--Not Found" when I enter the ODI console URL.
    I'm young to Weblogic. How to diagnose what cause the deployment failed?
    Thanks,
    Jeffrey

    Hi Tina and Sandeep,
    I found the following error in the log file:
    Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:305) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:246) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:262) at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54) at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:246) at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149) at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:21) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    I have edited the commEnv.cmd file by adding $MW_HOME\modules\oracle.jrf_11.1.1\jrf.jar to WEBLOGIC_CLASSPATH but still got the same error.
    Question: Is WEBLOGIC_CLASSPATH in commEnv.cmd file the right place to setup?
    Thanks,
    Jeffrey

  • Error 404 -- Not Found, when a Servlet is invoked from browser

    Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
              even the simplest servlet.
              I painstakenly went through all the steps that are listed in the WebLogic
              Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
              have missed a step somewhere.
              I have modified the weblogic.properties file as per all the instrustions,
              but the server simply won't recognize any servlets, not even the SqlServlet
              that came with the server as an example.
              It would require more than 1 exchange of posts to resolve it for me, and I
              am wondering if one of you is willing to work with me on this until I have
              managed to configure the server to make a servlet work on it.
              The server does function as a Web server as I can run the index.html
              document by entering the URL: http://localhost:7001/index.html
              I am pasting the contents of weblogic.properties file below to get the
              person who is willing to help me started.
              The machine I have is a Pentium III with Windows 2000 Professional on it.
              It's a home machine and the WebLogic server is the freely downloadable
              version. I am using it to prepare for a potential contract work.
              I have managed to modify setEnv.cmd file and have managed to compile the
              SqlServlet.java, which is an example servlet. Neither this particular
              servlet nor a HelloWorld type of very basic servlet I have written are
              recognized by the server.
              As you can see from my weblogic.properties file (pasted at the end of this
              post), the SqlServlet has been registered. I have also uncommented the lines
              to allow for the following type of URL:
              http://localhost:7001/servlet/myServlet
              Thanks!
              Anjum Jaleel
              CONTENTS OF MY weblogic.properties file
              # THE WEBLOGIC PROPERTIES FILE
              # This file, which conforms to the java.util.Properties file
              # definition, configures your WebLogic products. You cannot run
              # WebLogic Server without setting required configuration properties in this
              # file. Required properties are marked and appear first in the file.
              # Details on each entry and important information about configuration
              # and security are documented on our website. Please go to:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # for full instructions on how to edit this file.
              # You do not need to include properties in this file unless you want to
              # change the default, embedded property. Some properties on the
              # AdminProps page are not listed here because the default property
              # is being used. You can change the default by adding the property and
              # its value to this file.
              # You cannot set weblogic.system.home in this file, since the WebLogic
              Server
              # must know where home is in order to retrieve this file. You can
              # change WebLogic home on the command line when you start the
              # WebLogic Server.
              # CLUSTER USERS: Note that the (shared) per-cluster properties file should
              # contain most all of the properties in this file. The only properties
              # that potentially belong in a per-server properties file for a server
              # running in a cluster are the registration (startup class) of pinned
              # RMI objects, and a few tuning properties that may be different for
              # servers in the cluster, depending upon hardware and memory. If you use
              # a per-server properties file, please REMOVE all properties except those
              # that are specifically required in the per-server properties file. You
              # can find specific notes on clusters by searching through this file for
              # "CLUSTER USERS".
              # The way this file is organized:
              # Core properties (includes REQUIRED and RECOMMENDED)
              # Core system properties
              # Core security-related properties
              # Core security-related properties for SSL
              # Core HTTPD administrative properties
              # Optional properties
              # Administrator properties
              # System properties
              # System startup files
              # System shutdown files
              # Security-related properties for Workspaces
              # Jolt for WebLogic properties
              # WebLogic Enterprise Connectivity properties
              # WebLogic File properties
              # WebLogic JMS demo properties
              # WebLogic RMI demo properties
              # WebLogic EJB demo properties
              # WebLogic XML demo properties
              # WebLogic ZAC demo properties
              # HTTPD administrative properties
              # WebLogic JDBC driver properties
              # WebLogic JDBC connection pool management
              # WebLogic demo connection pool
              # WebLogic HTTP Servlet properties
              # Proxy servlet registration
              # Classpath servlet registration
              # File servlet registration
              # ServerSideInclude servlet registration
              # PageCompileServlet (used by JHTML)
              # JSPServlet (used by JSP)
              # ServletServlet registration
              # Servlet reload properties
              # Servlet ACLs
              # WebLogic JSP properties
              # WebLogic JHTML properties
              # WebLogic RMI over IIOP properties
              # User-written and demo servlet registrations
              # CORE PROPERTIES
              # You should set these before you start the WebLogic Server the first time.
              # If you need more instructions on individual properties in this
              # section, check the same section in the Optional Properties, where
              # we've left the long explanations. Or, better yet, go to our
              # website and read all about properties, at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # CORE SYSTEM PROPERTIES
              # TCP/IP port number at which the WebLogic Server listens for connections
              weblogic.system.listenPort=7001
              # CORE SECURITY-RELATED PROPERTIES
              # Read important information about security at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # REQUIRED: The system password MUST be set in order to start the
              # WebLogic Server. This password is case-sensitive, at least 8 characters.
              # The username for the privileged user is ALWAYS "system".
              # This username and password also includes httpd access (see
              # HTTPD properties below).
              weblogic.password.system=lovkako1
              # RECOMMEND Set to 'everyone' if HTTPD is enabled
              weblogic.allow.execute.weblogic.servlet=everyone
              # Set individual ACLs to restrict access to HTTP-related resources,
              # such as the Administration servlets.
              # To make your own servlets generally available, follow this
              # pattern (provide a weblogic.allow.execute) for your packages and
              # set ACLs as appropriate.
              # CORE SECURITY-RELATED PROPERTIES FOR SSL
              # Read important information about SSL at:
              # http://www.weblogic.com/docs51/classdocs/API_secure.html
              # Enable SSL
              # (default if property not defined is false)
              weblogic.security.ssl.enable=true
              # SSL listen port
              weblogic.system.SSLListenPort=7002
              # Servlets for SSL
              # Authentication servlet for creating tokens for applets
              weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
              ervlet
              # Limits number of unclaimed stored tokens
              weblogic.security.certificateCacheSize=3
              # Capture CA root of client servlet
              weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
              # Certificates for SSL
              # Name of acceptable CA roots
              # For client authentication change value to a valid .pem file
              #weblogic.security.clientRootCA=SecureServerCA.pem
              # Server certificates for SSL
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              # registration for certificate generator servlet
              weblogic.httpd.register.Certificate=utils.certificate
              weblogic.allow.execute.weblogic.servlet.Certificate=system
              # CORE HTTPD ADMINISTRATIVE PROPERTIES
              # True permits the HTTPD to run (default)
              # Uncomment this property to disable HTTPD
              weblogic.httpd.enable=true
              # If authentication is required, add username/password for each user
              # who will be included in an ACL, as in this commented-out example:
              #weblogic.password.peter=#8gjsL4*
              # OPTIONAL PROPERTIES
              # These properties affect the behavior of the WebLogic Server.
              # You only need to set these properties if you want
              # to change the default setting, which is the property shown.
              # ADMINISTRATOR PROPERTIES
              # Administrator properties are optional information properties,
              # particularly useful for clusters.
              #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
              94104
              #weblogic.administrator.name=Joe Administrator
              #weblogic.administrator.phone=1 415 555 1234
              # SYSTEM PROPERTIES
              # System properties in this section are set to system defaults
              # Performance pack. The shared library must be accessible from your
              # PATH (NT) or from your shared library path (UNIX; the name of the
              # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              weblogic.system.nativeIO.enable=true
              # Outputs logging information to the console as well as to the log file
              weblogic.system.enableConsole=true
              # Sets the directory or URL for the WebLogic Admin help pages
              # The help pages are shipped in the "docs/adminhelp" directory, in the
              # default document root in public_html
              weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
              p/
              # If you prefer to access the most recent help pages, you can do so online
              # by commenting out the previous property and uncommenting this one:
              #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
              # Properties for tuning the server's performance
              # Number of WebLogic Server execute threads.
              weblogic.system.executeThreadCount=15
              # Other optional system properties
              # Limits size of weblogic.log (in K) and versions old log
              weblogic.system.maxLogFileSize=1024
              # Adjust minimum length of password
              weblogic.system.minPasswordLen=8
              # UNIX only: If running on port 80 on UNIX, enable the setUID program
              #weblogic.system.enableSetUID=false
              # UNIX only: Unprivileged user to setUID to after starting up
              # WebLogic Server on port 80
              #weblogic.system.nonPrivUser=nobody
              # CLUSTER-SPECIFIC PROPERTIES
              # Cluster-specific properties in this section are set to system defaults.
              # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              # in the per-cluster properties file ONLY.
              # Time-to-live (number of hops) for the cluster's multicast messages
              # (default 1, range 1-255).
              #weblogic.cluster.multicastTTL=1
              # Sets the load-balancing algorithm to be used between
              # replicated services if none is specified. If not specified,
              # round-robin is used.
              #weblogic.cluster.defaultLoadAlgorithm=round-robin
              # SERVER-SPECIFIC CLUSTER PROPERTIES
              # Cluster-related properties in this section are set to system defaults.
              # CLUSTER USERS: Note that these server-specific cluster-related properties
              # should be set in the per-server properties file ONLY.
              # Sets the weight of the individual server for the weight-based
              load-balancing.
              # Range is 0 - 100.
              # Larger numbers increase the amount of traffic routed to this server.
              #weblogic.system.weight=100
              # SYSTEM STARTUP FILES - Examples
              # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              # objects should be registered in the per-server properties file.
              # All other startup classes should be registered in the per-cluster
              # properties file.
              # For more info on writing and using startup file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a startup class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.startupClass.[virtual_name]=[full_pathname]
              # Add arguments for the startup class
              #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/StartupQuery.java
              #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
              #weblogic.system.startupArgs.doquery=\
              # query=select * from emp,\
              # db=jdbc:weblogic:pool:demoPool
              # SYSTEM SHUTDOWN FILES - Examples
              # For more info on writing and using shutdown file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a shutdown class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
              # Add arguments for the shutdown class
              #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/ShutdownTest.java
              #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
              #weblogic.system.shutdownArgs.ShutdownTest=\
              # outfile=c:/temp/shutdown.log
              # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              # For backward compatibility, the following entries disable Access
              # Control on Workspaces
              weblogic.allow.read.weblogic.workspace=everyone
              weblogic.allow.write.weblogic.workspace=everyone
              # JOLT FOR WEBLOGIC PROPERTIES
              # These properties configure a BEA Jolt connection pool for use with
              # the simpapp and bankapp examples, and register a servlet for use with
              # with the simpapp example. The default server address provided here
              # points to a public TUXEDO server that is hosted by BEA for use with
              # this example.
              # Servlet registration for simpapp example:
              #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
              t
              # Pool creation and cleanup
              # note this example is set up to work with the public
              # demo TUXEDO server available from BEA's website:
              #weblogic.system.startupClass.demojoltpoolStart=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
              #weblogic.system.startupArgs.demojoltpoolStart=\
              # poolname=demojoltpool,\
              # appaddrlist=//beademo1.beasys.com:8000,\
              # failoverlist=//beademo1.beasys.com:8000,\
              # minpoolsize=1,\
              # maxpoolsize=3
              #weblogic.system.shutdownClass.demojoltpoolStop=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
              #weblogic.system.shutdownArgs.demojoltpoolStop=\
              # poolname=demojoltpool
              # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
              # The registrations enable a BEA IIOP connection pool and
              # register servlets for use with the simpapp and university examples.
              # Configure for your environment and uncomment to use.
              # Uncommenting these properties requires WebLogic Enterprise Connectivity
              # and an operating WebLogic Enterprise Server.
              # Servlet registration for simpapp servlet example
              #weblogic.httpd.register.SimpappServlet=\
              # examples.wlec.servlets.simpapp.SimpappServlet
              #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
              # Servlet registration for simpapp EJB example
              # (You'll need to add the wlec_ejb_simpapp.jar to the
              # weblogic.ejb.deploy property in this file.)
              #weblogic.httpd.register.ejbSimpappServlet=\
              # examples.wlec.ejb.simpapp.ejbSimpappServlet
              #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
              # Pool creation and cleanup for the simpapp example
              #weblogic.CORBA.connectionPool.simplepool=\
              # appaddrlist=//wlehost:2468,\
              # failoverlist=//wlehost:2468,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # domainname=simpapp
              # Servlet registration for university Servlet example:
              #weblogic.httpd.register.UniversityServlet=\
              # examples.wlec.servlets.university.UniversityServlet
              #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
              # Pool creation and cleanup for the University example:
              #weblogic.CORBA.connectionPool.Univpool=\
              # appaddrlist=//wlehost:2498,\
              # failoverlist=//wlehost:2498,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # apppassword=wlepassword,\
              # domainname=university
              # WEBLOGIC FILE PROPERTIES
              # Maps a volume name to a path, for client file read/write
              #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              # WEBLOGIC JMS DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL JMS deployment should be done in the
              # per-cluster properties file ONLY.
              # You set up a JDBC connection pool if you want persistent messages
              # (including durable subscriptions). To use JMS and EJBs in the same
              # transaction, both must use the same JDBC connection pool. Uncomment
              # the following property to use the default JDBC connection pool
              # 'demo', which is defined in the Demo connection pool section of this file.
              #weblogic.jms.connectionPool=demoPool
              # The JMS Webshare example demonstrates how the ClientID for a
              # durable subscriber is configured in the connection factory:
              #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
              #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
              #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
              #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
              # The JMS trader example shows how to use JMS with an EJB. In addition
              # to uncommenting the following properties, you must also set up and
              # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
              # ejb_basic_statelessSession.jar to try out this JMS example:
              #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
              #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
              #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
              #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
              # Registers the underlying servlet
              #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
              # These properties are used with the ServerReceive JMS example,
              # which demonstrates how to establish a JMS message consumer
              # in a startup class:
              #weblogic.system.startupClass.serverReceive=\
              # examples.jms.startup.ServerReceive
              #weblogic.system.startupArgs.serverReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              # These properties are used with the PoolReceive JMS example,
              # which demonstrates how to establish a pool of JMS message consumers
              # in a startup class:
              #weblogic.system.startupClass.poolReceive=\
              # examples.jms.startup.PoolReceive
              #weblogic.system.startupArgs.poolReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
              # WEBLOGIC RMI DEMO PROPERTIES
              # CLUSTER USERS: Note that pinned RMI objects should be registered
              # in the per-server properties file ONLY. All other RMI startup
              # classes should be registered in the per-cluster properties file.
              # Remote classes registered at startup after the pattern:
              #weblogic.system.startupClass.[virtualName]=[fullPackageName]
              # These examples can be compiled to see RMI in action. Uncomment to use:
              #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
              #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
              #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
              # WEBLOGIC EJB DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              # per-cluster properties file ONLY.
              # See WebLogic Demo Connection Pool below for a connection pool
              # to use with these examples.
              # Deploys EJBeans. Uncomment the appropriate lines below and
              # modify DBMS-related info and paths to match your particular installation:
              #weblogic.ejb.deploy=\
              # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
              # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
              # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
              # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
              # g:/weblogic/myserver/ejb_subclass.jar, \
              # g:/weblogic/myserver/jolt_ejb_bankapp.jar
              # Servlet used by the EJB basic beanManaged example
              # Uncomment to use:
              #weblogic.httpd.register.beanManaged=\
              # examples.ejb.basic.beanManaged.Servlet
              # Add a list of users (set the password with
              weblogic.password.[username]=XXX)
              # to set an ACL for this servlet:
              #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
              #weblogic.password.user1=user1Password
              #weblogic.password.user2=user2Password
              # WEBLOGIC XML DEMO PROPERTIES
              # These properties are required to run the XML examples.
              # Uncomment to use.
              # CLUSTER USERS: Note that ALL servlets should be set up
              # in the per-cluster properties file ONLY.
              #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
              # BizTalk example properties
              #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
              #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
              #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
              dapter
              #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
              # WEBLOGIC ZAC DEMO PROPERTIES
              # These registrations enable the ZAC Publish Wizard.
              weblogic.zac.enable=true
              # Set the publish root for a WebLogic Server. Edit and
              # uncomment to use.
              #weblogic.zac.publishRoot=g:/weblogic/zac
              # Set an ACL for each package you publish. The [name] is
              # the "Package name" you assign in the ZAC Publish Wizard.
              # Publish a package, edit this property, and uncomment to use.
              #weblogic.allow.read.weblogic.zac.[name]=[user list]
              #weblogic.allow.write.weblogic.zac.[name]=system
              # HTTPD ADMINISTRATIVE PROPERTIES
              # Enables logging of HTTPD info in common log format and
              # sets the log file name (default is "access.log" in "myserver")
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              weblogic.httpd.enableEvents=false
              # Enables HTTP sessions
              weblogic.httpd.session.enable=true
              # Sets an optional cookie name. The default name is "WebLogicSession".
              # Prior to version 4.0, the default was "TengahSession". To make
              # this backward compatible with cookies generated from previous
              # installations, you should set this property to "TengahSession".
              # Uncomment this line and set this to any string of your choice,
              # or comment out this property to use the default.
              #weblogic.httpd.session.cookie.name=WebLogicSession
              # MIME types
              weblogic.httpd.mimeType.text/html=html,htm
              weblogic.httpd.mimeType.image/gif=gif
              weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
              weblogic.httpd.mimeType.application/pdf=pdf
              weblogic.httpd.mimeType.application/zip=zip
              weblogic.httpd.mimeType.application/x-java-vm=class
              weblogic.httpd.mimeType.application/x-java-archive=jar
              weblogic.httpd.mimeType.application/x-java-serialized-object=ser
              weblogic.httpd.mimeType.application/octet-stream=exe
              weblogic.httpd.mimeType.text/vnd.wap.wml=wml
              weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
              weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
              weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
              weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
              # In seconds, the keep-alive for HTTP and HTTPS requests
              weblogic.httpd.http.keepAliveSecs=60
              weblogic.httpd.https.keepAliveSecs=120
              # WEBLOGIC JDBC DRIVER PROPERTIES
              # Enables JDBC driver logging and sets the file name for the log
              # The weblogic.jdbc.logFile is placed in the per-server
              # directory (default is "myserver")
              weblogic.jdbc.enableLogFile=false
              weblogic.jdbc.logFileName=jdbc.log
              # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
              # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
              # in the per-cluster properties file ONLY.
              # For creating JDBC connection pools. This example shows a connection
              # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
              # to use 4 JDBC connections (with a potential for up to 10 connections,
              # incremented by two at a time, with a delay of 1 second between each
              # attempt to connect to the database), to an Oracle database server called
              # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
              # connections are dropped from the pool until only 4 connections remain
              open.
              # Every 10 minutes, any unused connections in the pool are tested and
              # refreshed if they are not viable.
              #weblogic.jdbc.connectionPool.oraclePool=\
              # url=jdbc:weblogic:oracle,\
              # driver=weblogic.jdbc.oci.Driver,\
              # loginDelaySecs=1,\
              # initialCapacity=4,\
              # maxCapacity=10,\
              # capacityIncrement=2,\
              # allowShrinking=true,\
              # shrinkPeriodMins=15,\
              # refreshMinutes=10,\
              # testTable=dual,\
              # props=user=SCOTT;password=tiger;server=DEMO
              # Get more details on each argument for this property in the
              # Administrators Guide on setting properties at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # Set up ACLs for this connection pool with the following:
              #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
              # guest,joe,jill
              #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
              # joe,jill
              #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

    Problem Resolved!
              I found out that I had 'http' instead of 'httpd' in the statement where I
              registered my servlet, SqlServlet.
              Now, I am having difficulty with hot deployment. The server is returning
              error 404.
              

  • Error 404--Not Found while accessing web app through Weblogic 6.1

    Hi everybody,
              I am new to Weblogic and recently installed Weblogic6.1
              on my machine and I am trying to access my application using weblogic
              and it gives
              Error 404--Not Found
              From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              10.4.5 404 Not Found
              I have uploaded the WAR file of my application using the Admin
              console. The WAR file is place under
              \bea\wlserver6.1\config\mydomain\applications\screen.war.
              What am I doing wrong ?
              Thanks is advance.
              PS: I am also including my web.xml file
              <?xml version="1.0" encoding="ISO-8859-1"?>
              <!DOCTYPE web-app
              PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              <web-app>
              <session-config>
              <session-timeout>-1</session-timeout>
              </session-config>
              <!-- Action Servlet Configuration -->
              <servlet>
              <servlet-name>action</servlet-name>
              <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
              <init-param>
              <param-name>application</param-name>
              <param-value>resources.nmr.ApplicationResources</param-value>
              </init-param>
              <init-param>
              <param-name>config</param-name>
              <param-value>/WEB-INF/struts-config.xml</param-value>
              </init-param>
              <init-param>
              <param-name>debug</param-name>
              <param-value>2</param-value>
              </init-param>
              <init-param>
              <param-name>detail</param-name>
              <param-value>2</param-value>
              </init-param>
              <init-param>
              <param-name>validate</param-name>
              <param-value>true</param-value>
              </init-param>
              <load-on-startup>2</load-on-startup>
              </servlet>
              <!-- Action Servlet Mapping -->
              <servlet-mapping>
              <servlet-name>action</servlet-name>
              <url-pattern>*.do</url-pattern>
              </servlet-mapping>
              <!-- PDF servlet configuration -->
              <servlet>
              <servlet-name>pdf</servlet-name>
              <servlet-class>com.abbott.gprd.servlets.PdfServlet</servlet-class>
              </servlet>
              <!-- PDF servlet Mapping -->
              <servlet-mapping>
              <servlet-name>pdf</servlet-name>
              <url-pattern>/pdf</url-pattern>
              </servlet-mapping>
              <!-- MIME Mapping -->
              <mime-mapping>
              <extension>mol</extension>
              <mime-type>chemical/x-mdl-molfile</mime-type>
              </mime-mapping>
              <!-- The Welcome File List -->
              <welcome-file-list>
              <welcome-file>index.jsp</welcome-file>
              </welcome-file-list>
              <!-- Application Tag Library Descriptor -->
              <taglib>
              <taglib-uri>/WEB-INF/app.tld</taglib-uri>
              <taglib-location>/WEB-INF/app.tld</taglib-location>
              </taglib>
              <!-- Struts Tag Library Descriptors -->
              <taglib>
              <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
              <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
              <taglib-location>/WEB-INF/struts-html.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
              <taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/nmr.tld</taglib-uri>
              <taglib-location>/WEB-INF/nmr.tld</taglib-location>
              </taglib>
              </web-app>
              

    hmm
              it all looks ok to me
              what happens if you try to access an image or something in your war (ie
              something not java related)
              also - i have seen on some machines that localhost doesnt work but 127.0.0.1
              does work
              your app should be trying to access index.jsp which should be in the root
              directory of your war
              does index.jsp exist and is it in the root directory of your war?
              lastly - i noticed you have a startup servlet. Put a system.out in the init
              method of the servlet. If the servlet is being deployed OK then you should
              see some output in the console
              "Ravi" <[email protected]> wrote in message
              news:[email protected]...
              > I am specifying the same http://localhost:7001/screen and it still
              > gives the same error.
              >
              > Following is part of my cofig.xml where myapp is specified.
              >
              > <CustomRealm
              >
              ConfigurationData="user.filter=(&(cn=%u)(objectclass=person));user.dn=ou
              =people,
              > o=example.com;server.principal=cn=admin,
              >
              o=example.com;membership.filter=(&(member=%M)(objectclass=groupofuniquen
              ames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.ho
              st=ldapserver.example.com;server.ssl=true;group.dn=ou=groups,
              > o=example.com"
              > Name="defaultLDAPRealmForNovellDirectoryServices"
              > Notes="This is provided as an example. Before enabling this
              > Realm, you must edit the configuration parameters as appropriate for
              > your environment."
              > Password="{3DES}/4XkW5rmVvBHzFtI9SRK/g=="
              > RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
              > <Server ListenPort="7001" Name="myserver" NativeIOEnabled="true"
              > TransactionLogFilePrefix="config/mydomain/logs/">
              > <Log FileName="config/mydomain/logs/weblogic.log"
              > Name="myserver"/>
              > <SSL Enabled="true" ListenPort="7002" Name="myserver"
              > ServerCertificateChainFileName="config/mydomain/ca.pem"
              > ServerCertificateFileName="config/mydomain/democert.pem"
              > ServerKeyFileName="config/mydomain/demokey.pem"/>
              > <WebServer DefaultWebApp="DefaultWebApp"
              > LogFileName="./config/mydomain/logs/access.log"
              > LoggingEnabled="true" Name="myserver"/>
              > <ServerDebug Name="myserver"/>
              > <ExecuteQueue Name="default"/>
              > <KernelDebug Name="myserver"/>
              > <ServerStart Name="myserver"/>
              > </Server>
              > <Application Deployed="true" Name="screen"
              > Path=".\config\mydomain\applications">
              > <WebAppComponent Name="screen" Targets="myserver"
              > URI="screen.war"/>
              > </Application>
              > <SNMPAgent Name="mydomain"/>
              > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              > <ApplicationManager Name="mydomain"/>
              > <JTA Name="mydomain"/>
              >
              > Thanks in advance.
              > Ravi.
              >
              >
              > "Matt Krevs" <[email protected]> wrote in message
              news:<[email protected]>...
              > > what url are you specifying?
              > >
              > > i would guess that http://localhost/screen-web would work. Hard to say
              > > without also seeing your config.xml
              > >
              > > The critical item in config.xml is the value of URI in the
              webappcomponent
              > > element for your application
              > >
              > > eg if it was
              > >
              > > <WebAppComponent Name="myapp-web" Targets="myerver" URI="myapp-web"/>
              > >
              > > then the url you would call is http://localhost/myapp-web
              > >
              > > "Ravi" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > Hi everybody,
              > > > I am new to Weblogic and recently installed Weblogic6.1
              > > > on my machine and I am trying to access my application using weblogic
              > > > and it gives
              > > >
              > > > Error 404--Not Found
              > > > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              > > > 10.4.5 404 Not Found
              > > >
              > > > I have uploaded the WAR file of my application using the Admin
              > > > console. The WAR file is place under
              > > > \bea\wlserver6.1\config\mydomain\applications\screen.war.
              > > >
              > > > What am I doing wrong ?
              > > >
              > > > Thanks is advance.
              > > >
              > > > PS: I am also including my web.xml file
              > > >
              > > > <?xml version="1.0" encoding="ISO-8859-1"?>
              > > >
              > > > <!DOCTYPE web-app
              > > > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
              > > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              > > >
              > > > <web-app>
              > > >
              > > > <session-config>
              > > > <session-timeout>-1</session-timeout>
              > > > </session-config>
              > > >
              > > > <!-- Action Servlet Configuration -->
              > > > <servlet>
              > > > <servlet-name>action</servlet-name>
              > > >
              <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
              > > > <init-param>
              > > > <param-name>application</param-name>
              > > > <param-value>resources.nmr.ApplicationResources</param-value>
              > > > </init-param>
              > > > <init-param>
              > > > <param-name>config</param-name>
              > > > <param-value>/WEB-INF/struts-config.xml</param-value>
              > > > </init-param>
              > > > <init-param>
              > > > <param-name>debug</param-name>
              > > > <param-value>2</param-value>
              > > > </init-param>
              > > > <init-param>
              > > > <param-name>detail</param-name>
              > > > <param-value>2</param-value>
              > > > </init-param>
              > > > <init-param>
              > > > <param-name>validate</param-name>
              > > > <param-value>true</param-value>
              > > > </init-param>
              > > > <load-on-startup>2</load-on-startup>
              > > >
              > > > </servlet>
              > > >
              > > > <!-- Action Servlet Mapping -->
              > > > <servlet-mapping>
              > > > <servlet-name>action</servlet-name>
              > > > <url-pattern>*.do</url-pattern>
              > > > </servlet-mapping>
              > > >
              > > > <!-- PDF servlet configuration -->
              > > > <servlet>
              > > > <servlet-name>pdf</servlet-name>
              > > >
              <servlet-class>com.abbott.gprd.servlets.PdfServlet</servlet-class>
              > > > </servlet>
              > > >
              > > >
              > > > <!-- PDF servlet Mapping -->
              > > > <servlet-mapping>
              > > > <servlet-name>pdf</servlet-name>
              > > > <url-pattern>/pdf</url-pattern>
              > > > </servlet-mapping>
              > > >
              > > > <!-- MIME Mapping -->
              > > > <mime-mapping>
              > > > <extension>mol</extension>
              > > > <mime-type>chemical/x-mdl-molfile</mime-type>
              > > > </mime-mapping>
              > > >
              > > >
              > > > <!-- The Welcome File List -->
              > > > <welcome-file-list>
              > > > <welcome-file>index.jsp</welcome-file>
              > > > </welcome-file-list>
              > > >
              > > > <!-- Application Tag Library Descriptor -->
              > > > <taglib>
              > > > <taglib-uri>/WEB-INF/app.tld</taglib-uri>
              > > > <taglib-location>/WEB-INF/app.tld</taglib-location>
              > > > </taglib>
              > > >
              > > > <!-- Struts Tag Library Descriptors -->
              > > > <taglib>
              > > > <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
              > > > <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
              > > > </taglib>
              > > >
              > > > <taglib>
              > > > <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
              > > > <taglib-location>/WEB-INF/struts-html.tld</taglib-location>
              > > > </taglib>
              > > >
              > > > <taglib>
              > > > <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
              > > > <taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
              > > > </taglib>
              > > >
              > > > <taglib>
              > > > <taglib-uri>/WEB-INF/nmr.tld</taglib-uri>
              > > > <taglib-location>/WEB-INF/nmr.tld</taglib-location>
              > > > </taglib>
              > > >
              > > > </web-app>
              

  • Error 404 -- NOT FOUND when running a form in form 11g

    Hi All,
    I got this problem when I run the forms using internet explorer.
    I work on Forms 11g which uses weblogic 10.3 for web deployment of the forms.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Can any one tell me where it went wrong.
    Thanks

    Let's start by clearing up some confusion.
    PORTS
    In version 11.1.1.x here are how the common ports are defined by default:
    1. HTTP Server - 8888
    2. WLS_FORMS - 9001
    3. WLS_REPORTS - 9002
    4. WLS Admin Server - 7001
    So, if you understand how ports work in general, you should see that there are two ways to run a form. You can either go through HTTP Server or call WLS_FORMS directly. This means that both of the following would work, although one would be a direct path and the other would route the request through the HTTP Server:
    <li>http://ie1fdtfc5zl1s:9001/forms/frmservlet?config=frmdemo
    <li>http://ie1fdtfc5zl1s:8888/forms/frmservlet?config=frmdemo
    Port 7001, will always be the Admin Server port by default for the Classic domain. By default, the only thing you can do from here is access EM or WLS Console.
    As for the tns issue, by default, both the Builder and runtime will expect to find tnsnames.ora in the Instance Home \config so be sure you are adding the correct entries to the correct file.
    You can hard code a path to the file which you prefer be used by setting TNS_ADMIN in default.env (e.g. TNS_ADMIN=C:\Oracle\mytnsdirectory). This will apply only to running forms and not the Builder.
    Also, here is something which often is confusing to many people.... just because you launched your form from the Builder does not mean that the running form has anything to do with the Builder at that point. In other words, when you click on the RunForm button in the builder all you are doing is passing a url to a browser. The browser and the form are not using any of the Builder's settings except those which may have been passed in the URL (e.g. username/password). ALL running forms are considered "runtime". This means all of the environment configuration information for a running form will need to be set in default.env. The Builder, on the other hand will rely on the System variable, Windows Registry (or shell if on Unix).

  • While running servlets getting errors 404 or 505 resource not found

    Hi all,
    I'm novice to J2EE.
    I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
    I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
    when i access my web application by specifying the proper server and port no and context root it is showing
    either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
    Now let me elaborate what i've done till now.
    My webapplication folder structure is : C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\classes\Sai\ServExamp.class
    My servlet is ServExamp.java
    I created a folder called "Suresh".  In that folder created another folder called "WEB-INF".  In WEB-INF created a folder called "Classes".
    Since my servlet is in package "Sai", the .class file reside in \Suresh\WEB-INF\Classes\Sai\ServExamp.class
    The source code is :
    package Sai;
    import javax.servlet.;*
    import javax.servlet.http.;*
    import java.io.;*
    public class ServExamp extends HttpServlet
    public void doPost(HttpServletRequest req,HttpServletResponse res)throws IOException
    PrintWriter out=res.getWriter();
    java.util.Date today=new java.util.Date();
    out.println("<html>"+"<body>"+
    *"<h1 align=center>HF\'s Chapter1 Servlet </h1>"*
    +"<br>"+today+"</body>"+"</html>");
    Now i'm almost done creating a web application.  Next, I constructed a simple web.xml descriptor that gives a web friendly name for my servlet, and points to the servlet. I constructed  web.xml descriptor file in the WEB-INF folder (C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\).
    The web.xml file source is :
    *<!DOCTYPE web-app*
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    *"http://java.sun.com/dtd/web-app_2_3.dtd">*
    *<web-app>*
    *<display-name>Hello World Web Application</display-name>*
    *<description>Test Servlet</description>*
    *<servlet>*
    *<servlet-name>ServExamp</servlet-name>*
    *<servlet-class>Sai.ServExamp</servlet-class>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>ServExamp</servlet-name>*
    *<url-pattern>/Suresh</url-pattern>*
    *</servlet-mapping>*
    *</web-app>*
    Now I have told Weblogic that the URI /Suresh corresponds to my servlet "Sai.ServExamp".
    My Web Application is ready to be deployed at this point. I logged onto Weblogic's admin console,
    *1) clicked on deployments, then navigated to "Web Application Modules" .*
    *2) Clicked "Deploy new Web Application Module"*
    *3) Navigated to the location of your web application folder (Suresh). There was a radio button next to it indicating that I can select that folder as a valid web application.*
    *4) I Clicked that radio button and clicked "Target Module".*
    *5) It informed that my web application "Suresh" will be deployed to myServer.It asked a name for my web application deployment. By default it was "Suresh"*
    I clicked Deploy.
    *6) After deployment, my web application "Suresh" appeared in the "Web Application Modules" tree on the left.*
    I Clicked on "Suresh"( my web application) then clicked the testing tab, then clicked the link shown there(http://localhost:7001/Suresh-2).
    It was not showing  my servlet (showed a 403 error)
    Error - 403
    This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    I think so it came b'coz I don't have an index.html or index.jsp page.
    *7)Instead,I added my servlet on to the URL it provided.*
    http://localhost:7001/Suresh-2/Suresh
    It is showing these error code: Http: 505 resource not allowed
    The page cannot be displayed
    The page you are looking for cannot be displayed because the address is incorrect.
    Please try the following:
    If you typed the page address in the Address bar, check that it is entered correctly.
    Open the localhost:7001 home page and then look for links to the information you want.
    Click  Search to look for information on the Internet.
    when i just type : http://localhost:7001/   -> Error 404 not found error
    it's showing
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    *10.4.5 404 Not Found*
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    I want to run my web application & any help would be appreciated.
    Thanks in advance.
    with regards,
    S.SayeeNarayanan.
    Note: I even deployed my war file, which i got by execution of (jar cv0f webapp.war . ) command from the root directory of my web application i.e. Suresh
    Then executed my webapplication it is showing
    error-505 resource not allowed.
    --------------------------------------------------------------------------------------------

    nammathamizhan wrote:
    Hi all,
    I'm novice to J2EE.
    You're also a novice to this forum.
    First, turn off the bold font.
    Second, post your question once and only once to a single forum. You only waited an hour before reposting your question. That's not the way this works. Asking your question multiple times will not increase the likelihood that you''ll get an answer. As a matter of fact, you're guaranteed nothing at all. Give it your best effort and hope for success. This isn't a paid consultancy - we're volunteers.
    I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
    I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
    when i access my web application by specifying the proper server and port no and context root it is showing
    either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
    If you're correct, and it's deployed, that would suggest that the URL you gave is incorrect.
    >
    Now let me elaborate what i've done till now.Good info - almost too much.
    %

  • No Images and Error 404 After Clean Install

    Hello folks, I was in the hope you could help me with a brand new and clean install of APEX on WebLogic, so here is the basics:
    WebLogic 10.3.6
    Jrockit 28.2.7
    Apex Listener:2.0.3.221.10.13.
    Apex 4.1.0.00.32
    DB Enterprise 11.2.0.3
    I just finished deploying WebLogic and the listener and I get 2 different errors:
    1- When I access the default page http://host:port/apex I receive the blank page without any images, but looking into the source I can see the APEX login source there,
    2- When I access any other URL I receive error 404 below.
    What I tried:
    1- Configure and deploy the i.war
    2- Configure the listener defaults
    3- Turned debug on
    4- Verified if the APEX_PUBLIC_USER account is open.
    Detail - There are no users for REST, I have skipped this step in configuration.
    Error 404 shown:
    Request Path passes syntax validation
    Mapping request to database pool: PoolMap [_poolName=apex, _regex=null, _workspaceIdentifier=null, _failed=false, _lastUpdate=-1, _template=null, _type=REGEX]
    Applied database connection info
    Attempting to process with PL/SQL Gateway
    ==== Processing Request: ====
    GET /apex/default.htm
    ==== Headers in Request ====
    Accept: */*
    Referer: http://hqw0cdt0rwla01.dev.pbgc.gov:8077/console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationTestingPage&handle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dapex%2CType%3DAppDeployment%22%29
    Accept-Language: en-US
    User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
    Accept-Encoding: gzip, deflate
    Host: hqw0cdt0rwlm05.dev.pbgc.gov:7677
    Connection: Keep-Alive
    Cookie: ORA_WWV_USER_64727692400863=8A0CE01E4C4ADA12; s_vi=[CS]v1|28CFBB1E851D08FB-40000104A00168A1[CE]; __utma=260516940.1098765263.1375813699.1375813699.1375813699.1; __utmz=260516940.1375813699.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_pers=%20gpv_e11%3DMyPBA%2520Is%2520Down%2520for%2520Maintenance%7C1375815499520%3B
    ==== Cookies in Request ====
    ORA_WWV_USER_64727692400863 = 8A0CE01E4C4ADA12
    s_vi = [CS]v1|28CFBB1E851D08FB-40000104A00168A1[CE]
    __utma = 260516940.1098765263.1375813699.1375813699.1375813699.1
    __utmz = 260516940.1375813699.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
    s_pers = %20gpv_e11%3DMyPBA%2520Is%2520Down%2520for%2520Maintenance%7C1375815499520%3B
    isValidRequest(), procedure name:
    Validating: default.htm
    *** Total number of arguments: 0
    Procedure DENIED with Error code: 404
    ==== Request Processed ====
    Not processed as PL/SQL Gateway request
    Attempting to process as a RESTful Service
    Determining if request can be dispatched as a Tenanted RESTful Service
    Request path has one path segment, continuing processing
    No Tenant Principal established yet, continuing processing
    APEX_LISTENER pool does not exist, cannot dispatch
    Any help is greatly appreciated.
    Thank you in advance,
    Andre

    Jeff, tried as you recommended I have the files extracted to:
    /ora/Middleware1036/user_projects/applications/apex/apex
    and
    /ora/Middleware1036/user_projects/applications/apex/apex_list
    The apex.war and i.war files are under "/ora/Middleware1036/user_projects/applications/apex/apex_list"
    The configdir is set to "/ora/Middleware1036/user_projects/applications/apex/apex_list"
    the configuration files can be found under "/ora/Middleware1036/user_projects/applications/apex/apex_list/apex" and "/ora/Middleware1036/user_projects/applications/apex/apex_list/apex/conf" the directories where created by the command "java -jar apex.war setup".
    The images directory is set to "/ora/Middleware1036/user_projects/applications/apex/apex/images"
    I still get the same errors.
    Any other ideas on how to resolve this issue?
    Thank you in advance,
    Andre

  • LSO Content Player  Error - HTTP Error 404 - File or directory not found

    Hi All
    Please could you assist.
    I have published a course to my ISS CMS and configured the links in both ECC and J2EE lsm/mediator.
    Result
    Username='username', SystemName='HRD', Client='030', Host='22.22.22.22', Language='EN', SystemNumber='00', EnablePoolSharing='true', MaxConnection=50, AbapDebug=false:
    CPCFG.RSURL = http://iiscmshost.domain/LSO600/Content/
    CPCFG.REPUS = username
    ServerURL=http://iiscmshost.domain/LSO600/Content/  ok!
    I was able to successfully publish the course from the Authoring Environment to the CMS server.
    When selecting the starting the course from the portal with content player i get the following error.
    HTTP Error 404 - File or directory not found
    But the URL is referring to - http://iiscmshost.domain/lms/mediator/courseview?sid=8685627505550088697845288091101&language=EN&sys=HRD&client=030&sap-accessibility=X
    How does directory http://iiscmshost.domain/lms/mediator get created when the content is in http://iiscmshost.domain/LSO600/Content ??
    Secondly can I change this reference to my LSO600/Content directory.
    Please advise with any information. Point will be awarded.
    Regards
    Maahir

    Dear Maahir,
    We are facing the same problem. We are pointing over CMS to IIS, instead of KM content of portal. We are successfully able to release and publish the course, then attach to a course participant also.
    But. When participants logs into the portal and click on Start Now. It giving 404 file not found Error. Its the same error. All our Course and content pointed to CMS IIS Server Url.
    When we did the content player config test, result is NOT OK. We have required R3 authorization and CMS user authorization also with admin rights. Content Player console is working in AE when we start up the course. Its showing the error.
    So, it seems like content player is not working properly. Bcoz we are launching course from  http://WEBDAV repository server maintained in back end system. Which is the IIS(CMS Server)for us. Do we need to maintain anything separately to launch a course from IIS Server on R3 and SAP Portal. Below sample URL from page.
    http://Sever:port/lms/mediator/courseview = xxxxxxxxxxxxxxx
    Could you please us know, how did you resolve the issue and tell me the cause of this issue.
    Thanks and Regards
    Obli

Maybe you are looking for