POODLE Vulnerability and AMS configuration in Adapator.xml

Hi,
I am looking for some recommendation and guidance on how to ban AMS from using SSlV3 in with RTMPS clients. I know about that there's a configuration in Adaptor.xml called
"SSLCipherSuite" which should be able to somehow prevent a specific protocol, but the Adobe documentation recommends contacting with Adobe before changing that configuration.
So I was wondering if Adobe has any official recommendation to prevent RTMPS client from using SSLV3. Could someone please point me to the right direction?
Thanks
-Irtiza

When will it be released?
I can not comment on that...
How will it support older browsers?
Well most likely it will disable SSLv3 support from within the application. So you will not need to change anything in AMS ocnfiguration.
All browsers which work on TLS 1.0 and higher will continue to work as they were working till now.
Note that even in current release, if your browsers support TLS then TLS would be preferred mode of connection  and you will not be exposed to SSLv3 attack.
Even today, POODLE vulnerability exists only if you are working on those browsers which do not support TLS.
That said, you must upgrade your openssl to 1.0.1j, because prior to that a hacker could exploit a hack in openssl so that even if your endpoints supports TLS, it can hack and make the connection protocol get downgraded to SSLv3...openssl to 1.0.1j fixes this downgrade protocol attack..
The steps to compile openssl for AMS are available in public domain..please google and compile openssl for yourself and drop that openssl in your AMS installation.
Openssl consists of two files libeay32.dll and ssleay32.dll on windows  AND libssl.so.1.0.0 and libcrypto.so.1.0.0 on Linux...

