1 2 Previous Next 17 Replies Latest reply: Aug 14, 2013 7:54 AM by Manwendra RSS

    PeopleSoft 8.53 Integration Error with Oracle SES

    Manwendra


      My System Details are :

       

      Machine 1

      Hostname : host1

      Port : port1

      Application : PeopleSoft 8.53 + HCM 9.2 + Oracle 11g

      OS : Windows 7 (64 Bit)

       

      Machine 2

      Hostname : host2

      Port : port2

      Application :Oracle Secure Enterprise Search 11.1.2.2.0

      OS : Windows 2008 Server (64 Bit)

       

      No Error was encountered while installation and systems started without any error.

       

      Now when trying to integrate PeopleSoft with Oracle SES.

      I entered all the details as per installation docs at PeopleTools->Search Framework->administration->Search Instance

       

      When I click on Ping I encounter the following error :

       

      Ping Test Result: Failure. Exception caught GetMessageText: No default message. (0,0) (262,612)

       

      I am behind a proxy server and have made the required entries in integrationGateway.properties files for proxy server.

      Also have added userid:pwd in Proxy-Authorization property for HTTPTARGET connector ID.

       

      The Errorlog.html contains the following error:

      ----------------------------------------------------------------------------------------------------------------------------------------

      Type - Error
      ErrorLevel - Standard Gateway Exception
      Description - HttpTargetConnector:ExternalApplicationException. External System responded with an Error status.
      Exception -  PeoplesoftListeningConnector: GeneralFrameworkException 
      MessageCatalog  
      MessageSet: 158  MessageID: 10623  MessageParms: HttpStatusCode returned : 407

      -------------
      Stack Trace
      -------------
      com.peoplesoft.pt.integrationgateway.common.ExternalApplicationException: HttpTargetConnector:ExternalApplicationException. External System responded with an Error status.
      at com.peoplesoft.pt.integrationgateway.targetconnector.HttpTargetConnector.send(HttpTargetConnector.java:1159)
      at com.peoplesoft.pt.integrationgateway.service.BasicConnectorInvocator.execute(BasicConnectorInvocator.java:131)
      at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.invokeService(GatewayManager.java:147)
      at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.connect(GatewayManager.java:191)
      at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.doPost(PeopleSoftListeningConnector.java:183)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
      at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.service(PeopleSoftListeningConnector.java:86)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
      at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
      at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
      at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
      at com.peoplesoft.pt.integrationgateway.common.IBFilter.doFilter(IBFilter.java:84)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
      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:2273)
      at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
      at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

      ------------
      Request
      ------------

       

      Message-ID: <1975883609.1375092327640.JavaMail.userId@host1>
      Date: Mon, 29 Jul 2013 15:35:27 +0530 (IST)
      Mime-Version: 1.0
      Content-Type: multipart/related; boundary="Integration_Server_MIME_Boundary"
      Content-ID: PeopleSoft-Integration-Broker-Internal-Mime-Message
      PeopleSoft-ToolsRelease: 8.48

      --Integration_Server_MIME_Boundary
      Content-Type: text/plain; charset=UTF-8
      Content-Transfer-Encoding: 8bit
      Content-Disposition: inline
      Content-ID: IBInfo

      <?xml version="1.0"?><IBInfo><ExternalOperationName><![CDATA[GETAPIVERSION.V1]]></ExternalOperationName><OperationType>sync</OperationType><From><RequestingNode><![CDATA[PSFT_HR]]></RequestingNode><Protocol>http</Protocol><WS-Security><WSTokenType><![CDATA[]]></WSTokenType><WSTokenEncrypted></WSTokenEncrypted><WSTokenSigned></WSTokenSigned><WSTokenEncryptLevel></WSTokenEncryptLevel><WSRequestAliasName><![CDATA[]]></WSRequestAliasName></WS-Security><SAML-CertAlias><![CDATA[]]></SAML-CertAlias><SAML-QualifierName><![CDATA[]]></SAML-QualifierName><SAML-Issuer><![CDATA[]]></SAML-Issuer><SAML-SubjectName><![CDATA[]]></SAML-SubjectName><SAML-Signature><![CDATA[]]></SAML-Signature><SAML-TokenData>***deleted for security purposes****</SAML-TokenData><URIResourceIndex>-1</URIResourceIndex><SegmentsUnOrder>N</SegmentsUnOrder></From><ContentSections><ContentSection><ID>ContentSection0</ID><ContentType>text/plain; charset=UTF-8</ContentType><ContentTransfer>8bit</ContentTransfer><NonRepudiation>N</NonRepudiation></ContentSection></ContentSections><Connector><ConnectorClassName><![CDATA[HttpTargetConnector]]></ConnectorClassName><ConnectorParameters><ConnectorParam><Name><![CDATA[Method]]></Name><Value><![CDATA[POST]]></Value></ConnectorParam><ConnectorParam><Name><![CDATA[URL]]></Name><Value><![CDATA[http://host2:port2/search/api/admin/AdminService]]></Value></ConnectorParam><ConnectorParam><Name><![CDATA[SOAPUpContent]]></Name><Value><![CDATA[Y]]></Value></ConnectorParam></ConnectorParameters><ConnectorHeaders><Header><Name><![CDATA[sendUncompressed]]></Name><Value><![CDATA[Y]]></Value></Header><Header><Name><![CDATA[Content-Type]]></Name><Value><![CDATA[text/xml; charset=utf-8]]></Value></Header></ConnectorHeaders></Connector><AttachmentSection ResponseAsAttachment="N"></AttachmentSection></IBInfo>
      --Integration_Server_MIME_Boundary
      Content-Type: text/plain; charset=UTF-8
      Content-Transfer-Encoding: 8bit
      Content-ID: ContentSection0
      Content-Disposition: inline

      <?xml version="1.0"?>
      <getAPIVersion xmlns="http://search.oracle.com/Admin"><credentials xmlns=""><userName>eqsys</userName><password>***deleted for security purposes****</password></credentials></getAPIVersion>
      --Integration_Server_MIME_Boundary--

      ------------
      Response
      ------------

      Message-ID: <2136182902.1375092327641.JavaMail.userId@host1>
      Date: Mon, 29 Jul 2013 15:35:27 +0530 (IST)
      Mime-Version: 1.0
      Content-Type: multipart/related;
      boundary="----=_Part_8_1450854121.1375092327639"
      Content-ID: PeopleSoft-Integration-Broker-Internal-Mime-Message

      ------=_Part_8_1450854121.1375092327639
      Content-Type: text/plain; charset=UTF-8
      Content-Transfer-Encoding: 8bit
      Content-Disposition: inline
      Content-ID: IBInfo

      <?xml version="1.0"?><IBInfo><Status><StatusCode>40</StatusCode><MsgSet>158</MsgSet><MsgID>10623</MsgID><Parameters count="1"><Parm>HttpStatusCode returned : 407</Parm></Parameters><DefaultTitle>Integration Gateway Error</DefaultTitle></Status><ContentSections><ContentSection><ID>ContentSection0</ID><ContentType>text/plain; charset=UTF-8</ContentType><ContentTransfer>8bit</ContentTransfer><NonRepudiation>N</NonRepudiation></ContentSection></ContentSections></IBInfo>
      ------=_Part_8_1450854121.1375092327639
      Content-Type: text/plain; charset=UTF-8
      Content-Transfer-Encoding: 8bit
      Content-Disposition: inline
      Content-ID: ContentSection0

      <HEAD><TITLE>Proxy Authorization Required</TITLE></HEAD>
      <BODY BGCOLOR="white" FGCOLOR="black"><H1>Proxy Authorization Required</H1><HR>
      <FONT FACE="Helvetica,Arial"><B>
      Description: Authorization is required for access to this proxy</B></FONT>
      <HR>
      <!-- default "Proxy Authorization Required" response (407) -->
      </BODY>

      ------=_Part_8_1450854121.1375092327639--

      ---------------------------------------------------------------------------------------------------------------------------------------------------

       

      I have checked the required entries in integrationGateway.properties files for proxy server.

      Also have checked the userid:pwd entered in Proxy-Authorization property for HTTPTARGET connector ID.

      I have restarted the servers and machines as well but still the same error.

       

      Kindly help me ?

        • 1. Re: PeopleSoft 8.53 Integration Error with Oracle SES
          HakanBiroglu

          Couple of things to check:

          Make sure the SES database is started prior to starting the SES middletier (StartSES from the Start menu)

           

          Make sure to save the changes in the PeopleSoft SES Instance page prior to clicking on Ping.

           

          Make sure Integration Broker is setup correctly and user has proper roles (Search Server, Search Administrator, Search Developer)

          • 2. Re: PeopleSoft 8.53 Integration Error with Oracle SES
            Manwendra

            Thanks for your response.

             

            I checked all the three points but still the same error.

            • 3. Re: PeopleSoft 8.53 Integration Error with Oracle SES
              HakanBiroglu

              The error you get is HttpStatusCode returned : 407

               

              407 indicates proxy authentication failure, so your issue is still at PeopleSoft side.

               

              Please have a look at following thread and see if it helps in setting the correct proxy settings.

              https://forums.oracle.com/thread/959288

              • 4. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                RCC

                I agree with Hakan, sounds like your problem is getting to the proxy.

                Is the SES server on the same network as PS?  Or is it really somewhere else? Is this some kind of home setup since you are running PS on Win 7?  If SES is on the same network as PS, I would drop the proxy config and test that way first.  Get it working without the extra complexity, then add in Proxy.  You can test connectivity from PS to SES with telnet or just browsing to SES. 

                • 5. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                  Manwendra

                  RCC wrote:

                   

                  I agree with Hakan, sounds like your problem is getting to the proxy.

                  Is the SES server on the same network as PS?  Or is it really somewhere else? Is this some kind of home setup since you are running PS on Win 7?  If SES is on the same network as PS, I would drop the proxy config and test that way first.  Get it working without the extra complexity, then add in Proxy.  You can test connectivity from PS to SES with telnet or just browsing to SES.

                  Thanks for the response RCC.

                  The PS is a Demo Instance being used for study purpose. Both the machines are on the same network.

                  I tried the ping after removing the entries in integrationGateway.properties files for proxy server and it worked.

                   

                  Ping, Test Login and Validate are successful.

                   

                  I get the following error when I check Proxy Login.

                   

                  Proxy login failed : Invalid credentials for the federation entity (262,1317) (262,1318)

                   

                  I have created Federation Trusted Entity key by the name HCM92 on Oracle SES side and am using the same ID and password in the Query Service Credentials on the Search Instance Properties Page.

                   

                  I was not getting any error in any log file related to this.

                   

                  Kindly help.

                  • 6. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                    HakanBiroglu

                    I had a similar issue a couple of days ago, which was resolved by starting SES components in the correct order.

                     

                    Please try following:

                    Shutdown SES middletier and database.

                    Start SES database.

                    Wait till it is started

                    Start SES middletier(StartSES from the Start menu)

                    Try the Proxy login again

                     

                    Hope it helps.

                     

                    Hakan

                    • 7. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                      Manwendra

                      Thanks for the response HakanBiroglu.

                       

                      I tried this but the issue remained.

                      One thing that I found out was that I was unable to telnet my PS Instance from my Oracle SES machine.

                      I have asked my admin team for their help on opening the port it may take some time.

                       

                      Can this proxy issue be due to this ?

                      • 8. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                        HakanBiroglu

                        Ahh, you are able to ping SES from PS.

                        But you are not able to connect from SES machine to PS machine.

                        Perhaps it is a firewall issue and ports have to opened as you mention.

                        • 9. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                          RCC

                          In addition to checking with your networking team, try temporarily disabling the Windows firewall on your Windows 7 system (or forcing open the port Weblogic is listening on). You might be able to connect locally since your on the PC, but the local Windows firewall may be blocking everything else.  I've never used proxy so I'm somewhat unfamiliar with the problems that could occur with them.  I'm unclear on why you need a proxy if both systems are on the same network.

                          • 10. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                            Manwendra

                            I get the following error when I check Proxy Login.

                            Proxy login failed : Error with IdentityPlugin.validateUser:

                            oracle.search.sdk.common.PluginException: javax.xml.soap.SOAPException: Message send failed: proxy.company.com

                            at oracle.search.plugin.security.identity.psft.PsftIdentityPlugin.validateUser(PsftIdentityPlugin.java:334)

                            at oracle.search.query.internal.AuthnTask.run(AuthnTask.java:136)

                            (262,1317) (262,1318)

                             

                            I suspect the error is related to my company proxy server. proxy.company.com.

                            But I have removed the entries in integrationGateway.properties files for proxy server for Ping and Test Login to be successful.

                             

                            When I kept these entries Ping was not working after removing them Ping started working but Proxy Login is giving error.

                             

                            Any suggestions would be helpful.

                            • 11. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                              HakanBiroglu

                              I think you are mixing two things.

                              A proxyserver as we know it in the infra is the "port" that regulates/restrict you as an end user of a machine to other machines/internet.

                               

                              Proxy in PeopleSoft/SES terms (an unfortunate naming) is just an unique attribute, this is not your proxy server!

                               

                              See sections:

                              Creating a Federated Trusted Entity

                              Defining a Search Instance in the PeopleSoft System

                               

                              Do not set the proxy server in PeopleSoft configuration to connect to servers that are running on the same network, because you are able to ping to the SES server.

                              • 12. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                                Manwendra

                                Thanks for the response HakanBiroglu.

                                 

                                I do understand the difference.

                                I suspect the error is related to my company proxy server. proxy.company.com.

                                Proxy login failed : Error with IdentityPlugin.validateUser:

                                oracle.search.sdk.common.PluginException: javax.xml.soap.SOAPException: Message send failed: proxy.company.com

                                at oracle.search.plugin.security.identity.psft.PsftIdentityPlugin.validateUser(PsftIdentityPlugin.java:334)

                                at oracle.search.query.internal.AuthnTask.run(AuthnTask.java:136)

                                (262,1317) (262,1318)

                                 

                                The name proxy.company.com is the name of our company proxy server. The error message contains the name that's why I was suspecting that it has some role in the error.

                                 

                                I want to basically Define a Search Instance in the PeopleSoft System and out of Ping, Test Login, Proxy Login and Validate buttons on the Page.

                                 

                                Ping, Test Login and Validate are successful.

                                 

                                I get error on Proxy Login.

                                 

                                If I get this working I'll complete the setup of Search Instance.

                                • 13. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                                  HakanBiroglu

                                  What name, password did you provide for the Federated Trusted Entity in SES (entity name, password) during task Creating a Federated Trusted Entity?

                                  To be clear this is not your proxyserver.

                                  What name, password did you provide for the Query Service Credentials in PS (proxy name, password) during task Defining a Search Instance in the PeopleSoft System?

                                  To be clear this is not your proxyserver.

                                   

                                  Entity name in SES needs to match proxy name in PS and of course the passwords need to match

                                  • 14. Re: PeopleSoft 8.53 Integration Error with Oracle SES
                                    Manwendra

                                    Thanks for the response HakanBiroglu.

                                    HakanBiroglu wrote:

                                     

                                    What name, password did you provide for the Federated Trusted Entity in SES (entity name, password) during task Creating a Federated Trusted Entity?

                                     

                                    Name : PSSES

                                    Password : PSSES

                                     

                                    HakanBiroglu wrote:

                                     

                                    What name, password did you provide for the Query Service Credentials in PS (proxy name, password) during task Defining a Search Instance in the PeopleSoft System?

                                    Proxy Name : PSSES

                                    Password : PSSES

                                     

                                    I have given the same entry.

                                    1 2 Previous Next