Weblogic agent and SAM integration

Hi all,
after configuring everything as mentioned in the documentation I'm still getting an excetion:
F:\SJS_Weblogic_9_agent_2.2\j2ee_agents\am_wl9_agent\bin>agentadmin --getUuid an
dy user sun
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: number of retry = 3
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: retry interval = 1000
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: retry error codes = []
Failed to create debug directory
01/17/2007 01:15:37:203 PM GST: Thread[main,5,main]
AdminUtils: Could not initialize admin info message: Got LDAPServiceException c
ode=19
01/17/2007 01:15:37:203 PM GST: Thread[main,5,main]
Crypt.static{}: Encryptor class= com.iplanet.services.util.JSSEncryption
Exception in thread "main" java.lang.NoClassDefFoundError: org/mozilla/jss/crypt
o/KeyGenAlgorithm
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.iplanet.services.util.Crypt.createInstance(Crypt.java:133)
at com.iplanet.services.util.Crypt.<clinit>(Crypt.java:103)
at com.iplanet.am.util.AdminUtils.getAdminDN(AdminUtils.java:106)
at com.sun.identity.sm.SMSEntry.<clinit>(SMSEntry.java:166)
at com.sun.identity.sm.DNMapper.<clinit>(DNMapper.java:59)
at com.sun.identity.idm.AMIdentity.<init>(AMIdentity.java:135)
at com.sun.identity.agents.tools.handler.GetUniversalIdHandler.handleReq
uest(GetUniversalIdHandler.java:120)
at com.sun.identity.agents.tools.admin.AgentAdmin.dispatch(AgentAdmin.ja
va:251)
at com.sun.identity.agents.tools.admin.AgentAdmin.run(AgentAdmin.java:15
2)
at com.sun.identity.agents.tools.launch.AgentAdminLauncher.launchAdminTo
ol(AgentAdminLauncher.java:204)
at com.sun.identity.agents.tools.launch.AgentAdminLauncher.main(AgentAdm
inLauncher.java:308)
Do you where is the missing class and to which class path I should add it?
Thanks in advance

I'm getting the below exception. It seems like weblogic can't initialize the idm service. Any idea?
SSOTokenValidator: validate failed with exception
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: Invalid transport string
     at com.sun.identity.agents.util.TransportToken.initializeFromString(TransportToken.java:158)
     at com.sun.identity.agents.util.TransportToken.<init>(TransportToken.java:130)
     at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:120)
     at com.sun.identity.agents.realm.AmRealm.authenticate(AmRealm.java:149)
     at com.sun.identity.agents.weblogic.v9.AmWLLoginModule.login(AmWLLoginModule.java:137)
     at weblogic.security.service.DelegateLoginModuleImpl$loginDelegateAction.run(DelegateLoginModuleImpl.java:169)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.security.service.DelegateLoginModuleImpl.executePriv(DelegateLoginModuleImpl.java:121)
     at weblogic.security.service.DelegateLoginModuleImpl.login(DelegateLoginModuleImpl.java:86)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at weblogic.security.service.PrincipalAuthenticator.authInternal(PrincipalAuthenticator.java:412)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:352)
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.doBootAuthorization(SecurityServiceManagerDelegateImpl.java:780)
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:893)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:775)
     at weblogic.security.SecurityService.start(SecurityService.java:133)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Best regards

