OAM lost pswd mgmt

If the "Change on Reset" is checked in the password policy, when a user with expired/temporary password tries to login to a application, he will be redirected to the password change page. User provides temporary password and new password and clicks submit, the user gets to a confirmation page that password is changed. The confirmation page has a ok button. When the user click the ok button, the user is redirected to the application homepage with a valid obssocookie. This is out of the box functionality.
If we want the user to be redirected to login page after after clicking the ok on the confirmation page, what would be the best way to do this?
Thanks
VS

Hi VS,
It is very useful to have an xml tool such as XML Spy (there are also free utilities, such as Exchanger) so that you can validate the XSL, and directly see the effect of applying it to XML without using the WebPass/Identity Server.
To get the XML, you can add the parameter &format=xmlnoxsl to the url in the relevant WebPass page (in this case the Change Password screen) so that you can copy it into the xml tool for testing.
Regards,
Colin

Similar Messages

  • OAM lost pswd mgmt stylesheet issue

    We are getting stylesheet error after making changes to lpm_changepwd.xsl. How do we go about troubleshooting it? We are able to open the the xsl file in IE and see the content.
    Thanks.
    VS

    Hi VS,
    It is very useful to have an xml tool such as XML Spy (there are also free utilities, such as Exchanger) so that you can validate the XSL, and directly see the effect of applying it to XML without using the WebPass/Identity Server.
    To get the XML, you can add the parameter &format=xmlnoxsl to the url in the relevant WebPass page (in this case the Change Password screen) so that you can copy it into the xml tool for testing.
    Regards,
    Colin

  • OAM Lost Password Page customization

    I need to add extra text to the lost passwd mgmt page. I need to add some text after following standard text.
    Please answer your Challenge Question :
    http://<host>/identity/oblix/apps/lost_pwd_mgmt/bin/lost_pwd_mgmt.cgi?backUrl=http://<host>/identity/oblix/apps/userservcenter/bin/userservcenter.cgi
    I looked style sheet but couldn't figure out anything. can anyone please guide me how to customize the lost passwd mgmt page?
    Thanks

    You can use lpm_cr.xsl to customize LPM Challenge response page.
    Harish Jangada

  • OAM Lost Password Management Error

    I keep getting the same error: "Response does not match the stored response" in oblix log. Also I always find "@1#" string added to my question?
    Did anyone face this issue? I have AD as ldap and OAM 10.1.4.2 BP10. Pls let me know.

    Hi,
    Below are the LPM Policy configurations:
    Challenge Pharse Source : Predefined
    Predefined Challenges Phrases: 5 Questions
                   1) What is the name of your first school?
                   2) What is your mother's maiden name?
                   3) What is your fav color?
                   4) What is your favourite movie?
                   5) What is your favourite place to visit?
    Minimum Challenges to configured: 2
    Challenge Response Minimum Length : 1
    Minimum challenges to be answered: 2
    Challenge Post Type : All at once
    Enable the LPM.
    When an User access the protected application for the first time, he/she is challenged to set his/her 2 CQ out of 5 (Lets say What is your fav color and what is your favourite movie is selected) provided with the responses for 2 CQ's.
    In the Backend directory Server (AD,OID,SunOne Iplanet,OVD) the above Challenge questions were saved in the format of what is your fav color?@1#what is your favourite movie?@2#
    Response values will be in encrypted form in OID.
    Regards,
    Ajay

  • OAM: Lost Password Management

    I am having hard time configuring challenge and response attributes in OAM. We have OAM 10.1.4.3 Identity server running with AD 2003 as LDAP server.
    We added two new attributes: Challenge and response as Case insensitive and Case Sensitive String in AD with challenge and response semantic types.
    Now for some wierd reasons I always get two errors:
    1. We always see "@1#" appending to challenge questions.
    2. Everytime it reports as Invalid response even if we type right answer.
    Did I miss anything in configuration part? Pls let me know.

    Any one to reply on this-

  • OAM Lost password confirmation page

    Hi,
    I am working with 10.1.4.2 and need to customize lost password app pages , i have changed lpm_changepwd.xsl for GUI changes ,but not able to figure out how to remove or modify confirmation page post change password . currently , I get "User Application" and your password has been changes with Back button.
    Please provide any detail if anyone has done UI customization.
    regards,
    Tom

    You can use lpm_cr.xsl to customize LPM Challenge response page.
    Harish Jangada

  • IDXML for LostPassword and Reset Password

    HI All,
    I am new to IDXML and OAM Webpass, but I have tried my best to work on assignment. I have to implement User Credentials Mgmt. which includes Change Password, Reset Password, AddUpdateSecurityQuestions and Lost Password.
    I have found IDXML for Change password and Adding or updating Security Questions and implement it. But I am not able to find any IDXML for Lost PAssword Mgmt. or Reset Password.
    I have read something about Lost Password Mgmt in OAM Manual but it was for implementing Event Plugin - which I am totally unaware of.
    I will really appreciate if Somebody reply soon, as I am running out of time...tic..tic..tic....
    see... I have very less time.... :)
    Please help..
    Thanks in Adv.

    Hello Himanshu,
    The functionality of LPM is not directly available within IDXML (specifically the functionality provided by the lost_pwd_mgmt.cgi urls is not available). However, you can use IDXML to check for LPM conditions and then take appropriate action as an admin user.
    For example, you could make a check for password reset by checking the value of the obpasswordchangeflag attribute with an IDXML call that logs in with an admin account (so that the user is not redirected to the change password page). Then, if the value is true you could make another admin call to change the password and to reset the obpasswordchangeflag.
    In order to do this, you first need to make the LPM attributes available to the Identity System, for which please see Note 743075.1
    Regards,
    Colin

  • Recovering from a lost EM OMS MGMT server?

    We recently had a disaster where we lost our enterprise mgr OMS. We were running the OMS version 10.2.0.4 on linux x86 and our agents are also running on linux and they are the 10.2.0.4 agents.
    So long story short, we have to rebuild the mgmt station and I am wondering if I will need to reinstall the agents or will they be able to register with the new OMS

    Hi,
    If the new installation is having same "old name" and port then I guess,you don't have to make any changes.
    If it's different name,You can refer to metalink ID 413228.1,for relocating agents.

  • Multi Language support for lost password management in OAM

    We are trying to implement lost password management with multi-language support. We have updated lpm_changepwd.xsl for UI changes. Some of the text on the password change screen come for the lpm_changepwd.xsl. How can we have the text on the password change screen in multiple language?
    Thanks.
    Vinay

    Was able to do it by adding new files to the shared folder and updating the style in the lang folder to point to the new files.

  • What is the diff? OI Mgmt, OI Mgr, OAM?

    Hi,
    I'm new to FMW and confused by all the offerings.
    Can someone tell me in a few words what the difference is between these 3 technologies?
    - Oracle Identity Management
    - Oracle Identity Manager
    - Oracle Access Manager
    Based on what I see...
    - Oracle Identity Management is a product under OAS.
    - Oracle Identity Manager is a product under Oracle Identity Management.
    - Oracle Access Manager is a product under Oracle Identity Manager.
    Am I correct or close or out to lunch?
    Thanks!

    Hi
    This is how I understand how the products relate to each other:
    Oracle Identity Management isn't an actual product it's an umbrella term Oracle use to describe all the Oracle Identity and Access Management products. Please take a look at the link below:
    http://www.oracle.com/technology/products/id_mgmt/index.html
    Oracle Identity Manager and Oracle Access Manager are seperate products.
    Oracle Identity Manager is a provisioning and compliance product formerly Xellerate Identity Manager from Thor.
    Oracle Access Manager is a authentication and access product used for securing and providing single sign on to web based applications.
    Both products have many other features besides what's described above some of these features overlap such as workflow, user self service and password management.
    Hope this helps.
    Michael Barrow
    Identity Management Consultant

  • Adobe Edge (.oam file) interaction problem with Muse

    I created a edge animate file which has a parallax scrolling feature in it. When I scroll, the items move. But when I load the animation's .oam fle from muse, the animation losts its scrolling effect. How can I solve this?
    (PS:I used Edge Commons to create the effect)
    (Any other suggestions for creating parallax effects with muse?)

    Hello,
    Please double click on the symbol and make sure "autoplay " is unchecked in the stage properties. then republish the OAM file and then try.
    If the issue still persist please share the compressed project file with us to take a look at it.
    Regards
    Vivek

  • Error when trying to access OAM 11g Admin console

    I am getting an error when I try to access the OAM admin console, the page appears after I enter http://hostname:14100/oam but the login box has the following message in it:
    System error. Please re-try your action. If you continue to get this error, please contact the Administrator.
    I tried entering http://hostname:14100/oam_console but get a 404 error
    The log file outputs the following:
    [oracle@core bin]$ startManagedWebLogic.sh oam_server1
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=512m
    WLS Start Mode=Production
    CLASSPATH=/opt/oracle/product/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar::/opt/oracle/product/Middleware/Oracle_IDM1/oam/server/policy/sts-policies.jar:/opt/oracle/product/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/oracle/product/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/oracle/product/Middleware/jdk/lib/tools.jar:/opt/oracle/product/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/product/Middleware/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/product/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/opt/oracle/product/Middleware/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/product/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/product/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/product/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/opt/oracle/product/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/opt/oracle/product/Middleware/Oracle_IDM1/oam/agent/modules/oracle.oam.wlsagent_11.1.1/oam-wlsagent.jar:/opt/oracle/product/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/opt/oracle/product/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/product/Middleware/wlserver_10.3/server/lib/xqrl.jar
    PATH=/opt/oracle/product/Middleware/wlserver_10.3/server/bin:/opt/oracle/product/Middleware/modules/org.apache.ant_1.7.1/bin:/opt/oracle/product/Middleware/jdk/jre/bin:/opt/oracle/product/Middleware/jdk/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/Oracle/bin:/opt/oracle/product/Middleware/user_projects/domains/iam/bin:/opt/oracle/product/Middleware/OPatch:/opt/oracle/product/11.2.0/dbhome_1/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)
    Starting WLS with line:
    /opt/oracle/product/Middleware/jdk/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=512m -Dweblogic.Name=oam_server1 -Djava.security.policy=/opt/oracle/product/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/opt/oracle/product/Middleware/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/opt/oracle/product/Middleware/wlserver_10.3 -Dwls.home=/opt/oracle/product/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/oracle/product/Middleware/wlserver_10.3/server -Dcommon.components.home=/opt/oracle/product/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/opt/oracle/product/Middleware/user_projects/domains/iam -Djrockit.optfile=/opt/oracle/product/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/servers/oam_server1 -Doracle.domain.config.dir=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig -Digf.arisidbeans.carmlloc=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/carml -Digf.arisidstack.home=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/opt/oracle/product/Middleware/user_projects/domains/iam/servers/oam_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/opt/oracle/product/Middleware/Oracle_IDM1/oam/agent/modules/oracle.oam.wlsagent_11.1.1,/opt/oracle/product/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/opt/oracle/product/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -DOAM_POLICY_FILE=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/oam-policy.xml -DOAM_CONFIG_FILE=/opt/oracle/product/Middleware/user_projects/domains/iam/config/fmwconfig/oam-config.xml -DOAM_ORACLE_HOME=/opt/oracle/product/Middleware/Oracle_IDM1/oam -Doracle.security.am.SERVER_INSTNCE_NAME=oam_server1 -Does.jars.home=/opt/oracle/product/Middleware/Oracle_IDM1/oam/server/lib/oes-d8 -Does.integration.path=/opt/oracle/product/Middleware/Oracle_IDM1/oam/server/lib/oeslib/oes-integration.jar -Does.enabled=true -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConnectionFactoryImpl -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djavax.xml.soap.SOAPFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl -Doracle.oaam.home=/opt/oracle/product/Middleware/Oracle_IDM1/oaam/ -Doracle.oaam.home=/opt/oracle/product/Middleware/Oracle_IDM1/oaam/ -Doracle.oaam.home=/opt/oracle/product/Middleware/Oracle_IDM1/oaam/ -Djava.awt.headless=true -Dem.oracle.home=/opt/oracle/product/Middleware/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://core.apteclabs.edu:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/opt/oracle/product/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/opt/oracle/product/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
    [WARN ][jrockit] MaxPermSize=512m ignored: Not a valid option for JRockit
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    <Aug 16, 2011 9:34:29 AM EDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Aug 16, 2011 9:34:36 AM EDT> <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>
    <Aug 16, 2011 9:34:37 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64 from Oracle Corporation>
    <Aug 16, 2011 9:34:45 AM EDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <Aug 16, 2011 9:34:54 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Aug 16, 2011 9:37:45 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Aug 16, 2011 9:37:45 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Aug 16, 2011 9:38:02 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/oracle/product/Middleware/user_projects/domains/iam/servers/oam_server1/logs/oam_server1.log is opened. All server side log events will be written to this file.>
    Aug 16, 2011 9:38:25 AM oracle.security.am.common.nap.util.NAPLogger log
    SEVERE: Failed to communicate with any of configured Access Server, ensure that it is up and running.
    <Aug 16, 2011 9:38:27 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Aug 16, 2011 9:38:52 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Aug 16, 2011 9:38:52 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Aug 16, 2011 9:39:28 AM EDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in /opt/oracle/product/Middleware/Oracle_IDM1/oam/agent/apps/oam-wlsagent-logout.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.>
    <Aug 16, 2011 9:39:46 AM EDT> <Warning> <Coherence> <BEA-000000> <2011-08-16 09:39:46.790/320.434 Oracle Coherence GE 3.5.3/465p2 <Warning> (thread=DistributedCache, member=3): Assigned 257 orphaned primary partitions>
    [EL Info]: 2011-08-16 09:39:47.585--ServerSession(474132858)--EclipseLink, version: Eclipse Persistence Services - 1.1.0.r3634
    [EL Info]: 2011-08-16 09:39:48.526--ServerSession(474132858)--file:/opt/oracle/product/Middleware/Oracle_IDM1/oam/server/lib/oes-d8/jps-internal.jar-JpsDBDataManager login successful
    <Aug 16, 2011 9:40:01 AM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Aug 16, 2011 9:40:01 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Aug 16, 2011 9:40:01 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Aug 16, 2011 9:40:02 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.184.128:14100 for protocols iiop, t3, ldap, snmp, http.>
    <Aug 16, 2011 9:40:02 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:20c:29ff:fe26:71ec:14100 for protocols iiop, t3, ldap, snmp, http.>
    <Aug 16, 2011 9:40:02 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:14100 for protocols iiop, t3, ldap, snmp, http.>
    <Aug 16, 2011 9:40:02 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:14100 for protocols iiop, t3, ldap, snmp, http.>
    <Aug 16, 2011 9:40:02 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "oam_server1" for domain "iam" running in Production Mode>
    <Aug 16, 2011 9:40:04 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Aug 16, 2011 9:40:04 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Aug 16, 2011 9:43:32 AM EDT> <Error> <HTTP> <BEA-101017> <[ServletContext@477181353[app:oam_server module:oam path:/oam spec-version:2.5]] Root cause of ServletException.
    weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
    index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
    ^----^
    index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
    ^----^
    index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
    ^----^
    index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
    ^----^
    index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
    ^----^
    index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
    ^----^
    at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
    at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
    Truncated. see log file for complete stacktrace
    >
    <Aug 16, 2011 9:43:32 AM EDT> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'oam_server1' has triggered at Aug 16, 2011 9:43:32 AM EDT. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    WatchData: DATE = Aug 16, 2011 9:43:32 AM EDT SERVER = oam_server1 MESSAGE = [ServletContext@477181353[app:oam_server module:oam path:/oam spec-version:2.5]] Root cause of ServletException.
    weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
    index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
    ^----^
    index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
    ^----^
    index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
    ^----^
    index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
    ^----^
    index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
    ^----^
    index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
    <%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
    ^----^
    at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
    at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
    at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:416)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:326)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:265)
    at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
    at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = core.apteclabs.edu TXID = CONTEXTID = 11d1def534ea1be0:7f0631a0:131d2d0d910:-8000-0000000000000020 TIMESTAMP = 1313502212548
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 30000
    >
    <Aug 16, 2011 9:43:51 AM EDT> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in /opt/oracle/product/Middleware/user_projects/domains/iam/servers/oam_server1/adr/diag/ofm/iam/oam_server1/incident/incdir_8 with a lockout minute period of 1.>
    Any ideas?

    Hi,
    Another way to "find" the URL for the oamconsole, that I use if I'm not familiar with the configuration I'm working on is to first log into the Adminserver WL Console, then go to "Deployments".
    Then, find "oamconsole" in the Deployments listed (on the right).
    Click on that, then on the next page, look for the "Testing" tab. Click on the "Testing" tab, which which show the /oamconsole app.
    Click on the "+" to expand the tree, and you should see a bunch of different URLs on the right, e.g., if you have OAM console deployed to managed servers, etc., there'll be different URLs for those, etc., and you can just click on the links to open up OAM Console in your browser.
    Jim

  • OAM customization error

    I wanted to change the font colour of user manager application to red.To get this done i followed the instructions given in the document.the steps have been done in the process are as below.
    2.5.1 Prerequisites to Customizing Styles
    Be sure to complete the following prerequisites before you start to customize a style. This enables you to keep the original Classic Style (\style0) intact for reference and in case you need to return to it as a last resort.
    To prepare to customize styles
    As an Identity Administrator, add your own named style as described in the Oracle Access Manager Identity and Common Administration Guide.
    The original style stays in effect until an Identity Administrator makes your style the new system default.
    As an Identity Administrator, select the new style as the default style so that you can see the effect of any changes you make.
    2.5.2 Customization Facts
    Style Updates and Maintenance: Default wrapper files in \style0 and default global stylesheets in \shared are periodically updated to instantiate improvements through patches and product upgrades.
    The Release Notes notify you when such updates occur so you can propagate the changes to your custom styles. Oracle recommends that you compare the new file with your custom file and propagate any changes to your custom styles. It is risky to overwrite a default style with a customized style that bears the same name.
    Be sure to record the changes you make and the files that are involved so you can more quickly update custom stylesheets when you update default styles.
    Custom Directory: Stylesheet customization should occur only within your custom directory. Customized stylesheets must reside in your custom directory and relative pointers in all files must point to the files in your custom directory, not to files in \shared.
    Registration Files: As discussed in "General Content of Registration Files", a common registration file and each application's registration file contain the names of the stylesheets and schema files needed to present pages for the application. For example, when you look at the User Manager registration file in identity\oblix\apps\userservcenter\userservcenterreg.xml, you can see the application name and the names of the stylesheets the application calls during the completion of various functions.
    Also, given the application and the program name, you can locate the corresponding schema file name in the application's registration file.
    Oracle recommends that only experienced developers using extreme care consider editing a registration file. Registration files are covered in more detail at "Registration Files".
    Pointers: All wrapper files and stylesheets contain pointers as include statements that call another file. Most of these pointers are relative pointers that indicate where within the directory structure the file is without providing an absolute path name.
    For example, when you look at the usc_profile.xsl stylesheet called by User Manager functions, you can see that it contains include statements with relative pointers that call the following files:
    ./basic.xsl
    ./selectorinfo.xsl
    ./usc_searchform.xsl
    ./usc_navbar.xsl
    When you change the location of a file (place a copy of a stylesheet in your custom directory for customization), pointers to this file (whether relative or absolute) must be changed to reflect the new location in every file that calls it. All relative pointers in a stylesheet should point to files in your custom directory.
    In addition, many stylesheets contain relative pointers to object files. If Oracle Access Manager cannot instantiate an object when the page is loaded, unexpected behavior may result. All relative pointers to object files should be absolute pointers, as discussed in "Editing Stylesheets".
    Wrapper Files: Wrapper files include pointers to actual stylesheets in \shared. However, you cannot be assured that a wrapper file is called before the stylesheet because both the common registration file and the application's own registration file call stylesheets according to an internal ordering. For this reason, all wrapper files in your custom directory must be overwritten by a copy of the corresponding default stylesheet from the \shared directory.
    Important:
    Customizing stylesheets is an iterative process. Attempting to copy the entire contents of \shared into your custom directory at one time produce an error.
    Rather than copying all stylesheets at once, you start by investigating registration files to learn which functions (programs) call which stylesheets. You then selectively copy base stylesheets and a function-related stylesheet into your custom directory to overwrite their wrapper files, as discussed in "Copying Stylesheets to Your Custom Directory". You then customize and test the style for that function. When this returns satisfactory results you repeat the process to customize another function.
    2.5.3 Customization Guidelines
    The following guidelines should help ensure a successful customization.
    Retain all original files in the \style0 and \shared directories in pristine condition and store them safely for future use. Also, make a backup copy of your customized style files so that patches won't disrupt your customization.
    Record all changes you make and the files that are affected.
    Customize and test your new styles in a non-production environment before migrating them to your production environment.
    Important:
    Oracle recommends that you do not modify original style files in the \shared or \style0 directories. These may be overwritten by patch updates and product upgrades or you may want to refer to them later.
    When you use only one style, consider breaking the dependence on stylesheets in the \shared directory (again, to prevent patch\release updates to \style0 and \shared from disrupting customizations). This means that no stylesheet in your custom directory should inherit from or reference a stylesheet in \shared or \style0.
    When you use multiple custom styles, consider the pros and cons of sharing customizations between multiple custom styles with implementing individual customizations for each custom style. For example:
    Two styles that share the same stylesheet: When two custom styles (custom_style1 and custom_style2) can share the same stylesheet you may be tempted to customize the stylesheet in the \shared directory despite the risk of having your custom style overwritten by an updated stylesheet in a product patch or upgrade.
    Two individual styles: When two custom styles (custom_style1 and custom_style2) require their individually customized stylesheets you use the standard methodology and overwrite the wrapper files in your custom directory with the corresponding stylesheets in \shared.
    Consider using parameter stylesheet files for a custom style collection, rather than using hard-coded values (tab id's, attribute names, table/link properties, and so on); this is similar to how program code is written using header files.
    2.5.4 Customization Methodology Checklist
    As mentioned earlier, customization is an iterative process and more of an art than a science. This Guide does not attempt to give precise instructions for getting the presentation you want. Instead, this section outlines the recommended approach for a minor change.
    Important:
    Oracle recommends that you focus on stylesheets for one function at a time. Attempting to copy all stylesheets from \shared into your custom style directory results in an error.
    Table 2-28 Customization Methodology Checklist
    Check Action Description
    Add a New Style
    See the Oracle Access Manager Identity and Common Administration Guide for details about adding a style and selecting your new style as the default.
    Choose a Function to Customize
    Decide which function to customize first. Oracle recommends that you customize stylesheets related to one function at a time.
    Copy Selected Stylesheets into Your Custom Directory
    Copy selected stylesheets from \shared to your custom directory to overwrite corresponding wrapper stylesheets:
    Base stylesheets
    Stylesheets included in base stylesheets
    A function-related stylesheet identified in application registration file
    Function-related stylesheets identified in oblixbasereg.xml
    Customize Stylesheets in Your Custom Directory
    Change relative pointers in copied stylesheets to point to files in your custom directory.
    Change relative pointers to objects to absolute pointers.
    Complete other changes to implement the function's customization.
    Record Your Work
    Keep a record of the files you change and the changes you make.
    Copy Your Custom Directory Structure to WebPass
    Build a custom directory structure on WebPass and copy customized styles and images into it.
    Note: On WebPass, stylesheets are used only for client-side processing and are not required for server-side processing.
    Test Your Customized Style
    Test the customized style and make any alterations you need to the stylesheets in your custom directory.
    Record the changes.
    Customize Another Function
    Repeat this process on a function by function basis:
    Choose a function.
    Copy related stylesheets from \shared to your custom directory.
    Customize pointers and styles.
    Record and test your work.
    Propagate the Customized Style
    When you have copied and customized all stylesheets for the application, copy the custom style directory to all Identity Servers and WebPass hosts in your environment.
    2.6 Customizing the Identity System Pages
    This example shows a method for changing the way a page looks, without changing what it does. The change is a simple font color alteration for a specific page in one application. After making the change you must verify that the change is successful. When you finish this functional customization, you must create the same custom style directory structure on WebPass and copy all image files into it so WebPass can display the appropriate images in response to queries. You then test the implementation.
    The following topics demonstrate one sequence in the "Customization Methodology Checklist". You can complete the following procedures to gain first-hand experience:
    Task overview: Customizing Identity System pages includes
    Completing Prerequisites
    Choosing a Function to Customize
    Copying Stylesheets to Your Custom Directory
    Editing Stylesheets
    Copying Images and Styles to WebPass
    Testing Your Customized Style
    Propagating Styles
    See also:
    For details about localizing messages, see "Localizing XSL Files".
    2.6.1 Completing Prerequisites
    A prerequisite to customizing a style is to add a style and select the new style as the default, as described in the Oracle Access Manager Identity and Common Administration Guide. The resulting files and file structure provide the foundation for your customization.
    Suppose you added a new style named Pastel in a directory named Pastel and requested files be copied from Classic Style (in directory \style0).
    To confirm the results of adding a new style
    Add a style and select it as the default, as described in the Oracle Access Manager Identity and Common Administration Guide.
    New Custom Directory: Oracle Access Manager creates a directory that duplicates \style0 for the default language, English. If you have installed a Language Pack for French, Oracle Access Manager also creates a directory that duplicates \style0 in the French language directory.
    Locate your new custom directory.
    For example:
    Identity_install_dir \identity\oblix\lang\en-us\Pastel
    Identity_install_dir \identity\oblix\lang\fr-fr\Pastel
    Wrapper Stylesheets: Your custom directory contains wrapper stylesheets that point to actual stylesheets in another directory. If you selected the Classic Style to copy from, your custom directory duplicates the content of the \style0 directory.
    Open a wrapper stylesheet in your new custom directory, basic.xsl, and review the files that it includes.
    For this example:
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\basic.xsl
    <?xml version="1.0" ?>
    - <!-- Copyright (c) 1996-2005, Oracle Inc. All Rights Reserved.
    -->
    - <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
    <xsl:include href="./style.xsl" />
    <xsl:include href="../msgctlg.xsl" />
    <xsl:include href="../../shared/basic.xsl" />
    </xsl:stylesheet>
    The basic.xsl wrapper stylesheet includes the following three files:
    style.xsl file in your custom directory
    msgctlg.xsl, one directory up from your custom directory (in identity\oblix\lang\en-us)
    basic.xsl in identity\oblix\lang\shared
    Locate and review the content of the basic.xsl stylesheet in \shared.
    For example:
    Identity_install_dir\identity\oblix\lang\shared\basic.xsl
    <?xml version="1.0" ?>
    - <!-- Copyright (c) 1996-2002, Oblix Inc. All Rights Reserved. -->
    - <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
    <xsl:include href="obstringutil.xsl" />
    - <!-- xsl:output indent="no"/ -->
    <xsl:include href="font.xsl" />
    <xsl:include href="title.xsl" />
    The basic.xsl stylesheet in the \shared directory includes additional files (font.xsl, title.xsl, obstringutil.xsl) and provides templates to define attributes and status and control display information. See "basic.xsl" for more information.
    During your customization process, you copy selected stylesheets from the \shared directory into your custom directory. This overwrites wrapper files with corresponding stylesheets you can then edit in your custom directory.
    New Custom XML Document: In addition to the custom directory structure, when you select the new custom style as the default style, Oracle Access Manager creates an XML document (a duplicate of style0.xml) named after the directory you created.
    Locate and open the custom xml document that was created when you added the new style.
    For this example:
    Identity_install_dir\identity\oblix\config\style\Pastel.xml
    <?xml version="1.0" ?>
    - <ParamsCtlg xmlns="http://www.oblix.com" CtlgName="style0">
    - <ValNameList ListName="">
    <NameValPair ParamName="styleReady" Value="TRUE" />
    </ValNameList>
    </ParamsCtlg>
    This new file, stored with style0.xml, provides the status of your custom style and the location of the original style directory from which wrapper files were copied. For example, if your custom style directory is named Pastel and you copied from Classic Style, the Pastel.xml file is created when you select Pastel as the default style.
    You do not need to edit this file. The original style0.xml remains unchanged. Also, there is a .lck version, Pastel.xml.lck, which is a lock file. No other new files are created when you add a new style.
    Updated styles.xml: The styles.xml file is updated to include a new NameValPair that provides both the directory and style names you supplied when creating the style.
    Locate and open the styles.xml file to confirm it was updated with your new style information.
    For example:
    Identity_install_dir\identity\oblix\config\style\styles.xml
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    - <ValNameList xmlns="http://www.oblix.com" ListName="styles.xml">
    <NameValPair ParamName="style0" Value="Classic Style" />
    <NameValPair ParamName="Pastel" Value="Pastel" />
    </ValNameList>
    In this example, both the default Classic Style and new custom Pastel style are identified. You do not need to edit this file.
    After confirming your custom directory structure, new and updated files, you are ready to choose a function and begin your customization.
    2.6.2 Choosing a Function to Customize
    The first step in the customization process is to choose a function to customize. For this example, suppose you want to change the font color to red on a specific page of the User Manager without changing anything else.
    To identify the function and source information
    Log in to the Identity System, as usual.
    Navigate to the desired page.
    For this example, click:
    Identity System Console, User Manager, and then click My Identity
    The page appears, as shown in Figure 2-6.
    Figure 2-6 Customization Example: A User Manager Page Displays Red Text
    The following information on each Identity System application page is useful for customizing styles:
    Application Name: The application name, User Manager, appears on a highlighted tab in the top left area of the screen.
    Each application's \bin directory contains the registration file that you need to identify functions. See "Registration Files".
    Page Name: The page name, in this example it is My Profile, is the first page that you want to customize so you can see text in a red font color.
    Registration File Path: The URL for each page includes a path to the application page, for example, identity\oblix\apps\userservcenter\bin\userservcenter.cgi. You can use this to locate the relevant registration file on the Identity Server.
    Function Name: The URL for each page also includes a segment, program=view in this case, that you can use to locate the relevant stylesheet name for the function in the registration file.
    Record the required information to assist you during the customization.
    For this example:
    Application: User Manager
    Page: User Profile
    Registration File Path: Identity_install_dir\identity\oblix\apps\userservcenter\bin\
    Function: program=view
    2.6.3 Copying Stylesheets to Your Custom Directory
    Once you have identified the function you want to customize, your next task in any customization is to copy relevant stylesheets into your custom directory from the \shared directory. This activity overwrites wrapper files in your custom directory with copies of stylesheets you can customize. This also retains the original stylesheets in \shared as well as the original default wrappers in \style0.
    Locating and copying relevant stylesheets is an iterative process in itself. In the following procedure you must locate and copy:
    Base stylesheets
    Stylesheets included in base stylesheets
    The specific function-related stylesheet identified for the program in the application's registration file, in this case the stylesheet associated with program=view
    Stylesheets included in the function-related stylesheet
    Eventually your custom directory must contain all stylesheets, including those identified in the application's registration file and in oblixbasereg.xml. Even if you do not need to edit a stylesheet, it must be copied to your custom directory.
    Important:
    Copying stylesheets is an iterative process that must be done in a selective manner. Attempting to copy all stylesheets from \shared to you custom directory at one time results in an error.
    To locate and copy relevant stylesheets
    Copy the base stylesheets to your custom style directory from \shared to overwrite the default wrappers with stylesheets you can customize.
    For example:
    Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ basic.xsl, font.xsl, searchform.xsl, navbar.xsl, title.xsl
    Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\
    This retains the original base stylesheets in \shared as well as the original default wrappers in \style0.
    Open each base stylesheet in your custom style directory and locate include statements that point to other stylesheets you must copy, as well as any style information you need to customize.
    For this example, see Table 2-29:
    Table 2-29 Base Stylesheet Pointers and Items to Customize
    Base Stylesheets in Custom Directory Pointers to Related Stylesheets and Items to Customize
    basic.xsl
    Contains implied relative include pointers to other stylesheets you need in your local custom directory:
    <xsl:include href="obstringutil.xsl" />
    <xsl:include href="font.xsl" />
    <xsl:include href="title.xsl" />
    Record the names of additional stylesheets you must copy into your custom directory from \shared. In this case, obstringutil.xsl.
    font.xsl
    Does not contain include pointers to other files.
    Does contain color information you can customize:
    <xsl:variable name="subHeadingColor">#006699...
    <xsl:variable name="contentTitleColor">#000000...
    <xsl:variable name="contentTextColor">#000000...
    searchform.xsl
    Does not contain include pointers to other files.
    Does not contain color information to customize. No changes needed to this stylesheet in your custom directory.
    navbar.xsl
    Does not contain include pointers to other files.
    Does contain color information you may customize later.
    title.xsl
    Does not contain include pointers to other files.
    Does contain color information you may customize later. No changes needed to this stylesheet in your custom directory.
    Copy stylesheets included in base stylesheets to your custom directory from \shared.
    For this example, obstringutil.xsl:
    Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ obstringutil.xsl
    Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\obstringutil.xsl
    Record the stylesheets you have copied from \shared to your custom directory so you can track your work.
    Locate the required registration files.
    For this example, oblixbasereg.xml and userservcenterreg.xml:
    Identity_install_dir\identity\oblix\apps\common\bin\oblixbasereg.xml Identity_install_dir\identity\oblix\apps\userservcenter\bin\ userservcenterreg.xml
    At some point, you typically need stylesheets included in the common registration file oblixbasereg.xml. However, stylesheets included in oblixbasereg.xml are not needed for this example.
    For this example, you must locate only the function-related stylesheet in the userservcenterreg.xml file.
    Open the application's registration file and locate the function-related stylesheet you need.
    For this example, locate ObProgram name="view":
    <?xml version="1.0" ?>
    - <ObProgramRegistry>
    - <ObApplication name="userservcenter">
    - <ObProgram name="front">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObSchema name="usc_front.xsd" />
    </ObProgram>
    - <ObProgram name="commonNavbar">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObSchema name="usc_front.xsd" />
    </ObProgram>
    - <ObProgram name="view">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObButton name="initiateDeactivateUser" />
    - <!-- ObButton name="manageSubscriptions"/ -->
    <ObButton name="userreactivate" />
    <ObButton name="wfTicketDelete" />
    <ObButton name="userModify" />
    <ObSchema name="usc_profile.xsd" />
    </ObProgram>
    You can see in the registration file that the usc_profile.xsl stylesheet is associated with the function you want to customize (ObProgram name="view"). The usc_profile.xsl stylesheet is also associated with a number of other functions.
    Copy the function-related stylesheet, usc_profile.xsl, to your custom style directory from \shared and record the stylesheet name.
    For this example:
    Copy From: Identity_install_dir\identity\oblix\lang\en-us\shared\ usc_profile.xsl
    Copy To: Identity_install_dir\identity\oblix\lang\en-us\Pastel\ usc_profile.xsl
    Open the function-related stylesheet and locate include statements that point to other stylesheets you must copy, record any information you plan to customize.
    For this example, usc_profile.xsl:
    Table 2-30 usc_profile.xsl Pointers and Items to Customize
    usc_profile.xsl in Custom Directory Pointers to Related Stylesheets and Items to Customize
    usc_profile.xsl
    This main stylesheet for the User Manager includes stylesheets that must be copied to your custom directory:
    <xsl:include href="./basic.xsl" />
    <xsl:include href="./selectorinfo.xsl" />
    <xsl:include href="./usc_searchform.xsl" />
    <xsl:include href="./usc_navbar.xsl" />
    Note: selectorinfo.xsl, usc_searchform.xsl and usc_navbar.xsl should be copied.
    Also record pointers to objects that should be customized:
    <object id="cenroll" classid= ...
    codebase="../../common/bin/xenroll.cab" />
    and
    <script src="../../common/bin/installCert.vbx" ...
    Repeat steps to copy relevant stylesheets, then record their names and details you plan to change.
    For this example:
    Copy From:
    Identity_install_dir\identity\oblix\lang\en-us\shared\selectorinfo.xsl
    Identity_install_dir\identity\oblix\lang\en-us\shared\usc_searchform.xsl
    Identity_install_dir\identity\oblix\lang\en-us\shared\usc_navbar.xsl
    Copy To:
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\selectorinfo.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_searchform.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_navbar.xsl
    These stylesheets do not contain include statements, other stylesheet names, nor parameters you need to change.
    You have collected, copied, and recorded relevant stylesheets for this example.
    2.6.4 Editing Stylesheets
    After copying relevant stylesheets, you may need to edit them. As described in Table 2-29 the information that needs to be customized for this example includes:
    Font colors defined in the base stylesheet font.xsl should be changed to red.
    Pointers to objects defined in usc_profile.xsl should change from a relative path to an absolute path.
    Note:
    To help streamline development and testing, consider implementing XSL stylesheet control parameters. See "Caching Considerations".
    To edit stylesheets for a simple font color change
    Open the font.xsl stylesheet in your custom directory in a text editor.
    For example,
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\ font.xsl
    Edit the stylesheet to change all colors from the default color to red (FF0000), then save the change.
    For example,
    Change all Default Font Colors From:
    ... <xsl:variable name="pageHeaderColor">#006699</xsl:variable>
    <xsl:variable name="subHeadingColor">#006699</xsl:variable>
    <xsl:variable name="contentTitleColor">#000000</xsl:variable>
    <xsl:variable name="contentTextColor">#000000</xsl:variable>
    and others ...
    To Red (#FF0000):
    ... <xsl:variable name="pageHeaderColor">#FF0000</xsl:variable>
    <xsl:variable name="subHeadingColor">#FF0000</xsl:variable>
    <xsl:variable name="contentTitleColor">#FF0000</xsl:variable>
    <xsl:variable name="contentTextColor">#FF0000</xsl:variable>
    and others ...
    Record your changes to this file.
    If you restarted the Identity Server now you would not yet see your changes. This is because you have not yet customized the function-related stylesheet that identifies where to apply the changes.
    Edit the basic.xsl stylesheet in your custom directory as follows to add required include statements that were in the original basic.xml (but were lost when you copied over the basic.xsl from the shared folder).
    Locate the line containing the following:
    <xsl:include href="obstringutil.xsl"/>
    Add the following information so that it precedes the line identified in a):
    <xsl:include href="./style.xsl" />
    <xsl:include href="../msgctlg.xsl" />
    Edit the usc_profile.xsl stylesheet in your custom directory to change the relative path to objects, as shown in the following, then save the changes.
    For example:
    Change From a Relative Path:
    - <head>
    ...<object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="../../common/bin/xenroll.cab" />
    ... <script src="../../common/bin/installCert.vbx" language="VBScript" />
    </head>
    Change To an Absolute Path:
    - <head>
    ... <object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="/identity/oblix/apps/common/bin/xenroll.cab" />
    ... <script src="/identity/oblix/apps/common/bin/installCert.vbx" language="VBScript" />
    </head>
    This concludes the specific function-related change for this example.
    Ensure that file system access control for new custom style directories and files is set to match the ownership and permissions of \style0.
    Restart the Identity Server.
    If you log in to the Identity System now and view the My Identity page, you see the red font color. However, the images supplied by WebPass won't appear until they are included in a corresponding custom style directory structure on the WebPass host.
    After doing this i checked user manager application then iam being displayed the following error page.
    style shhet error report form.
    an error has occured while executing the application.
    your browser does not support sending email automatically.
    please send email to <a=" "><\a> with the following information.
    you name
    email adress
    make sure to append the trace back in the mail
    in the log file errors have been given as below
    Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
    "Failed to compile XSL file."     XSL file:^../../../lang/en-us/pastel2/usc_profile.xsl     
    Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
    "OIS_LOG_PASSED_ERROR"     Error^writer\obhtmlpage.cpp:276: Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl

    Hi Matt,
    I think the page you are being redirected to is servererror.jsp, which is deployed within oam-server.ear, within its own ngsso-web.war application. You could deploy your own version of this. I assume you could also modify the ErrorPage setting in oam-config.xml to define your own page, though I have not tested this. This would be a customisation, so you would be responsible for the system behaviour when doing this.
    Regards,
    Colin

  • OAM 11g not starting

    Hi All,
    I recently installed OAM 11g using following Steps:
    1. Installed 11g DB
    2. RCU utility for creating OAM repositories
    3. Installed WebLogic 11g
    4. Added OAM instances to the Weblogic Domain
    5. Launch Weblogic
    5.1 Weblogic ADMIN console coming up without any issues: http://oam:7001/console
    5.2 When I try to Launch OAM App from Weblogic console or CMD prompt (using command: startManagedWeblogic.cmd oam_server1 t3://oam:14001) I get the following error: OAM is not coming up:
    ============================================================
    ####<Nov 1, 2010 11:38:30 AM GMT-04:00> <Info> <Management> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625910745> <BEA-141187> <Java system properties are defined as follows:
    CSS_TOOLKIT_LOC = C:\Oracle\Middleware\Oracle_IDM1\oam\server\lib\csslib
    OAM_CONFIG_FILE = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\fmwconfig\oam-config.xml
    OAM_ORACLE_HOME = C:\Oracle\Middleware\Oracle_IDM1\oam
    OAM_POLICY_FILE = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\fmwconfig\oam-policy.xml
    OAM_PROXY_LOG = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\fmwconfig\oam_proxy_logging.properties
    awt.toolkit = sun.awt.windows.WToolkit
    common.components.home = C:\Oracle\MIDDLE~1\ORACLE~1
    domain.home = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam
    em.oracle.home = C:\Oracle\Middleware\oracle_common
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    igf.arisidbeans.carmlloc = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\FMWCON~1\carml
    igf.arisidstack.home = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\FMWCON~1\arisidprovider
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_IDM1\oam\agent\modules\oracle.oam.wlsagent_11.1.1\oam-wlsagent.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
    java.class.version = 50.0
    java.endorsed.dirs = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\endorsed
    java.ext.dirs = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\ext
    java.home = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre
    java.io.tmpdir = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
    java.library.path = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\bin;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin;c:\app\Administrator\product\11.2.0\dbhome_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
    java.protocol.handler.pkgs = oracle.mds.net.protocol|weblogic.net
    java.runtime.name = Java(TM) SE Runtime Environment
    java.runtime.version = 1.6.0_17-b04
    java.security.policy = C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.6
    java.vendor = Oracle Corporation
    java.vendor.url = http://www.oracle.com/
    java.vendor.url.bug = http://download.oracle.com/docs/cd/E15289_01/go2troubleshooting.html
    java.version = 1.6.0_17
    java.vm.info = compiled mode
    java.vm.name = Oracle JRockit(R)
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Oracle Corporation
    java.vm.vendor.url = http://www.oracle.com/
    java.vm.vendor.url.bug = http://download.oracle.com/docs/cd/E15289_01/go2troubleshooting.html
    java.vm.version = R28.0.0-679-130297-1.6.0_17-20100312-2123-windows-ia32
    javax.management.builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
    javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
    javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
    javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
    javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
    jrf.version = 11.1.1
    jrockit.optfile = C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt
    kernel.download.enabled = false
    oes.enabled = true
    oes.integration.path = C:\Oracle\Middleware\Oracle_IDM1\oam\server\lib\oeslib\oes-integration.jar
    oes.jars.home = C:\Oracle\Middleware\Oracle_IDM1\oam\server\lib\oes-d8
    oracle.core.ojdl.logging.applicationcontextprovider = oracle.core.ojdl.weblogic.ApplicationContextImpl
    oracle.core.ojdl.logging.componentId = oam_server1
    oracle.core.ojdl.logging.usercontextprovider = oracle.core.ojdl.weblogic.UserContextImpl
    oracle.domain.config.dir = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\FMWCON~1
    oracle.oaam.home = C:\Oracle\Middleware\Oracle_IDM1\oaam\
    oracle.security.am.SERVER_INSTNCE_NAME = oam_server1
    oracle.security.jps.config = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\fmwconfig\jps-config.xml
    oracle.server.config.dir = C:\Oracle\MIDDLE~1\USER_P~1\domains\oam\config\FMWCON~1\servers\oam_server1
    org.apache.commons.logging.Log = org.apache.commons.logging.impl.Jdk14Logger
    org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
    org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
    org.xml.sax.driver = weblogic.xml.jaxp.RegistryXMLReader
    org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
    os.arch = x86
    os.name = Windows 2003
    os.version = 5.2
    path.separator = ;
    platform.home = C:\Oracle\MIDDLE~1\WLSERV~1.3
    sun.arch.data.model = 32
    sun.boot.class.path = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\resources.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\rt.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\sunrsasign.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\jsse.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\jce.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\lib\charsets.jar;C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\classes
    sun.boot.library.path = C:\Oracle\MIDDLE~1\JROCKI~1.0-6\jre\bin
    sun.cpu.endian = little
    sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
    sun.desktop = windows
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = Cp1252
    sun.management.compiler = Oracle JRockit(R) Optimizing Compiler
    sun.os.patch.level = Service Pack 2
    user.country = US
    user.dir = C:\Oracle\Middleware\user_projects\domains\oam
    user.home = C:\Documents and Settings\Administrator
    user.language = en
    user.name = Administrator
    user.timezone = GMT-04:00
    vde.home = C:\Oracle\Middleware\user_projects\domains\oam\servers\oam_server1\data\ldap
    weblogic.Name = oam_server1
    weblogic.ProductionModeEnabled = true
    weblogic.alternateTypesDirectory = C:\Oracle\Middleware\Oracle_IDM1\oam\agent\modules\oracle.oam.wlsagent_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1
    weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
    weblogic.ext.dirs = C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath
    weblogic.home = C:\Oracle\MIDDLE~1\WLSERV~1.3\server
    weblogic.jdbc.remoteEnabled = false
    weblogic.management.discover = false
    weblogic.management.server = t3://oam:14001
    weblogic.security.SSL.trustedCAKeyStore = C:\Oracle\Middleware\wlserver_10.3\server\lib\cacerts
    wls.home = C:\Oracle\MIDDLE~1\WLSERV~1.3\server
    wlw.iterativeDev = false
    wlw.logErrorsToConsole = false
    wlw.testConsole = false
    >
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Notice> <WebLogicServer> <OAM> <oam_server1> <Main Thread> <<WLS Kernel>> <> <> <1288625916703> <BEA-000365> <Server state changed to STANDBY>
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Notice> <WebLogicServer> <OAM> <oam_server1> <Main Thread> <<WLS Kernel>> <> <> <1288625916703> <BEA-000365> <Server state changed to STARTING>
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Info> <SAFService> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625916783> <BEA-281003> <SAF Service has been initialized.>
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Info> <SAFService> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625916813> <BEA-281002> <SAF Service has been started.>
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Info> <WseeCore> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625916823> <BEA-220502> <The Wsee Service is starting>
    ####<Nov 1, 2010 11:38:36 AM GMT-04:00> <Info> <Deployer> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625916853> <BEA-149209> <Resuming.>
    ####<Nov 1, 2010 11:38:39 AM GMT-04:00> <Info> <JDBC> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625919237> <BEA-001177> <Creating Connection Pool named oamDS, URL = jdbc:oracle:thin:@localhost:1521/oimdb, Properties = user=DEV_OAM;oracle.net.CONNECT_TIMEOUT=10000;.>
    ####<Nov 1, 2010 11:38:39 AM GMT-04:00> <Info> <Common> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625919287> <BEA-000626> <Free resources in pool "oamDS" will be tested every "300" seconds.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <JDBC> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920068> <BEA-001124> <Created Connection Pool named oamDS.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <JDBC> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920128> <BEA-001174> <Creating Data Source named oamDS, JNDI Name = jdbc/oamds.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <JDBC> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920298> <BEA-001512> <Data Source oamDS has been successfully created.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <Diagnostics> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920399> <BEA-320114> <Initializing the Diagnostics Harvester.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <Diagnostics> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920409> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Nov 1, 2010 11:38:40 AM GMT-04:00> <Info> <Diagnostics> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625920419> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Nov 1, 2010 11:38:41 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625921761> <BEA-160151> <Registered library Extension-Name: UIX, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (WAR).>
    ####<Nov 1, 2010 11:38:42 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625922572> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Nov 1, 2010 11:38:48 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625928370> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain.webapp, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Nov 1, 2010 11:38:48 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625928620> <BEA-160151> <Registered library Extension-Name: jsf, Specification-Version: 1.2, Implementation-Version: 1.2.9.0 (WAR).>
    ####<Nov 1, 2010 11:38:48 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625928691> <BEA-160151> <Registered library Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2.0.1 (WAR).>
    ####<Nov 1, 2010 11:38:48 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625928841> <BEA-160151> <Registered library Extension-Name: ohw-rcf, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Nov 1, 2010 11:38:48 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625928961> <BEA-160151> <Registered library Extension-Name: ohw-uix, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929111> <BEA-160151> <Registered library Extension-Name: oracle.adf.dconfigbeans, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929251> <BEA-160151> <Registered library Extension-Name: oracle.adf.management, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929281> <BEA-160151> <Registered library Extension-Name: oracle.dconfig-infra, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929351> <BEA-160151> <Registered library Extension-Name: oracle.jrf.system.filter (WAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929572> <BEA-160151> <Registered library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929592> <BEA-160151> <Registered library Extension-Name: oracle.pwdgen, Specification-Version: 11.1.1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929622> <BEA-160151> <Registered library Extension-Name: oracle.wsm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Nov 1, 2010 11:38:49 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625929642> <BEA-160151> <Registered library Extension-Name: orai18n-adf, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Nov 1, 2010 11:38:50 AM GMT-04:00> <Error> <Deployer> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625930613> <BEA-149205> <Failed to initialize the application 'oracle.idm.uishell [LibSpecVersion=11.1.1,LibImplVersion=11.1.1]' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
    weblogic.management.DeploymentException: Exception occured while downloading files
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:683)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'oam', port: '14001'
         at weblogic.net.http.HttpClient.openServer(HttpClient.java:327)
         at weblogic.net.http.HttpClient.openServer(HttpClient.java:419)
         at weblogic.net.http.HttpClient.New(HttpClient.java:246)
         at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:176)
         at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
         at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:57)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:683)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Nov 1, 2010 11:38:51 AM GMT-04:00> <Info> <J2EE> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625931064> <BEA-160151> <Registered library Extension-Name: oracle.webcenter.composer, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (WAR).>
    ####<Nov 1, 2010 11:38:52 AM GMT-04:00> <Error> <Deployer> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625932005> <BEA-149205> <Failed to initialize the application 'oracle.oaam.libs [LibSpecVersion=11.1.1.3.0,LibImplVersion=11.1.1.3.0]' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
    weblogic.management.DeploymentException: Exception occured while downloading files
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:683)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'oam', port: '14001'
         at weblogic.net.http.HttpClient.openServer(HttpClient.java:327)
         at weblogic.net.http.HttpClient.openServer(HttpClient.java:419)
         at weblogic.net.http.HttpClient.New(HttpClient.java:246)
         at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:176)
         at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
         at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:57)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:683)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Nov 1, 2010 11:38:52 AM GMT-04:00> <Info> <Deployer> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288625932025> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_NEW to STATE_PREPARED on server oam_server1.>
    ####<Nov 1, 2010 11:38:58 AM GMT-04:00> <Info> <Deployer> <OAM> <oam_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    ============================================================
    Any suggestiongs on as to what might be causing this error?
    Did I miss a step in OAM installation?
    Thanks for your help in advance

    I changed the port as per the doc 1384844.1 and I still get the same problem.

  • How to persist URL parameters in OAM portal inserts?

    Hi,
    We have a requirement to redirect the users to different XSLs based on the containers configured in OID (ou=employees,ou=customers). We have configured different style directories (employees and customers) in OAM. For Identity Administration activities we are using another style (adminStyle) used by OAM Identity Administrators.
    We are using OAM portal inserts for navigating from webapplication (integrated with OAM) to OAM modify profile page to change user attributes.
    Also webapplication using different authenitcation scheme in OAM.
    User login into webapplication using login.jsp (form based authentication scheme) and clicks on Modify profile link (URL will be portal insert URL).
    After the user session timeout (Configured in webgate) user is redirected to OAM login page (form based authentication). Once the user enters valid credentials user is redirected to OAM user manager application (only navigation bar with back button is displayed).
    The parameters comp=true, style=employees and program=modify are lost. Hence user not able to see OAM Modify profile page. Again user needs to click on back button (portalid) to get into Modify profile page. How to persist these parameters in the URL?
    Following is the portal insert URL we are using:
    http://<host>:<port>/identity/oblix/apps/userservcenter/bin/userservcenter.cgi?program=modify&uid=UserDN&style=employees&xsl=usc_profile.xsl&comp=true &portalid=webapphome
    Anypointers on this is appreciated.
    Thanks in advance.
    Regards,
    Srikanth
    Edited by: Srikanth_idam on 16-Apr-2010 04:30

    Hi Srikanth,
    That looks like a bug (6158232) that was fixed in version 10.1.4.2 of OAM Access Server (maybe WebGate too). Are you on an earlier version?
    Regards,
    Colin

Maybe you are looking for

  • Using sql to monitor free/used space

    Hi, Using the next sql statement SELECT /* + RULE */  df.tablespace_name "Tablespace",        df.bytes / (1024 * 1024) "Size (MB)",        SUM(fs.bytes) / (1024 * 1024) "Free (MB)",        Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",       

  • My apps won't update or install. I would push the update/install button, and it wouldn't do anything. How do I fix that?

    My apps won't update or install. I would push the update/install button, and it wouldn't do anything. How do I fix that?

  • DB13 online backup restore

    I am taking daily online backup from DB13 with the option"database backup+redolog file" on a tape medium.If I want to restore this taken backup what is the procedure and commands to be used

  • Event Server supports clustering / transactional safety?

    Does this new Event Server application server support clustering and/or transaction safety? I.e. in a trading type of application, how do you distribute load across multiple event servers and also, to what extent can you lose messages should a server

  • NWBC Change Logs

    Hi All, I am working on SAP transportation management (TM) system which uses NWBC. All end users access NWBC and perform various transactions like Create Booking, Change Booking etc. Change logs are not being captured in any of the change tables (CDH