Similar Messages

  • Sslv3 poodle vulnerability and sharepoint site using https

    Hi
    Is it safe  to run IIS crypto tool and choose
    'FIPS 140-2'  on Sharepoint WFe
    We have one web application accessible to users using HTTPS with a  valid  SSL from CA.

    FIPS 140-2 is not supported by SharePoint and enforcing it will break SharePoint.
    Instead, disable SSLv3 support in IIS.
    https://www.digicert.com/ssl-support/iis-disabling-ssl-v3.htm
    https://support.microsoft.com/kb/187498/
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • POODLE vulnerability - ASA 5520

    Hi
    I would like to know if my firewalls ASA 5520 (Cisco Adaptive Security Appliance Version 8.4(6), 8.2(1)) are vulnerables to the Poodle vulnerability.
    Which workaround should i do??? it would have any impact in my VPN or servers DMZ????
    Thanks...

    Hi ,
    Both these  ASA versions are vulnerable 
    Conditions:
    The default configuration of SSL on all versions of the ASA enables SSLv3.
    Due to CSCug51375, the ASA is unable to disable SSLv3 on ASA v9.0.x and v9.1.1.x.
    To see the SSL configuration:
    show run all ssl
    Default configuration of the ASA:
    ssl client-version any
    ssl server-version any
    The following non-default configuration values also enable SSLv3:
    ssl client-version sslv3-only
    ssl client-version salve
    ssl server-version sslv3-only
    ssl server-version sslv3
    The following versions are vulnerable regardless of ssl configuration:
    * 9.0.x
    * 9.1.1.x
    Workaround:
    Disable SSLv3, write the changes to the startup-config.
    This workaround only applies to the following versions:
    * 7.x and later
    * 8.2 and later
    * 8.3 and later
    * 8.4 and later
    * 8.5 and later
    * 8.6 and later
    * 8.7 and later
    * 9.1.2 and later (with CSCug51375 fix)
    * 9.2.1 and later (with CSCug51375 fix)
    * 9.3.1 and later
    Use the following config-mode commands:
    ssl server-version tlsv1
    ssl client-version tlsv1-only
    There is no need to reboot. The configuration must be saved via "write memory".
    Here is the bug details CSCur23709
    Known fixed ASA versions 9.0(4.201) ,9.2(2.103),9.3(1.1)
    Thanks,
    Prashant Joshi

  • How i configure the log4j.xml in weblogic server

    hi
    i write a new lg4j.xml and i put this in WEB-INF/classes,i deployed this jar in my remote server,but it not reflected. [i am not specify the server logs, we have some API's which is deployed in server for that API log files is configured using log4j.xml ]
    i saw there is a option in weblogic - setDomain -LOG4J_CONFIG_FILE='here we give the path for log4j.xml'.I think it's only work for local machines not for the remote machines.
    i don't know how to get a log files in weblogic server

    To use Quartz primarily within an application server environment,include the Quartz JAR within the enterprise application (.ear or .war file). However, if you want to make Quartz available to many applications then simply make sure it's on the classpath of your appserver.
    You can also deploy it as a jar file or a library module as required.
    Quartz depends on a number of third-party libraries (in the form of jars) which are included in the distribution .zip file in the 'lib' directory. To use all the features of Quartz, all of these jars must also exist on your classpath.
    -Sandeep

  • Problem parsing configuration/hibernate.cfg.xml

    I am trying to integrate struts with hibernate. I have created a plug-in for that and copied all the necessary jars & xmls to the classpath. I am providing the full stack trace, can any one say what could be the problem
    net.sf.hibernate.HibernateException: problem parsing configuration/hibernate.cfg
    .xml
    at net.sf.hibernate.cfg.Configuration.doConfigure(Configuration.java:963
    at net.sf.hibernate.cfg.Configuration.configure(Configuration.java:902)
    at net.sf.hibernate.cfg.Configuration.configure(Configuration.java:888)
    at com.plugin.HibernatePlugIn.initHibernate(HibernatePlugIn.java:72)
    at com.plugin.HibernatePlugIn.init(HibernatePlugIn.java:54)
    at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle
    t.java:869)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:336)
    at javax.servlet.GenericServlet.init(GenericServlet.java:211)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
    java:1029)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:86
    2)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
    t.java:4013)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
    357)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
    .java:823)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:80
    7)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
    at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDep
    loyer.java:277)
    at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
    at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:625
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:431
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
    :349)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
    eSupport.java:119)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478
    at org.apache.catalina.core.StandardService.start(StandardService.java:4
    80)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:231
    3)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
    Caused by: org.dom4j.DocumentException: hibernate.sourceforge.net Nested excepti
    on: hibernate.sourceforge.net
    at org.dom4j.io.SAXReader.read(SAXReader.java:358)
    at net.sf.hibernate.cfg.Configuration.doConfigure(Configuration.java:958
    )

    Looks like a problem with Hibernate itself parsing the config file?
    Here's a posting from the Hibernate forum that sounds similar:
    http://forums.hibernate.org/viewtopic.php?p=2256871&highlight=&sid=e1090f717891db4535310102c61bec25
    -steve-

  • How to configure crystal report xml file as data source in BOE in Solaris?

    Hi,
    How to configure crystal reports from xml file as data source in Solaris? I didn't find any suitable driver for xml / excel files for sun solaris.
    Which driver i have to use to connect xml file to crystal report to view my crystal report in solaris BOE?
    And the same way excel file as data source for crystal report.
    Thanks

    Hi Don thanks for the reply,
    In windows environment I donot have any problem when creating crystal report from Xml file and Excel file. After creating reports when I publish those into boe server in solaris, getting connection failed error.
    My solaris BOE server doent have any network connection with windows machines. So i have to place the files in solaris server.
    Below the steps what I tried:
    1. Created crystal reports from cr designer in windows using ADO.Net(xml) and in another try with Xml webservices drivers. Reports works well as it should.
    2. Saved in BOE repository in Solaris server from crystal reports and changed database configuration settings as:
        -Used custom database logon information and specified cr_xml as custom driver.
        -Chnaged database path to file directory path according to solaris server file path </app/../../>
        -tried table prefix also
        - Selected radio button use same database logon as when report is run saved.
    My environment :
    SAP BOXI3.1 sp3
    crystal reports 2008 sp3
    SunOS
    Cr developing in windows 7.
    For Excel I tried with ODBC in windows but I can't find any ODBC or JDBC drivers for Excel in solaris.
    Any help to solve my issues
    Thanks
    Nagalla

  • ALE and Idocs configuration

    Hi Gurus,
    Please tell me the ALE and Idocs configuration settings
    Thnaks in advance

    Hi,
    Please refer to the details mentioned in the hyper-links beow.
    You will get the details how to go about it.
    To see the IDOC & status check it in WE02/WE05
    You will get step by step process.
    ABAP Development
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
    http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
    ABAP Development
    Follow below steps to create custom IDOC.
    1.Create segments through transaction WE31.
    2.Create IDoc Type through transaction WE30 by attaching created segments.
    3.Message type through transaction WE81.
    4.Link Idoc and message type in WE82 transaction.
    Check the transaction WEDI for ALE settings
    Check these links for more details on IDoc's:
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
    Hope this will help.
    Regards,
    Priyanka.

  • ORABPEL-30028  Invalid configuration file wf_config.xml

    Hi,
    Recently I have upgraded BPEL 10.1.3.1.0 to 10.1.3.4.0. I have included all the required jar files in classpath even though I am getting the below error.
    Please assist me to resolve this.
    ORABPEL-30028
    Invalid configuration file wf_config.xml
    The configuration file wf_config.xml not be read.
    Make sure that the configuration file wf_config.xml is available and is a valid XML document. Contact oracle support if error is not fixable.
         at oracle.bpel.services.config.ConfigurationManager.init(ConfigurationManager.java:79)
         at oracle.bpel.services.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:101)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:119)
         at oracle.bpel.services.config.ConfigurationManager.getBooleanProperty(ConfigurationManager.java:170)
         at oracle.bpel.services.common.exception.ServicesException.<clinit>(ServicesException.java:61)
         at oracle.bpel.services.config.ConfigurationManager.init(ConfigurationManager.java:79)
         at oracle.bpel.services.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:101)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:119)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:141)
         at oracle.bpel.services.config.ConfigurationManager.getStringProperty(ConfigurationManager.java:187)
         at oracle.bpel.services.workflow.task.impl.WorkflowUtil.<clinit>(WorkflowUtil.java:127)
         at oracle.bpel.services.workflow.repos.Predicate.isUserColumnAndCaseAgnostic(Predicate.java:726)
         at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:780)
         at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:762)
         at oracle.bpel.services.workflow.repos.Predicate.<init>(Predicate.java:487)
         at com.wipro.sobay.oraclebpel.WorklistService.fetchTaskListforSearch(Unknown Source)
         at com.wipro.sobay.oraclebpel.WorklistService.getTaskCount(Unknown Source)
         at com.wipro.sobay.auditor.action.ViewTaskListAction.viewTaskList(Unknown Source)
         at com.wipro.sobay.auditor.action.ViewTaskListAction.postexecute(Unknown Source)
         at com.wipro.sobay.action.SobayBaseAction.execute(Unknown Source)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.NullPointerException
         at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:358)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:287)
         at oracle.bpel.services.common.util.AbstractJaxbUtil.unmarshal(AbstractJaxbUtil.java:128)
         at oracle.bpel.services.config.ConfigurationManager.init(ConfigurationManager.java:60)
         ... 43 more
    2009-10-23 16:04:58,031 INFO [STDOUT] <2009-10-23 16:04:58,031> <ERROR> <oracle.bpel.services.workflow> <::>
    java.lang.NullPointerException
         at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:358)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:287)
         at oracle.bpel.services.common.util.AbstractJaxbUtil.unmarshal(AbstractJaxbUtil.java:128)
         at oracle.bpel.services.config.ConfigurationManager.init(ConfigurationManager.java:60)
         at oracle.bpel.services.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:101)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:119)
         at oracle.bpel.services.config.ConfigurationManager.getBooleanProperty(ConfigurationManager.java:170)
         at oracle.bpel.services.common.exception.ServicesException.<clinit>(ServicesException.java:61)
         at oracle.bpel.services.config.ConfigurationManager.init(ConfigurationManager.java:79)
         at oracle.bpel.services.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:101)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:119)
         at oracle.bpel.services.config.ConfigurationManager.getProperty(ConfigurationManager.java:141)
         at oracle.bpel.services.config.ConfigurationManager.getStringProperty(ConfigurationManager.java:187)
         at oracle.bpel.services.workflow.task.impl.WorkflowUtil.<clinit>(WorkflowUtil.java:127)
         at oracle.bpel.services.workflow.repos.Predicate.isUserColumnAndCaseAgnostic(Predicate.java:726)
         at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:780)
         at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:762)
         at oracle.bpel.services.workflow.repos.Predicate.<init>(Predicate.java:487)
         at com.wipro.sobay.oraclebpel.WorklistService.fetchTaskListforSearch(Unknown Source)
         at com.wipro.sobay.oraclebpel.WorklistService.getTaskCount(Unknown Source)
         at com.wipro.sobay.auditor.action.ViewTaskListAction.viewTaskList(Unknown Source)
         at com.wipro.sobay.auditor.action.ViewTaskListAction.postexecute(Unknown Source)
         at com.wipro.sobay.action.SobayBaseAction.execute(Unknown Source)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
         at java.lang.Thread.run(Thread.java:595)
    Thanks,
    VENKAT R

    Hi.
    Actually, this exception occurs when I try to get the list of task from BPEL using my application built in java (JBOSS server).
    I could able to open the wf_config.xml and wf_client_config.xml file from browser without having any error.
    Thanks,
    VENKAT R

  • Managed Servers not starting with options configured in config.xml

    Hi,
    I Installed an Weblogic 10.3 on a Red Hat system and i configured an domain and 2 managed servers.
    I configured the servers with some java arguments like this:
    -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m
    I do see in the ${DOMAIN_HOME}/config/config.xml the managed servers with the settings that I have configured it via the Web Gui Admin Console.
    Now I want to start the Managed Servers with the following command:
    +cd ${DOMAIN_HOME}/bin+
    +./startManagedWebLogic.sh managed-server1 http://admin:port+
    When i check the console, I don't see the correct JVM settings! Also other options that I configured in the Web Gui Admin Console, don't appear in the logfile.
    The JVM settings I see, are those from the AdminServer.
    How can I change/fix this?
    Please help.
    Kind regards,
    Werner

    Hi,
    Please add the changes to the startup script startManagedWeblogic.sh.
    You can add the memory args settings as "-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m"
    Please let me know if it dosent fix.

  • What is the cisco ironport C680 and M680 configuration backup file size?

    what is the cisco ironport C680 and M680 configuration backup file size?

    Size of the XML itself?  That is going to vary based on what you have configured, total lines of code, and # of appliances you may/may not have in cluster.
    M680, based on SMA as stand-alone, should be similar --- you are probably looking @ < 1 MB... 
    Looking @ my test environment, in which I have a nightly cron job set to grab a backup of...
    -rw-rw----  1 robert robert 161115 Sep 26 02:00 C000V-564D1A718795ACFEXXXX-YYYYBAD60A5A-20140926T020002.xml
    So, 161115 bytes = .15 MB
    -Robert

  • Integrating SOA and Peoplesoft: Configuring JMSTARGET Connector in IB.

    Hi All,
    I have created JMS queue/topic in oracle application server. Can anybody idea how can we configure JMS connector of peoplesoft integration broker.
    Let me first explain my requirement, I am working in peoplesoft outbound interface design with SOA integration.
    So my approach will be creating JMS queue in oracle application Server and then configuring this JMS to any node of peoplesoft IB.
    Then extracted information from peoplesoft need to send to the above node so that once the node receive the message it should
    populate the JMS queue inturn SOA BPEL will be triggered to write into third party file/database.
    Please give your inputs on this approach if you any other suggetion for peoples soft outbound integration with SOA.
    Thanks inadvance.

    Its published, but somehow you are unable to see it..issues with Meatlink for sure..
    Here is its content :
    Applies to:
    PeopleSoft Enterprise PT PeopleTools - Version: 8.4 - Release: 8.4
    Information in this document applies to any platform.
    This document was previously published as Customer Connection Solution 201077819
    Symptoms
    Please see below.
    Cause
    Not Applicable
    Solution
    <<Document:664816.1>> E-IB: Configuring Integration Broker with IBM MQ on AIX
    SPECIFIC TO: Enterprise, PeopleTools, Integration Broker Release 8.49
    ISSUE:
    How to setup Integration Broker to PUT messages to an IBM MQ Server on a remote machine?
    SOLUTION:
    <See attachment for documentation with screenshot examples.>
    Configuring Integration Broker with IBM MQ on AIX
    The following guide is intended to outline the setup between Peoplesoft Integration Broker and IBMs Websphere MQ version 6 client on AIX. Note: This is not a certification, but a working example, specifically using the MQ client to connect to a remote machine running the MQ server.
    Platform Information:
    PeopleSoft PeopleTools 8.49
    IBM Websphere MQ Release 6
    AIX
    Steps
    1) Install and IBM Websphere MQ (WMQ) client
    2) Configure WMQ connection
    3) Configure Peoplesoft
    4) TEST using PING and a Peoplesoft message to PUT data onto the WMQ server
    Steps
    1) Install and configure Websphere MQ client on AIX where Peoplesoft is located
    NOTE: This is one optional architecture. It is also possible to install Peoplesoft and MQ on the same server, which avoids the client software altogether.
    a. IBM deliveres an MQ client that is installed on the same box as the Peoplesoft with the following options.
    i. Installed to /usr/mqm, all objects owned by local user mqm
    ii. Ensure that the MQ Extended Transactional Client is installed
    1. This includes com.ibm.mqetclient.jar file
    iii. Mq specific environment variables
    1. $MQ_JAVA_DATA_PATH=/usr/mqm
    2. $MQ_JAVA_INSTALL_PATH=/usr/mqm/java
    3. $MQ_JAVA_LIB_PATH=/usr/mqm/java/lib
    4. jms.jar, fscontext.jar, jndi.jar, providerutil.jar, stcjms.jar
    iv. CLASSPATH
    1. Includes the following MQ jar files
    i. com.ibm.mqetclient.jar
    ii. providerutil.jar
    iii. com.ibm.mqjms.jar
    iv. ldap.jar
    v. jta.jar
    vi. jndi.jar
    vii. jms.jar
    viii. connector.jar
    ix. com.ibm.mq.jar
    2. Example
    a. > echo $CLASSPATH
    i. echo $CLASSPATH /usr/mqm/java/lib/com.ibm.mqetclient.jar:/usr/mqm/java/lib/providerutil.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/ldap.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib:/usr/mqm/java/bin
    3. When setting up Peoplesoft, add these jar files to the classpath setting in the setenv.sh file and reboot PIA
    2) Configure WMQ
    a. Edit JMSAdmin.config (located in /usr/mqm/java/bin)
    ii. Set Initial Context Factory = com.sun.jndi.fscontext.RefFSContextFactory
    # The following line specifies which JNDI service provider is in use.
    # It currently indicates an LDAP service provider. If a different
    # service provider is used, this line should be commented out and the
    # appropriate one should be uncommented.
    #INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    #INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
    iii. Set PROVIDER_URL=file:/usr/mqm/java
    # The following line specifies the URL of the service provider's initial context. It currently refers to an LDAP root context. Examples of a file system URL and WebSphere's JNDI namespace are also shown, commented out.
    #PROVIDER_URL=ldap://polaris/o=ibm,c=us
    PROVIDER_URL=file:/usr/mqm/java
    #PROVIDER_URL=iiop://localhost/
    b. Run JMSAdmin to setup queue and qcf to the MQ server
    i. def qcf(PLAS160_QCF) HOSTNAME(GSPLVP006-VM2) PORT(1414) CHANNEL(SYSTEM.DEF.SVRCONN) QMANAGER(QM_gsplvp006_vm2) TRANSPORT(CLIENT)
    ii. NOTE: When connecting from a client to a remote server, it is important to specify the hostname, port and transport along with the other values.
    iii. def q(PLAS160_Q) queue(PLAS160_Q)
    1. Note: The q is a local naming alias, whereas the queue is the physical queue name on the MQ server
    iv. Screenshot:
    v. This creates a .bindings file
    vi. NOTE: It is also possible to use IVTSetup for this, but JMSAdmin is recommended.
    vii. NOTE: It is possible to gain a .bindings file from your MQ server administrator. Be sure that this format is correct, and the location on the client is referenced correctly.
    viii. JMSAdmin can also be used to determin what connections are available from this machine using command dis ctx as shown
    b. Optional: Test the connection to the MQ server using IBM software.
    NOTE: Testing the ivtQ and ivt QCF can be accomplished using the IVTRun program, provided that the ivtQ and ivtQCF have been setup in the .bindings file with the same available on the MQ server (some mq administrators do not enable this by default)
    i. Example IVTRun, see Appendix 1
    ii. Example .bindings file see Appendix 2
    3) Configure PeopleSoft
    a. Create an external NODE representing the target JMS queue
    i. Example node, see appendix 3
    b. Setup the connectors properties for the new node
    i. Use the connector ID= JMSTARGET
    ii. Example properties screenshot, see Appendix 4
    1. Notes
    a. JMSProvider is MQSeries
    b. JMSFactory, JMSQueue are those specified in the .bindings file representing that on the JMS server. In this case, PLAS160_QCF and PLAS160_Q are used for this example.
    c. JMSUrl is the location of the working .bindings file on the web server (in this case file:/D:/apps/IBM/WebSphereMQ/Java )
    c. Setup Gateway Properties
    i. Access the Gateway Properties using PIA and add the JMS information for MQSeries to the integrationgateway.properties file as shown:
    ## JMS configuration Section
    # <the following line is required>
    ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
    ii. Queue information here is only needed if going to GET message using the JMSListeningConnector. Not needed for the target PUT (or ping)
    iii. Example integrationgateway.properties, See appendix 5
    4) Test PUT connection from Peoplesoft to WMQ
    1. Ping the JMS node from the node definition
    b. Setup routings to PUT messages to the MQ node
    i. Example using USER_PROFILE
    ii. Submit the message and check the Operations Monitor
    iii. Verify that the message made it to MQ (this is viewed by browsing the queue on the Websphere MQ Explorer, message browser. A better utility is rfhutil which is included in the MQ windows client development kit)
    NOTE: This document is intended for 1 way communication TO Mq from Peoplesoft. Setup for GET using the JMSListeningConnector is a separate topic for documentation.
    Appendix 1 IVTRun
    Appendix 2 .bindings file.
    NOTE: The PLAS160_QCF and PLAS160_Q references are applicable to this example.
    #This file is used by the JNDI FSContext.
    #Wed Sep 17 11:43:13 PDT 2008
    PLAS160_QCF/RefAddr/9/Type=SRC
    PLAS160_Q/RefAddr/5/Encoding=String
    PLAS160_QCF/RefAddr/13/Content=5000
    PLAS160_QCF/RefAddr/3/Content=GSPLVP006-VM2
    PLAS160_Q/RefAddr/8/Content=PLAS160_Q
    PLAS160_QCF/RefAddr/13/Type=PINT
    PLAS160_QCF/RefAddr/1/Type=TRAN
    MYPUT/RefAddr/2/Content=-2
    PLAS160_QCF/RefAddr/6/Encoding=String
    PLAS160_QCF/RefAddr/17/Type=RINT
    PLAS160_QCF/RefAddr/5/Type=CHAN
    PLAS160_QCF/RefAddr/18/Encoding=String
    PLAS160_Q/RefAddr/2/Content=-2
    PLAS160_PUT/RefAddr/1/Encoding=String
    PLAS160_QCF/RefAddr/20/Content=SYSTEM.DEFAULT.MODEL.QUEUE
    PLAS160_PUT/RefAddr/3/Type=PER
    MYPUT/RefAddr/6/Encoding=String
    PLAS160_Q/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/8/Content=PLAS160_PUT
    PLAS160_Q/RefAddr/6/Encoding=String
    MYPUT/RefAddr/0/Type=VER
    PLAS160_PUT/RefAddr/7/Type=FIQ
    PLAS160_QCF/RefAddr/7/Encoding=String
    MYPUT/RefAddr/4/Type=CCS
    PLAS160_PUT/RefAddr/2/Content=-2
    PLAS160_QCF/RefAddr/19/Encoding=String
    PLAS160_PUT/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/2/Encoding=String
    PLAS160_Q/RefAddr/3/Type=PER
    MYPUT/RefAddr/8/Type=QU
    MYPUT/RefAddr/7/Encoding=String
    PLAS160_Q/RefAddr/7/Encoding=String
    MYPUT/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_Q/RefAddr/7/Type=FIQ
    PLAS160_QCF/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/6/Type=CCS
    MYPUT/RefAddr/9/Content=
    PLAS160_QCF/RefAddr/10/Type=SFIPS
    PLAS160_QCF/RefAddr/10/Encoding=String
    PLAS160_PUT/RefAddr/3/Encoding=String
    PLAS160_QCF/RefAddr/20/Type=TM
    MYPUT/RefAddr/8/Encoding=String
    PLAS160_Q/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/14/Type=MBS
    PLAS160_QCF/RefAddr/17/Content=5000
    PLAS160_QCF/RefAddr/2/Type=QMGR
    PLAS160_PUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
    PLAS160_QCF/RefAddr/7/Content=\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
    MYPUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
    MYPUT/RefAddr/3/Content=-2
    PLAS160_PUT/RefAddr/0/Type=VER
    MYPUT/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/18/Type=TCM
    PLAS160_QCF/RefAddr/9/Encoding=String
    PLAS160_QCF/RefAddr/11/Content=false
    PLAS160_QCF/RefAddr/1/Content=1
    PLAS160_Q/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/11/Encoding=String
    PLAS160_QCF/RefAddr/20/Encoding=String
    PLAS160_PUT/RefAddr/4/Type=CCS
    PLAS160_PUT/RefAddr/4/Encoding=String
    PLAS160_QCF/RefAddr/14/Content=10
    PLAS160_QCF/RefAddr/4/Content=1414
    PLAS160_Q/RefAddr/9/Content=
    MYPUT/RefAddr/9/Encoding=String
    MYPUT/RefAddr/0/Content=6
    MYPUT/RefAddr/1/Type=EXP
    PLAS160_Q/RefAddr/9/Encoding=String
    PLAS160_PUT/RefAddr/8/Type=QU
    PLAS160_Q/RefAddr/0/Content=6
    PLAS160_Q/RefAddr/0/Type=VER
    MYPUT/RefAddr/5/Type=TC
    PLAS160_Q/RefAddr/3/Content=-2
    PLAS160_QCF/RefAddr/0/Encoding=String
    PLAS160_PUT/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/21/Content=
    PLAS160_Q/RefAddr/4/Type=CCS
    MYPUT/RefAddr/9/Type=QMGR
    PLAS160_QCF/RefAddr/21/Encoding=String
    PLAS160_PUT/RefAddr/9/Content=
    PLAS160_QCF/RefAddr/12/Encoding=String
    PLAS160_PUT/RefAddr/5/Encoding=String
    MYPUT/RefAddr/0/Encoding=String
    PLAS160_Q/RefAddr/8/Type=QU
    PLAS160_Q/RefAddr/0/Encoding=String
    PLAS160_PUT/RefAddr/0/Content=6
    PLAS160_Q/FactoryName=com.ibm.mq.jms.MQQueueFactory
    PLAS160_PUT/RefAddr/3/Content=-2
    PLAS160_QCF/RefAddr/7/Type=CT
    PLAS160_QCF/RefAddr/1/Encoding=String
    PLAS160_QCF/RefAddr/11/Type=SPAG
    PLAS160_QCF/RefAddr/21/Type=TQPFX
    PLAS160_QCF/RefAddr/13/Encoding=String
    PLAS160_QCF/RefAddr/22/Encoding=String
    PLAS160_PUT/RefAddr/6/Encoding=String
    PLAS160_QCF/RefAddr/15/Type=FIQ
    PLAS160_QCF/RefAddr/3/Type=HOST
    MYPUT/RefAddr/1/Encoding=String
    PLAS160_PUT/RefAddr/1/Type=EXP
    PLAS160_QCF/RefAddr/19/Type=MNST
    PLAS160_QCF/RefAddr/2/Encoding=String
    PLAS160_PUT/RefAddr/5/Type=TC
    PLAS160_QCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
    PLAS160_QCF/RefAddr/14/Encoding=String
    PLAS160_QCF/RefAddr/18/Content=true
    MYPUT/RefAddr/2/Type=PRI
    PLAS160_QCF/RefAddr/8/Content=0
    MYPUT/RefAddr/4/Content=1208
    MYPUT/RefAddr/2/Encoding=String
    PLAS160_PUT/RefAddr/9/Type=QMGR
    PLAS160_Q/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_Q/RefAddr/1/Encoding=String
    MYPUT/RefAddr/7/Content=1
    PLAS160_Q/RefAddr/1/Type=EXP
    MYPUT/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/12/Content=true
    PLAS160_QCF/RefAddr/2/Content=QM_gsplvp006_vm2
    PLAS160_Q/RefAddr/7/Content=1
    PLAS160_QCF/RefAddr/3/Encoding=String
    PLAS160_Q/RefAddr/5/Type=TC
    PLAS160_QCF/RefAddr/15/Content=1
    PLAS160_QCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
    MYPUT/RefAddr/1/Content=-2
    PLAS160_PUT/RefAddr/7/Encoding=String
    PLAS160_QCF/RefAddr/15/Encoding=String
    PLAS160_Q/RefAddr/9/Type=QMGR
    MYPUT/RefAddr/3/Encoding=String
    PLAS160_Q/RefAddr/1/Content=-2
    PLAS160_Q/RefAddr/2/Encoding=String
    PLAS160_Q/RefAddr/4/Content=1208
    PLAS160_QCF/RefAddr/8/Type=CTO
    PLAS160_PUT/RefAddr/7/Content=1
    PLAS160_QCF/RefAddr/22/Content=1
    PLAS160_QCF/RefAddr/12/Type=UCP
    PLAS160_QCF/RefAddr/0/Type=VER
    PLAS160_QCF/RefAddr/4/Encoding=String
    PLAS160_QCF/RefAddr/22/Type=MRET
    PLAS160_QCF/RefAddr/16/Type=LA
    PLAS160_PUT/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_QCF/RefAddr/4/Type=PORT
    PLAS160_PUT/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/16/Encoding=String
    PLAS160_PUT/RefAddr/1/Content=-2
    PLAS160_PUT/RefAddr/4/Content=1208
    PLAS160_Q/RefAddr/3/Encoding=String
    PLAS160_PUT/RefAddr/2/Type=PRI
    PLAS160_PUT/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/5/Encoding=String
    MYPUT/RefAddr/3/Type=PER
    PLAS160_PUT/RefAddr/9/Encoding=String
    PLAS160_QCF/RefAddr/17/Encoding=String
    MYPUT/RefAddr/4/Encoding=String
    PLAS160_Q/RefAddr/2/Type=PRI
    MYPUT/RefAddr/7/Type=FIQ
    PLAS160_Q/RefAddr/4/Encoding=String
    PLAS160_QCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
    PLAS160_QCF/RefAddr/16/Content=
    PLAS160_Q/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/6/Content=819
    PLAS160_QCF/RefAddr/19/Content=true
    PLAS160_QCF/RefAddr/9/Content=0
    MYPUT/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/0/Encoding=String
    MYPUT/RefAddr/8/Content=PLAS160_PUT
    PLAS160_QCF/RefAddr/10/Content=false
    MYPUT/RefAddr/5/Encoding=String
    PLAS160_QCF/RefAddr/0/Content=6
    Appendix 3 Node definition
    Appendix 4 - Node JMSTarget Connectors Properties
    Appendix 5 integrationgateway.properties JMS configuration section
    ## JMS configuration Section
    #The JNDIFactory Classnames for Weblogic, IPlanet, MQSeries.
    #ig.jms.JMSProvider.JNDIFactory.Weblogic=weblogic.jndi.WLInitialContextFactory
    #ig.jms.JMSProvider.JNDIFactory.IPlanet=com.sun.jndi.fscontext.RefFSContextFactory
    ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
    #ig.jms.JMSProvider.JNDIFactory.OracleApplicationServer=com.evermind.server.rmi.RMIInitialContextFactory
    # Enter the number of Queue listners to instantiate
    #ig.jms.Queues=1
    # For each queue specify the following properties
    # Name
    # Provider
    # JMSFactory name (which is binded to the JNDI)
    # MessageSelector (optional Message Filter)
    # JNDI System File URL
    # JMS User
    # JMS Password
    # Example :
    #ig.jms.Queue1=QUEUE_VAS
    #ig.jms.Queue1.Provider=MQSeries
    #ig.jms.Queue1.JMSFactory=QCF
    # ig.jms.Queue1.MessageSelector=
    #ig.jms.Queue1.Url=file:/D:/apps/IBM/WebSphereMQ/Java
    # ig.jms.Queue1.User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.Password=EncryptedPassword
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    #IBInfoHeaders
    #ig.jms.Queue1.MessageName=QE_F18_ASYNC
    #ig.jms.Queue1.MessageVersion=VERSION_1
    #ig.jms.Queue1.RequestingNode=FromNode
    #ig.jms.Queue1.DestinationNode=ToNode
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    #ig.jms.Queue1.NodePassword=EncryptedRequestingNodePassword
    #ig.jms.Queue1.SubChannel=SubChannel
    # Enter the number of Topic Subscribers to instantiate
    # ig.jms.Topics=1
    # For each Topic specify the following properties
    # Name
    # Provider
    # JMSFactory name (which is binded to the JNDI)
    # MessageSelector (optional Message Filter)
    # JNDI System File Url
    # JMS User
    # JMS Password
    # Example :
    # ig.jms.Topic1=ExampleTopic
    # ig.jms.Topic1.Provider=MQSeries
    # ig.jms.Topic1.JMSFactory=TopicConnectionFactory
    # ig.jms.Topic1.MessageSelector=
    # ig.jms.Topic1.Url=file:c:/
    # ig.jms.Topic1.User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Topic1.Password=EncryptedPassword
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    #IBInfo Headers
    #ig.jms.Topic1.MessageName=QE_F18_ASYNC
    #ig.jms.Topic1.MessageVersion=VERSION_1
    #ig.jms.Topic1.RequestingNode=FromNode
    #ig.jms.Topic1.DestinationNode=ToNode
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    #ig.jms.Topic1.NodePassword=EncryptedRequestingNodePassword
    #ig.jms.Topic1.SubChannel=SubChannel
    #For sending error either ErrorQueue or ErrorTopic must be configured
    #If both exists, errors are only sent to ErrorQueues.
    #Configure the Error-Queue configuration
    # ig.jms.ErrorQueue=ErrorQ
    # ig.jms.ErrorQueue-Provider=Weblogic
    # ig.jms.ErrorQueue-User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.ErrorQueue-Password=sam
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    # ig.jms.ErrorQueue-JMSFactory=TopicConnectionFactory
    # ig.jms.ErrorQueue-Url=file:c:/
    #Configure the Error-Topic configuration
    # ig.jms.ErrorTopic=Error
    # ig.jms.ErrorTopic-Provider=IPlanet
    # ig.jms.ErrorTopic-User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.ErrorTopic-Password=sam
    # ig.jms.ErrorTopic-JMSFactory=TopicConnectionFactory
    # ig.jms.ErrorTopic-Url=file:c:/
    ## End of JMS configuration Section
    # Profile Information
    # Set it to either TRUE or FALSE
    ig.ProfileInformation=FALSE
    #End-Of Profile Information
    ##EIPTestTool Properties
    #Class name of the Gateway Manager to use during processing
    #ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.EIPTestToolGatewayManager
    #Contains a true or false value.
    #True for LoopBack
    #ig.EIPLoopBack=TRUE
    #Contains the directory path that will be used
    #to store request/response files during recording.
    #ig.EIPOutputDirectory=c:/temp/output
    # Number of ig.EIPMsgProp.N.propFile's
    #ig.EIPMsgProp.count=0
    #Certification root directory
    #ig.EIPInputDirectory=c:/temp/input
    #MessageProperty file names with locations.
    #ig.EIPMsgProp.1.propFile=c:/temp/input/properties/pro1.xml
    #ig.EIPMsgProp.2.propFile=c:/temp/input/properties/pro2.xml
    #Overrides input directory for an EIP
    #ig.EIPMsgProp.1.inputDirectory=c:/temp/input/properties1/
    #EIPNodemapFileName
    #ig.EIPNodeMap=c:/temp/nodemap.xml
    ##End of EIPTestToolProperties
    #File connector password.
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    ig.fileconnector.password=EncryptedPassword
    #End of file connector properties.
    ## Query Access Services (QAS) Configuration Section.
    # QAS Repository Home Directory. This is the directory where Query result blocks will be
    # temporarily persisted.
    # Example:
    #ig.qas.repositoryHomeDir=C:/QASRepository
    # Uncomment the following line and replace the value with the actual QAS Repository Home Directory.
    #ig.qas.repositoryHomeDir=<Full-Path-For-Directory>
    ## END of QAS Configuration.
    ## AS2 Connector Properties.
    # These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
    # REQUIRED:
    # AS2 KeyStore Properties
    # Uncomment the following two lines to specify your key keystore path and password.
    # Use the PSCipher.bat utility to encrypt the keystore password.
    # example:
    # ig.AS2.KeyStorePath=C://pt846//webserv//peoplesoft//keystore//pskey
    # ig.AS2.KeyStorePassword=GD9klUFw8760HVaqeT4pkg==
    # OPTIONAL:
    # AS2 Log Directory, logs all incoming and outgoing AS2 requests and responses.
    # Uncomment and specify the correct directory name to enable logging.
    # example:
    # ig.AS2.LogDirectory = c://temp//as2//logs
    ## End of AS2 Connector Properties
    ## AS2ListeningConnector Only Properties.
    # OPTIONAL:
    # AS2From and AS2To http header parameters are required on all incoming AS2 messages. These parameters must
    # map to PeopleSoft node definitions either directly or indirectly via AS2 From & To map specifications.
    # AS2 From & To Map
    # This map translates incoming AS2From and AS2To http header parameters into PeopleSoft node names.
    # This property is not required if your incoming messages use AS2From and AS2To parameters that match
    # existing PeopleSoft node definitions.
    # ig.AS2.AS2ListenerMap.From.<AS2From>= Specify the PSFT Source Node Name.
    # ig.AS2.AS2ListenerMap.To.<AS2To>= Specify the PSFT Target Node Name.
    # This example translate AS2From from AS2SENDER to PSFT_SRC_NODE, and AS2To from AS2RECEIVER to PSFT_TGT_NODE.
    # example:
    # ig.AS2.AS2ListenerMap.From.AS2SENDER=PSFT_SRC_NODE
    # ig.AS2.AS2ListenerMap.To.AS2RECEIVER=PSFT_TGT_NODE
    # AS2 Message name
    # Message name used to publish AS2 transactions.
    # Use this property if the incoming AS2 Message Name is not in the HTTP Header or the URL.
    # Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters .
    # when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
    # AS2 From & To map above.
    # ig.AS2.<source>.<target>.MessageName= Specify the Message Name
    # example:
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.MessageName=AS2_ORDER_REQUEST
    # These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
    # REQUIRED:
    # AS2 Certificates
    # CertificateAlias is the certificate of the AS2 Listening Node used to decrypt incoming messages.
    # SignerCertificateAlias is the certificate of the AS2From trading partner of Listening Node used to verify
    # the incoming signature.
    # Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters
    # when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
    # AS2 From & To map above.
    # ig.AS2.<source>.<target>.CertificateAlias = Specify the target AS2 Listening Node certificate alias.
    # ig.AS2.<source>.<target>.SignerCertificateAlias = Specify the source AS2From trading partner certificate alias.
    # example:
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.CertificateAlias=<GeneratedAS2certificatealias>
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.SignerCertificateAlias=<GeneratedAS2certificatealias>
    ## End of AS2ListeningConnector Only Properties
    ## AS2 Target Connector Properties
    # These Properties need to be set to use the AS2TargetConnector
    # AS2 Original Request Information Log Directory
    # This is required for Async MDN only. The Async MDN receiver uses this directory
    # to find original request information.
    # example:
    # ig.AS2.AS2Directory=c://temp//as2
    ## END of AS2 Target Connector Properties.
    #XML dtd lookup flag
    # true - enable dtd reference lookup dtd on gateway. this is also the default value.
    # false - disable dtd reference lookup on gateway.
    ig.dtdLookup=true
    # Maximum active connections to be cached on gateway
    # These are connections from gateway to peoplesoft application server
    # Caching connections will improve integration broker throughput
    ig.connection=10
    #####################

  • Configuration/Workspace/Designer.xml file missing

    My Designer.xml file is missing. Anyone know where can I find this?

    save the following to Designer.xml and move to C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\Workspace
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <panelset>
      <application/>
      <document maximize="true" rect="0 0 500 500"/>
      <panelframe dock="left" height="801" width="282" x="0" y="12">
        <panelcontainer expanded="true" height="118" visible="true">
          <panel height="118" id="tools" unconstrainedheight="736" unconstrainedwidth="30" width="278"/>
        </panelcontainer>
        <panelcontainer expanded="true" height="637" visible="true">
          <panel height="637" id="droverproperties" unconstrainedheight="114" unconstrainedwidth="278" width="278"/>
        </panelcontainer>
      </panelframe>
      <panelframe dock="right" height="801" width="212" x="1" y="12">
        <panelcontainer expanded="true" height="350" visible="true">
          <panel column0id="1" column0width="230.00" column1id="2" column1width="230.00" column2id="3" column2width="70.00" column3id="4" column3width="135.00" column4id="5" column4width="70.00" filename="" height="350" id="droverlibrary" previewwithgrid="0" previewwithmoviebackground="1" sortasending="1" sortcolumn="1" splitter="0.34" unconstrainedheight="300" unconstrainedwidth="278" width="208"/>
        </panelcontainer>
        <panelcontainer expanded="true" height="114" visible="true">
          <panel height="114" id="align" unconstrainedheight="114" unconstrainedwidth="208" width="208"/>
          <panel height="114" id="info" unconstrainedheight="114" unconstrainedwidth="208" width="208"/>
          <panel height="114" id="transform" unconstrainedheight="114" unconstrainedwidth="208" width="208"/>
        </panelcontainer>
        <panelcontainer expanded="true" height="268" visible="true">
          <panel height="268" id="mixer" unconstrainedheight="268" unconstrainedwidth="208" width="208"/>
          <panel height="268" id="swatches" unconstrainedheight="268" unconstrainedwidth="208" width="208"/>
        </panelcontainer>
      </panelframe>
      <panelframe dock="top" height="146" width="543" x="0" y="0">
        <panelcontainer expanded="true" height="123" visible="true">
          <panel height="123" id="drovertimeline" isInLayerMode="false" unconstrainedheight="180" unconstrainedwidth="600" width="539"/>
          <panel height="123" id="keyframeeditor" unconstrainedheight="180" unconstrainedwidth="600" visibleTab="false" width="539"/>
          <panel height="123" id="output" unconstrainedheight="180" unconstrainedwidth="600" visibleTab="false" width="539"/>
          <panel height="123" id="compiler errors" unconstrainedheight="180" unconstrainedwidth="600" visibleTab="false" width="539"/>
        </panelcontainer>
      </panelframe>
    </panelset>

  • [svn] 4494: Added tests to hit channels and services configuration exceptions

    Revision: 4494
    Author: [email protected]
    Date: 2009-01-12 16:12:09 -0800 (Mon, 12 Jan 2009)
    Log Message:
    Added tests to hit channels and services configuration exceptions
    checkintests: passed
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/error.t xt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/service s-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/services- config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/error. txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/servic es-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/messaging-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/er ror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/se rvices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/services- config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/error.t xt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/service s-config.xml

    my connectivity is okay, I'm getting errors from domain controller itself, I checked and the network is okay, but  for the record here is my ipconfig /all
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : server
       Primary Dns Suffix  . . . . . . . : ***.tk
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : ***.tk
    Ethernet adapter Ethernet:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
    n
       Physical Address. . . . . . . . . : 00-0C-29-32-7E-79
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 213.233.***.***(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 213.233.***.1
       DNS Servers . . . . . . . . . . . : 127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

  • Configure the log4j.xml file

    Hello All,
    I am trying to configure the log4j.xml file, so that i can get differnet logging messages based on the level to different log files. for ex: info messages in info.log, debug messages in debug.log and so on...i tried using the below...but, no luck.
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
    <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
    <appender name="UCF_Exception" class="org.apache.log4j.RollingFileAppender">
         <param name="File" value="UCF_Exception.log"/>
         <param name="Append" value="false"/>
         <param name="MaxFileSize" value="1000KB"/>
         <param name="MaxBackupIndex" value="2"/>
         <layout class="org.apache.log4j.xml.XMLLayout">
              <param name="LocationInfo" value="true"/>
         </layout>
    </appender>
    <log4j.logger.UCFExceptionLogger>
         <level value ="debug"/>
         <appender-ref ref="UCF_Exception" />
    </log4j.logger.UCFExceptionLogger>
    </log4j:configuration>
    getting exception
    log4j:WARN No appenders could be found for logger (UCFExceptionLogger).
    log4j:WARN Please initialize the log4j system properly.
    Can someone help me...

    I'm not 100% sure this is possible with log4j, but if it is then you've still got some errors in your log4j.xml file
    Change
    <log4j.logger.UCFExceptionLogger>
       <level value ="debug"/>
       <appender-ref ref="UCF_Exception" />
    </log4j.logger.UCFExceptionLogger>to
    <logger name="UCFExceptionLogger>
       <level value="debug"/>
       <appender-ref ref="UCF_Exception" />
    </logger>
    The log4j jar includes a DTD. You can use the free version of XMLSpy to validate your log4j.xml file against it.
    Steve                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Disable SSLv3 on Exchange 2010 server (Poodle Vulnerability)

    Following the recommendation to mitigate the Poodle vulnerability, we tried disabling SSLv3 and making sure that users had TLS 1.1 and 1.2 enabled on their browsers.
    We used IIScrypt to turn off SSLv3 (v2 was already disabled from before).
    Now, OWA works fine, and users are able to connect via the Web.
    Internally, users are also able to connect with Outlook 2010/2013.
    however, users are not able to connect via Outlook from outside (Outlook anywhere)
    In the event viewer you get an error:
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 70. The Windows SChannel error state is 105.
    I opened a ticket with Microsoft but the lady working on the case wanted us to re-enable SSLv2 which is out of the question.
    Anybody has seen this issue as well?

    Hi Max
    could you provide the steps to turn off SSLv3 . Is it from the registry
    http://support.microsoft.com/kb/187498 ?
    Mat A
    Yes. Copy and paste this into a text file and save as a .reg file, then double click on the file to add to the registry of the server
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Client]
    "DisabledByDefault"=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server]
    "Enabled"=dword:00000000
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Maybe you are looking for

  • Sales order BOM is not reflecting in sales order

    Hi Guys, I have created a sales order in which all the items of the sales BOM (ex:A-a1,a2,a3).have been exploded.My strategy is make to order and i am dealing with valuated stock. Now i have created sales order BOM for that particular sales order thr

  • Get parent Collectionset in create Collection

    Hi All,      In Create Collection, How to get parent collectionset. Thanks, Dung

  • Class Not Found in j2ee

    Hi, I'm able to build the Converter example, run the DeployTool, etc. But when I run the j2ee server, I get the following: Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/corba/se/internal/util/IdentityHashtable at com.sun.corba.ee

  • Locked Up Installing Windows 7

    I tried to use a full install 32 bit dvd to install Windows 7 on my vintage 2007 Core 2 Duo iMac AL and am in trouble.  The iMac has SL 10.6.8  installed and a full software update was performed before starting the W7 exercise.  The W7 installation f

  • The absence of oraclemaps.js file

    I have to enter the following code, while am trying to setup the Oracle Maps Workbook <script language="JacaScript" src="/mapviewer/fsmc/jslib/oraclemaps.js"></script> but the oraclemaps.js file does not exist in the dir. What can i do;