Similar Messages

  • WebLogic 10gR3 and Windows Integrated Authentication

    Hi:
    I have an intranet web application running on WebLogic 10gR3 and would like to make use of the Windows Integrated Authentication (SSO, SPNEGO, Active Directory) so that the intranet users don't have to log in to access the web application.
    In weblogic, I've managed to create an ActiveDirectoryAuthenticator and can see all the users and groups from Active Directly. Also created a NegotiateIdentityAsserter with both WWW-Authenticate.Negotiate and Authorization.Negotiate options.
    When I set the web.xml login-config to BASIC, the browser shows the login dialog and authentication happens through AD. I've changed the login-config to CLIENT_CERT as suggested by the documentation:
    <login-config>
         <auth-method>CLIENT-CERT</auth-method>
    </login-config>but I'm getting the following error:
    Error 401--Unauthorized
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.2 401 Unauthorized
    The request requires user authentication. The response MUST include a
    WWW-Authenticate header field (section 14.46) containing a challenge
    applicable to the requested resource. The client MAY repeat the request
    with a suitable Authorization header field (section 14.8). If the request
    already included Authorization credentials, then the 401 response indicates
    that authorization has been refused for those credentials. If the 401
    response contains the same challenge as the prior response, and the user
    agent has already attempted authentication at least once, then the user
    SHOULD be presented the entity that was given in the response, since
    that entity MAY include relevant diagnostic information. HTTP access
    authentication is explained in section 11.Help is highly appreciated
    Albert
    Edited by: albertattard on Jul 13, 2009 3:40 PM
    Edited by: albertattard on Jul 13, 2009 3:42 PM

    Hi:
    I have an intranet web application running on WebLogic 10gR3 and would like to make use of the Windows Integrated Authentication (SSO, SPNEGO, Active Directory) so that the intranet users don't have to log in to access the web application.
    In weblogic, I've managed to create an ActiveDirectoryAuthenticator and can see all the users and groups from Active Directly. Also created a NegotiateIdentityAsserter with both WWW-Authenticate.Negotiate and Authorization.Negotiate options.
    When I set the web.xml login-config to BASIC, the browser shows the login dialog and authentication happens through AD. I've changed the login-config to CLIENT_CERT as suggested by the documentation:
    <login-config>
         <auth-method>CLIENT-CERT</auth-method>
    </login-config>but I'm getting the following error:
    Error 401--Unauthorized
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.2 401 Unauthorized
    The request requires user authentication. The response MUST include a
    WWW-Authenticate header field (section 14.46) containing a challenge
    applicable to the requested resource. The client MAY repeat the request
    with a suitable Authorization header field (section 14.8). If the request
    already included Authorization credentials, then the 401 response indicates
    that authorization has been refused for those credentials. If the 401
    response contains the same challenge as the prior response, and the user
    agent has already attempted authentication at least once, then the user
    SHOULD be presented the entity that was given in the response, since
    that entity MAY include relevant diagnostic information. HTTP access
    authentication is explained in section 11.Help is highly appreciated
    Albert
    Edited by: albertattard on Jul 13, 2009 3:40 PM
    Edited by: albertattard on Jul 13, 2009 3:42 PM

  • Weblogic.rmic and ant integration issue

    I am trying to call weblogic.rmic compiler through a ant script and was
    sucessful in doing so and generating the stubs and skelton for my RMI
    implementation.
    But i also want to pass a system property value (in the example i am passing
    file=stdout using -D to java) to weblogic.rmi compiler and don't know how to
    do that.
    Any help will be greatly appreciated...
    Thanks
    Kunjan Jhaveri
    781-372-3965
    [email protected]
    PS: Script enclosed.
    <target name="local.genStubs" depends="local.compile">
    <java classname="weblogic.rmic" fork="yes" failonerror="yes">
    <jvmarg value="-Dfile=stdout" />
    <arg value="-classpath" />
    <arg value="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
    <arg value="-d" />
    <arg value="${SRCDIR}${file.separator}build${file.separator}classes" />
    <arg value="com.ehealthdirect.ee.kernel.EEMutexManagerImpl" />
    <classpath>
    <pathelement
    path="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
    </classpath>
    </java>
    </target>

    As far as I know, rmic doesn't know anything about a "file" system property. Is
    there some reason you expect this to do something special?
    Kunjan Jhaveri wrote:
    I am trying to call weblogic.rmic compiler through a ant script and was
    sucessful in doing so and generating the stubs and skelton for my RMI
    implementation.
    But i also want to pass a system property value (in the example i am passing
    file=stdout using -D to java) to weblogic.rmi compiler and don't know how to
    do that.
    Any help will be greatly appreciated...
    Thanks
    Kunjan Jhaveri
    781-372-3965
    [email protected]
    PS: Script enclosed.
    <target name="local.genStubs" depends="local.compile">
    <java classname="weblogic.rmic" fork="yes" failonerror="yes">
    <jvmarg value="-Dfile=stdout" />
    <arg value="-classpath" />
    <arg value="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
    <arg value="-d" />
    <arg value="${SRCDIR}${file.separator}build${file.separator}classes" />
    <arg value="com.ehealthdirect.ee.kernel.EEMutexManagerImpl" />
    <classpath>
    <pathelement
    path="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
    </classpath>
    </java>
    </target>

  • Solstice Agent and SMC Integration

    This is a long shot, but has anybody attempted to integrate the Sun Management Center (SMC) Agent with the Solstice Enterprise Agent (SEA)? Can it be done ? Do you make the SMC Agent a sub-agent of SEA ? If so, what are the problems ? I am looking to utilise the SMC Agent for specific purposes, but cannot find any documentation detailing the logisitics of integrating it with SEA.

    This is a long shot, but has anybody attempted to integrate the Sun Management Center (SMC) Agent with the Solstice Enterprise Agent (SEA)? Can it be done ? Do you make the SMC Agent a sub-agent of SEA ? If so, what are the problems ? I am looking to utilise the SMC Agent for specific purposes, but cannot find any documentation detailing the logisitics of integrating it with SEA.

  • UCCX 7.0.1SR5 to 8.0 upgrade while also adding LDAP integration for CUCM - what happens to agents and Historical Reporting data?

    Current State:
    •    I have a customer running CUCM 6.1 and UCCX 7.01SR5.  Currently their CUCM is *NOT* LDAP integrated and using local accounts only.  UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
    •    The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
    Goal:
    •    Upgrade software versions and migrate to new hardware for UCCX
    •    LDAP integrate the CUCM users
    Desired Future State and Proposed Upgrade Method
    Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server. 
    Then during a weekend maintenance window……
    •    Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
    •    Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
    •    Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
    •    Restore the data from the UCCX PUT tool
    •    Continue setup per documentation
    At this point does UCCX see these agents as the same as they were before?
    Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
    I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
    We can simplify this question along these lines
    Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01.  Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software. 
    If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens? 
    I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
    What would historical reporting show in this case?  A set of old agents and a set of new agents treated differently?
    Has anyone run into this before?
    Is my goal possible while keeping the agent configuration and HR data as it was before?

    I was doing some more research looking at the DB schema for UCCX 8.
    Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
    My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
    How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
    Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
    Database table name: Resource
    The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
    A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive.

  • Agent Failover and AD Integration in Operations Manager

    Hi
    I got some queries around SCOM agent failover and AD Integration:
    Does the discovery wizard differentiates between domain-joined and workgroup systems in terms of deploying agent on them?
    Why do we ever need Active Directory Integration with Operations Manager as described here
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    - is it required for non-domain joined Windows systems or any other systems? All the other documents I read are saying that Windows agents can failover to other available MS in resource pool if their currently assigned MS fails and fails back automatically
    as soon as it comes back online.
    Is the automatic failover applicable to agents installed using client push (Discovery Wizard) Or it applies to agents installed manually using MOMAgent.msi?
    Also referred to this article
    http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    but doesn’t seems to be having grip on it so far. Request some details on the above points.
    Thanks
    Taranjeet Singh
    zamn

    Hi,
    For the first question, I don't think we can use discovery wizard to install agent on non-domain joined computers. Please refer to the below links for how to deploy SCOM agent to non-domain computers:
    http://blogs.technet.com/b/quenguyen/archive/2011/07/13/monitoring-non-domain-servers-using-scom.aspx
    http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om-2012.aspx
    For the second question, as we can read from the below link:
      http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    SCOM windows agents automatic failover does not require AD integration or PowerShell scripting or Configuration Manager or manual agents installation specially for small to medium environment and agents distribution between different SCOM management servers
    can be accomplished through push agents wizard, and windows agents failover can be simply verified from event viewer.
    Regards,
    Yan Li
    Regards, Yan Li

  • Any kind of integration experience with Weblogic JMS and Oracle AQ?

    Hi,
    In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
    I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
    After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
    Any comments, references, documentation, sample code, url will be most welcomed :)
    Thank you very much!
    Tonguc
    [email protected]
    References I found upto now;
    Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
    (Packages; javax.jms & oracle.jms)
    Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
    Part IV
    Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
    Chapter 11, "Introducing Oracle JMS"
    Chapter 12, "Oracle JMS Basic Operations"
    Chapter 13, "Oracle JMS Point-to-Point"
    Chapter 14, "Oracle JMS Publish/Subscribe"
    Chapter 15, "Oracle JMS Shared Interfaces"
    Chapter 16, "Oracle JMS Types Examples"
    A Sample Code from Otn
    http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

    I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
    3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
    One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
    I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
    In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
    Hope the above gives you a different perspective.
    Eric

  • Book on Weblogic Portal and beehive page flow portal integration

    I request oracle press to write a book on Weblogic Portal as well as Creating pageflow based portlets with weblogic portal and workshop.
    The old edocs.bea.com documentation sucks and does not meet the oracle press standard.
    Thanks
    Biren

    The Beta 9.2 Team,
    9.2 features sounds good and interesting. We are using BEA's Content management system(8.1) extensively.
    Our requirement is to create a portlet for Content Owner/Users to create HTML documents with images and upload it into BEA Repository. Upon uploading, Content Admin needs to be notified through email and they will either approve or reject the document. The content status again needs to be notified to the content owner/user via email.
    1. As known to everyone 8.1 doesn't have WYSIWYG editor and is included in 9.2. Can i reuse the 9.2 WYSIWYG functionality into 8.1 as a portlet??
    2. The following thread(http://forums.bea.com/bea/message.jspa?messageID=400001479&tstart=0) says
    - workflow ==> We have limited workflow support. We plan to enhance this in our next major release.
    Does this limited workflow support include email notification?
    Any inputs would be greatly appreciated!!
    Thanks,
    -Nach.

  • ODI 11g Weblogic agent start up failure

    I have defined the weblogic agent in my master repository but still can not get it to start in the weblogic sever? Does anyone know how i can resolve this problem?
    Please see full error below:
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
    ODI-1405: Agent OracleDIAgent start failure: the agent is not defined in the topology for master repository.
         at oracle.odi.runtime.agent.servlet.AgentServlet$1.doAction(AgentServlet.java:734)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:193)
         at oracle.odi.runtime.agent.servlet.AgentServlet.getSnpAgentForAgentInstance(AgentServlet.java:726)
         at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:323)
         at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:226)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    :oracle.odi.agent.logging.logFramework.OdiAgentException:ODI-1405: Agent OracleDIAgent start failure: the agent is not defined in the topology for master repository.

    Hi Adrian,
    I have started my work with new domain creation.
    Before that i have created two agents
    1)STAND_AGENT Host:localhost,port-20910
    2)JAVAAGNT1 Host:localhost,port-*20917*
    both i have started and tested the connection as well executing the interface using these 2 agents.It went fine.Then i started creating the domain.
    My adminserver Host:localhost,port-7011 and odi_server1 Host:localhost,port*-20917*(java agent port)( is this fine?).
    Completed the domain creation and started the admin server ,in logs i found the error for credential stores and i have done that also.
    Then stoped the server ans started the wls adminserver. In the log i am getting the same error u posted in the begining,
    ODI-1405: Agent OracleDIAgent start failure: the agent is not defined in the topology for master repository.
         at oracle.odi.runtime.agent.servlet.AgentServlet$1.doAction(AgentServlet.java:734)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:193)
         at oracle.odi.runtime.agent.servlet.AgentServlet.getSnpAgentForAgentInstance(AgentServlet.java:726)
         at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:323)
         at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:226)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Adrian ,Please help.
    Thanks & Regards,
    MNK

  • ODI 11g Weblogic agent test connection  in windows

    Hi,
    I have deployed the ODI console,Java EE agent and ODI sdk web services.Weblogic admin server link http://localhost:7001/console/login/LoginForm.jsp.
    The link for my ODI console looks like this :http://localhost:7001/odiconsole
    In my master repository i have just created Java EE agent in my master repository with weblogic context as:oraclediagent and port:7001 is WLS server port.
    Till now i have not created even single standalone agent.
    I took encoded password for my Java EE agent say JAVA_AGENT2 and modified in the odiparams file.
    i started the java agent and while testing the connection of this java agent i am getting following error.
    Agent Test failed.
    oracle.odi.runtime.agent.invocation.InvocationException: ODI-1425: Agent application cannot be reached using http://localhost:7001/oraclediagent.
         at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.reThrowAgentErrorAsInvocation(RemoteRuntimeAgentInvoker.java:932)
         at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:267)
         at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeIsAlive(RemoteRuntimeAgentInvoker.java:427)
         at oracle.odi.ui.action.SnpsPopupActionTestAgentHandler.actionPerformed(SnpsPopupActionTestAgentHandler.java:65)
         at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent.jButtonTestAgent_ActionPerformed(EditFrameSnpAgent.java:964)
         at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent.connEtoC2(EditFrameSnpAgent.java:200)
         at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent$IvjEventHandler.actionPerformed(EditFrameSnpAgent.java:148)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
         at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
         at java.awt.Component.processMouseEvent(Component.java:6263)
         at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
         at java.awt.Component.processEvent(Component.java:6028)
         at java.awt.Container.processEvent(Container.java:2041)
         at java.awt.Component.dispatchEventImpl(Component.java:4630)
         at java.awt.Container.dispatchEventImpl(Container.java:2099)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
         at java.awt.Container.dispatchEventImpl(Container.java:2085)
         at java.awt.Window.dispatchEventImpl(Window.java:2475)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
    Please help me to clarify my doubts & error.
    1) Before setting up an Java EE agent a standalone agent must be set up?
    2)If yes ,then odiparams needs to update for the standalone agent ?(i hope yes it is must)
    3)I will now start creating the java ee odi agent and then,should i updtae the encoded password of for this agent in the same odiparams.bat file?
    4)To create agents,data server,schema,respositoies which login name should i login i mean master repositoy login name/work repository login name?
    Please help me,
    Thanks,
    MNK

    Hi Dev,
    Thanks a for ur quick repply.
    Now i am able login into ODI console,when i click on any object like runtime,toplogy, the connection to server is falied i am getting and following error i have seen in the log
    <Oct 1, 2010 2:13:12 PM IST> <Error> <HTTP> <OFSCVR0188> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285922592453> <BEA-101019> <[ServletContext@20584931[app:odiconsole module:odiconsole path:/odiconsole spec-version:2.5]] Servlet failed with IOException
    weblogic.utils.NestedRuntimeException: Cannot parse POST parameters of request: '/odiconsole/faces/shell/UIShell.jspx'
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:2017)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:1897)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:1791)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getParameter(ServletRequestImpl.java:1868)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.access$800(ServletRequestImpl.java:1706)
         at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:794)
         at javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:169)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:137)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.odi.repex.view.main.auth.AuthMustFilter.doFilterInternal(AuthMustFilter.java:41)
         at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.odi.repex.view.main.auth.ThreadAuthFilter.doFilterInternal(ThreadAuthFilter.java:38)
         at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.net.SocketTimeoutException: Read timed out
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:177)
         at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:228)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:1991)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:1897)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:1791)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getParameter(ServletRequestImpl.java:1868)
         at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.access$800(ServletRequestImpl.java:1706)
         at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:794)
         at javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:169)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:137)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.odi.repex.view.main.auth.AuthMustFilter.doFilterInternal(AuthMustFilter.java:41)
         at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.odi.repex.view.main.auth.ThreadAuthFilter.doFilterInternal(ThreadAuthFilter.java:38)
         at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Any idea?
    Thanks,
    MNK

  • OES and WebCenter Integration And PEP API Issues

    Hi All,
    Currently we want to develop a WebCenter app which will check Authentication Policy in Oracle Entitlement Server using PEP API.
    We encountered some issues, and have following questions:
    1. According to PEP sample API, seems the PEP client application could only connect to the OES which is deployed on the same container context (same WLS domain).
    Is that possible for our PEP client application to connect to OES which is deployed on a different WLS domain or even remote WLS?
    2. Currently we deployed our WebCenter Spaces and OES on different WLS domains, is this a common pattern for WebCenter and OES integration?
    We got following error while starting up OES, after we try deploying OES 11.1.1.5.0 and WebCenter Portal 11.1.1.6.0 together on a WLS (10.3.5) domain.
    Any ideas? Thanks in advance.
    Thanks,
    Nicholas
    Caused By: oracle.mds.config.MDSConfigurationException: MDS-00035: cannot load the class: oracle.security.apm.rgx.mds.cust.SiteCC.
         at oracle.mds.config.CustConfig.getCustClassList(CustConfig.java:365)
         at oracle.mds.config.CustConfig.loadFromBean(CustConfig.java:277)
         at oracle.mds.config.CustConfig.<init>(CustConfig.java:242)
         at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:781)
         at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
         at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:491)
         at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:438)
         at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:516)
         at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:204)
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         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)

    Finally I found the error I got was because of the wrong version of JDeveloper and WebCenter extension.
    Portal apps which created by JDev 11.1.1.6.0 are not able to run on WebCenter 11.1.1.1.5, while the ones created by JDev 11.1.1.1.5 with WC extension 11.1.1.4.0.120306 work.
    Looks like it's not a good idea to mix FMW products of different version in a single project.

  • MQ/WebLogic Topology and Architecture

    I am new to MQ and am trying to get my head around a couple of basic "big
              picture" things; I'll explain what I think is going on and hopefully someone
              will jump in when I'm off in the weeds. I need to do is integrate a J2EE
              application with a legacy MQ system and as you might expect, I cannot alter
              that system, I must accommodate it (which J2EE is designed to do).
              MQ is designed to be distributed; the idea that you'll install an MQ Server
              on every Application Server machines seems like a special case. In my case,
              it's academic.
              First MQ itself:
              There appears to be some internal and proprietary things MQ needs to do for
              efficiency and possibly historical reasons. To achieve that, you must install
              an MQ Client on each machine so that access appears to be local for Applications
              that talk to MQ. I have written some code that talks directly to the server
              using some of the Client libraries and I was able to send but could not get
              messages off the queue; I found some documentation that said that this would
              be the case in some circumstances. I suspect that the reason for this is
              that I may have not used the "correct" client libraries since I found some
              example code that doesn't yet run (we can ignore that for now).
              The Client install does give you Java classes that provide connectivity and
              it implies JMS support but in what form, since the classes appear to use
              proprietary code?
              Does the Client have the ability to run as a JMS Server that appears to be
              a local JMS nexus that I can talk to with standard JNDI lookups?
              WebLogic J2EE Integration:
              The ultimate goal here is to integrate an existing MQ installation so I can
              send and recieve from a J2EE Application I am working on.
              I have been reading that there's at least three different ways to make this
              connection.
              1) Roll your own using the proprietary lib clients in a startup class
              2) Using WebLogic's Bridge technology
              3) Use WebLogic's Foreign Destination configuration.
              Detailed questions below by item number:
              1) -> I understand that directly using IBM's client libraries is supposed
              to function the same as running the Client locally, that doesn't sound like
              it would give the scalability of pooling and that solution won't route to
              drive MDBs.
              2) -> A lot of posts state that for WL/MQ integration this is not necessary.
              I don't know a lot about the specifics of what I will need to do to talk
              to this other system yet, I am just trying to get my head around the general
              cases.
              3) -> This is the most appealing to me since it sounds like it is a matter
              of using the WL console to set up the JMS destination once I have the correct
              libraries in the server's classpath. It would seem that the JMS queues look
              like they are local, I can drive MDBs from this with all the manageability
              built in. However, does the server use the same provider factory class as
              I would in my own code or are there special considerations?
              Comments and pointing to specific reading encouraged (don't just say, to
              read the 677 page Java MQ docs).
              Thanks

    Wow! All I can say is "Thanks", it's gonna take we a while to get through
              all this but I do appreciate the help. I tried to get the Client stuff installed
              on my Linux dev box but it's not clear which rpms are needed and some complained
              because I am still running RH7.3. I am in the process of moving to a supported
              platform RHEL3.x or above... stay tuned.
              Hello Tom,
              > Hi!
              >
              > If you haven't already done it, the best place to start is to read
              > through the entire "Integrating Remote JMS Providers" FAQ:
              >
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > I'm also appending my own integration notes which mention MQ (and
              > which you may have already run across). I update these notes from
              > time to time. Enjoy!
              >
              > Tom, BEA
              >
              > JMS Integration of Foreign Vendors with BEA WebLogic Server
              > -----------------------------------------------------------
              >
              > The following notes are derived mostly from
              > "http://dev2dev.bea.com/technologies/jms/index.jsp".
              >
              > For additional questions, a good forum for WebLogic questions in
              > general is "newsgroups.bea.com". These can be mined for information by
              > using Google's newsgroup search function.
              >
              > JMS Integration Overview
              > ------------------------
              > - For integration with "non-Java" and/or "non-JMS" platforms, see
              > "Non-Java Integration Options" below.
              >
              > - For a foreign JMS vendor to participate in a WL transaction it must
              > support XA. Specifically, it must support the javax.jms.XA*
              > interfaces.
              >
              > - In WL versions 6.0 and up it is possible to make synchronous calls
              > to foreign JMS vendors participate in a WL transaction as long as the
              > foreign vendor supports XA.
              >
              > - WL 6.0 and 6.1 MDBs can be driven by foreign vendors
              > non-transactionally. They can be driven transactionally by a select
              > few foreign vendors (MQ is not part of the select few)
              >
              > - WL 7.0 and later, MDBs can be driven by foreign vendors
              > transactionally and non-transationally.
              >
              > - WL 6.1 and later WL provides a messaging bridge feature. Messaging
              > bridges forward messages between any two JMS destinations, including
              > foreign destinations, and can transfer messages transactionally or
              > non-transactionally.
              >
              > - WL 8.1 JMS provides additional features that simplify transactional
              > and JNDI integration of foreign vendors. See
              > http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features and
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > Integration with 8.1 Details
              > ----------------------------
              > To start, first read the "Integrating Remote JMS Providers FAQ"
              > (released in Dec 2004) at:
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > A good overview of 8.1 JMS interop capability is the presentation
              > "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              >
              > http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/App
              > lication_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              >
              > This document refers to helpful new 8.1 features, which simplify
              > integration. These include:
              > http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_
              > foreign_providers
              > http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              > And are also summarized here (under interoperability):
              > http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              > Also read the MDB documentation, which extensively covers integrating
              > foreign vendors:
              >
              > http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              >
              > The 8.1 features are likely sufficient for most 8.1 integration needs,
              > but you may want to refer to the "Using Foreign JMS Providers With
              > WLS" white-paper mentioned below, which is 7.0 specific but contains
              > specific examples of configuring non-WebLogic JMS vendors. See also
              > notes on "MQ" below.
              >
              > Integration with 6.1 and 7.0 Details
              > ------------------------------------
              > Read the "Using Foreign JMS Providers With WLS" white-paper:
              >
              > http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              >
              > Note that this white-paper does not take into account 8.1 features.
              >
              > For 7.0 read the extensive 8.1 MDB documentation, which largely also
              > applies to 7.0:
              >
              > http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              >
              > Non-Java Integration Options
              > ----------------------------
              > - WL JMS has a JNI based C client which is available for Windows and
              > some UNIX platforms. This C client supports 7.0 and up, and will be
              > officially packaged with WLS in 9.0 (virtually unchanged). The C API
              > is currently only supported through the jms newsgroup. See "JMS C
              > API", here:
              >
              > http://dev2dev.bea.com/technologies/jms/index.jsp
              >
              > - WL supports direct Windows COM access through its "JCOM" feature.
              > This doesn't include the JMS API, but one can invoke EJBs which in
              > turn invoke JMS. See
              >
              > http://e-docs.bea.com/wls/docs61/jcom.html
              >
              > http://e-docs.bea.com/wls/docs70/jcom/
              >
              > http://e-docs.bea.com/wls/docs81/jcom/
              >
              > - Similar to JCOM, but more advanced and supported on more platforms,
              > WL supports access via the standard IIOP protocol. You can use the
              > BEA Tuxedo C client for this purpose (no license fee). This doesn't
              > include the JMS API, but one can invoke EJBs which in turn invoke JMS.
              > See
              > http://e-docs.bea.com/wls/docs81/rmi_iiop/
              > http://e-docs.bea.com/wls/docs70/rmi_iiop/
              > http://e-docs.bea.com/wls/docs61/rmi_iiop/
              > Unlike most other approaches, the IIOP client approach also allows the
              > client to begin and commit user (JTA) transactions (not configured).
              > - If you already have a BEA Tuxedo license, one option is communicate
              > through BEA Tuxedo (which has various APIs on Windows) and configure a
              > WebLogic Server to respond to these requests via the WTC bridge.
              > Search for "WTC" in the BEA docs. Unlike most other approaches, the
              > Tuxedo API approach also allows the client to begin and commit user
              > (JTA) transactions.
              >
              > - Another approach is to interop via web-service standards. Or even to
              > simply to invoke a servlet on the WL server using a basic HTTP call
              > from the client. These operation in turn can invoke the JMS API.
              > There is a white-paper on "Interoperability Study of BEA WebLogic
              > Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates
              > web-services here:
              > http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              >
              > - Yet another approach is to use a third party product that is
              > designed to wrap any JMS vendor. There are even open source
              > versions. In no particular order, here are some examples: Open3
              > WinJMS, CodeMesh, Active JMS, SpiritSoft
              >
              > - Finally, there are .NET/C/C++ integration libraries that are not
              > specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              >
              > Notes on MQ Remote Capable XA Clients
              > -------------------------------------
              > Until recently, IBM MQ JMS clients could not work transactionally
              > unless they were running on the same host as their MQ server. This is
              > a limitation unique to MQ that was relaxed with the introduction of
              > IBM's new "WebSphere MQ Extended Transactional Client". See:
              >
              > http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              >
              > The product is new, and for some reason, configuration of this client
              > seems to be tricky, even when WebLogic is not involved at all. Oddly,
              > the main sticking point seems to be simply making sure that class
              > paths refer to the required IBM jars:
              >
              > - Required on WLS where MQ objects are bound into JNDI:
              > com.ibm.mq.jar, com.ibm.mqjms.jar
              >
              > - Required only if MQ objects are bound into JNDI on a different
              > server: com.ibm.mq.jar
              >
              > If there are problems when using this client, first get it to work
              > using a pure IBM client without any BEA classes involved. Once that
              > is working, search the WL JMS newsgroup for answers and/or contact BEA
              > customer support.
              >
              > Notes on Oracle AQ Integration
              > ------------------------------
              > If problems are encountered integrating Oracle's built-in queuing
              > (Oracle AQ) JMS client, there is publicly available wrapper code that
              > can aid integrating AQ directly into MDBs, JMS, or the messaging
              > bridge. The solution is titled "Startup class to bind
              > AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is
              > posted to:
              >
              > http://dev2dev.bea.com/codelibrary/code/startupclass.jsp (older
              > version) http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer
              > version)
              >
              > Caveats:
              >
              > It may be that the solution doesn't directly support concurrent
              > consumers. Perhaps Oracle requires that concurrent consumers each
              > have a unique JMS connection? As a work-around, parallel message
              > processing can be achieved indirectly by forwarding AQ messages into a
              > WL JMS destination - which do support concurrent processing.
              >
              > Up-to-date versions of Oracle may be required. For more information,
              > google search the weblogic.developer.interest.jms newsgroup for
              > "Oracle" and "AQ".
              >
              > MDB Thread Pool Notes
              > ---------------------
              > WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to
              > specify which thread pool an MDB uses to run its instances. In most
              > cases this field should be configured to help address potential
              > performance issues and/or dead-locks:
              >
              > http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-
              > policy
              >
              > (Note that "dispatch-policy" is ignored for non-transactional foreign
              > vendors; in this case, the MDB "onMessage" callback runs in the
              > foreign vendor's thread.)
              >
              > MDB Concurrency Notes
              > ---------------------
              > Queue MDBs driven by foreign providers can run multiple instances
              > concurrently. Topic MDBs driven by foreign providers are limited to
              > one instance (not sure, but transactional foreign driven topic MDBs
              > may not have this limitation). The size of the thread pool that the
              > MDB runs in and the "max-beans-in-free-pool" descriptor limit how many
              > instances run concurrently.
              >
              > Design Guide-Lines and Performance Tuning Notes
              > -----------------------------------------------
              > The "WebLogic JMS Performance Guide" white-paper contains detailed
              > design, performance, and tuning information for Clustering, Messaging
              > Bridge, JMS, and MDBs.
              >
              > http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD
              > .jsp
              >

  • Oracle Portal and Discoverer Integration

    Portal Version: 9.0.2.0.1
    RDBMS Versjion: 9.0.1.3
    OS/Vers. Where Portal is Installed:: Suse 7 SLES
    Error Number(s)::
    Oracle Portal and Discoverer Integration
    We're trying to integrate Discoverer with Portal unsuccessfully.
    We made many things in accordance with oracle's documentation until add discoverer portlets (worksheet and list of workbooks) in a test page.
    In view mode, the worksheet portlet shows the error:
    "The portlet has not been defined. The publisher must define the portlet by clicking on Edit Defaults for the portlet on the edit mode of this page. Please contact the publisher of this page."
    We think we have to edit properties before. Is this? Anyway edit worksheet portlet crashes between step 1 and 2. The error is: "The listener returned the following Message: 500 Internal Server Error".
    We have a public conection created in EM and a discoverer application which can be viewed using plus or viewer.
    Furthermore, it's not possible delete the added portlets neither the page that contain it. The error at delete is:
    Error: An unexpected error occurred: User-Defined Exception (WWC-44082)
    (WWC-00000)
    An unexpected error has occurred in portlet instances: User-Defined Exception (WWC-
    44846)
    An unexpected error occurred: User-Defined Exception (WWC-43000)
    The following error occurred during the call to Web provider:
    oracle.portal.provider.v2.PortletNotFoundException
    at oracle.portal.utils.v2.ContainerException.fillInStackTrace(Unknown Source)
    at java.lang.Throwable.<init>(Throwable.java:78)
    at java.lang.Exception.<init>(Exception.java:29)
    at oracle.portal.utils.v2.ContainerException.<init>(Unknown Source)
    at oracle.portal.provider.v2.PortletException.<init>(Unknown Source)
    at oracle.portal.provider.v2.PortletNotFoundException.<init>(Unknown Source)
    at oracle.disco.portlet.provider.DiscoPortletPersonalizationMgr.destroy
    (DiscoPortletPersonalizationMgr.java:65)
    at oracle.portal.provider.v2.DefaultPortletInstance.deregister(Unknown Source)
    at oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter.deregisterPortlet
    (Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.doMethodCall(Unknown Source)
    at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.processInternal(Unknown Source)
    at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.process(Unknown Source)
    at oracle.webdb.provider.v2.adapter.SOAPServlet.doSOAPCall(Unknown Source)
    at oracle.webdb.provider.v2.adapter.SOAPServlet.service(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
    at com.evermind.server.http.ResourceFilterChain.doFilter
    (ResourceFilterChain.java:59)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
    at com.evermind.server.http.ServletRequestDispatcher.invoke
    (ServletRequestDispatcher.java:523)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
    (ServletRequestDispatcher.java:269)
    at com.evermind.server.http.HttpRequestHandler.processRequest
    (HttpRequestHandler.java:735)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
    (WWC-43147)
    Edit properties for portlet List of Workbook works but in view mode we have the error in the portlet area:
    "Failed to refresh portlet. Please verify that the information used to create the
    portlet instance or customization is still valid. Otherwise, please contact your
    iAS administrator. oracle.discoiv.controller.FatalControllerException:
    DiscoNetworkException - Nested exception: org.omg.CORBA.OBJECT_NOT_EXIST: minor
    code: 0 completed: No null"
    Any ideas?
    Thanks

    Hi there,
    Have you applied any patches to 9ias since it was first installed? We had the same problem and had to apply a couple of patches to get the portlets working.
    1. Apply the 9.0.2.53.16 one-off patch for Oracle 9iAS Discoverer which takes Discoverer up to 9.0.2.53.16. This patch appears to be password protected and you need to get someone at Oracle support to give you a password.
    2. Apply the Discoverer Portlet Provider: 9.0.2.53.00c patch (patch no. 2595444) which gives you a new discportal.xsl file that actually works. It's this second step that solves your problem but you need to do step 1 before this. This is password protected as well.
    3. As you've upgraded Disco on the server to 9.0.2.53, you'll need to upgrade Disco Admin & Desktop within your 9iDS installation using patch no. 2555265. This is because Disco 9.0.2.53 uses an upgraded EUL that Disco Admin & Desktop need to be patched to use.
    This was the course of action Oracle support advised us about nine months ago. Of course they may have released a further patch to Disco that does 1 & 2 in one go, but we regularly carry out steps 1 and 2 on servers we use and we can use the Disco portlets successfully.
    Hope this helps
    Mark Rittman
    [email protected]

  • Question regarding MM and FI integration

    Hi Experts
    I have a question regarding MM and FI integration
    Is the transaction Key in OMJJ is same as OBYC transaction key?
    If yes, then why canu2019t I see transaction Key BSX in Movement type 101?
    Thanks

    No, they are not the same.  The movement type transaction (OMJJ) links the account key and account modifier to a specific movement types.  Transaction code (OBYC) contains the account assignments for all material document postings, whether they are movement type dependent or not.  Account key BSX is not movement type dependent.  Instead, BSX is dependent on the valuation class of the material, so it won't show in OMJJ.
    thanks,

  • Facebook and Twitter integration not working

    I'm have trouble using Facebook and Twitter integration in Mountain Lion. When I click 'Click to Tweet', or 'Click to Post', nothing happens; I don't get the notecard looking thig, and it's like I never clicked the button. Same thing with sharing from an app, except for Twitter. I receive notifications from both just fine, but I'm unable to post. I can tweet something from the sharing menu (link to a webpage with Safari, for example), but I cannot send a tweet using the 'Click to Tweet' button in Notification Center. Also, I cannot post to Facebook by neither sharing nor the 'Click to Post' button. So far I have tried sharing with Safari, Finder, and Preview, all with the same results. (Facebook sharing with iPhoto does work, but I don't believe that is integrated with OS X.)
    I have also tried the following, with no luck:
    Checked my settings on the Facebook and Twitter sites.
    Removed my acounts and re-added them.
    Obviously, my internet connection is working.
    Added my Facebook account to the 'Guest User' account, and another administrator account.
    Had a friend add his Facebook account to his own (limited) account on my computer--he could not post to Facebook either.
    I believe the last two things I tried indicate that this is a system-wide problem. A couple more things to note: 1) there is no kind of error message; it just sits there, like nothing happend, no 'spinning wheel' or anything. 2) It DID work before. Twitter worked when I first upgraded to Mountain Lion, and Facebook worked when I installed the 10.8.2 update. I don't use either often enough to know when exactly they stopped.
    Here is a video illistrating my problem.
    It's been driving myself crazy with this over the past few days, and can't seem to find an answer anywhere. I also seem to be the only one with this problem.

    First, I would eject whatever it is that you downloaded. Go to Finder and eject it that way or depending how you have your system set up, do the two finger tap and Eject it. Download the link above. Once it downloads, double click it to install it. It should work. If it doesn't you need to use your Disk Utility to check for errors. Click your Finder again and then Applications. Scroll down to Utilities and then Disk Utility. Click on your hard drive and you will get a menu of items on the right side. Towards the bottom, you will see a button to Verify Disk Permissions. Click that and let it run. It may take a few minutes to finish. Once it's finished there may be a list of things wrong with your system. Click the Repair Permissions and let the computer do it's thing. Use Disk Utility at least once a month to make sure everything is in order on your system. If this doesn't fix it, I don't have any other suggestions. I'd hate to say do a fresh install but that might be the next step if this doesn't work.
    Something else to consider is that is if you use Time Machine and the system did work at one point, you could go back to the last known good point and reinstall that back-up. You would lose anything you have saved since that point (obviously). If you take steps to back up your information, that should not be an issue. (For me), Time Machine works as advertised. If you are not backing system up regularly, shame on you. You need to start ASAP backing up. It's an easy process and it's times like you are having now, that make the small preventive maintenance, worth extra time and effort.
    Good luck.

Maybe you are looking for