Banner
+ Reply to Thread
Results 1 to 8 of 8

Thread: Issue in Carrier Synchronization Program
                  
    Bookmark and Share    
   

  1. #1
    Member ashwinrrao is on a distinguished road
    Join Date
    Oct 2007
    Posts
    75
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Issue in Carrier Synchronization Program

    Hi,
    We are enabling the standard EBS to OTM integration between OTM 6.2 and EBS R12. We have performed all the setups in EBS and are trying to syn up carriers using the Carrier Synchronization program. The program errors out with the following error message

    Failed to read wsdl file at: "http://ITGAPPS2:8001/soa-infra/services/default/WshSendRefDataStlToOtm/client?wsdl", caused by: java.net.UnknownHostException. : http://itgapps1.company.com: java.net.UnknownHostException: http://itgapps1.company.com

    apps2 is our SOA server and apps1 is our OTM server.

    The WSDL files are present at the soa-infra/services/default location and are visible from the SOA console. They are active. We tried shutting them down and restarting but same error appears.
    Also the error seems to point to an issue on the OTM side as the unknown host exception refers to the OTM server.

    Has anyone faced a similar issue?

    Regards,
    Ashwin

  2. #2
    Member ashwinrrao is on a distinguished road
    Join Date
    Oct 2007
    Posts
    75
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Re: Issue in Carrier Synchronization Program

    Conversely, if anyone has implemented this integration, can you let me know what Aq, DB and adapter settings you have used in SOA? As per the guide, it should be product name appended by adapter name. In my case the db adapter is named as wsh_ebsdbadapter. I am wondering whether it should be wsh_ebs or otm_ebs or something else.
    Regards,
    Ashwin

  3. #3
    Member ayush1312 is on a distinguished road
    Join Date
    Sep 2010
    Posts
    66
    Thanks
    11
    Thanked 6 Times in 6 Posts
    Rep Power
    4

    Re: Issue in Carrier Synchronization Program

    Quote Originally Posted by ashwinrrao View Post
    Hi,
    We are enabling the standard EBS to OTM integration between OTM 6.2 and EBS R12. We have performed all the setups in EBS and are trying to syn up carriers using the Carrier Synchronization program. The program errors out with the following error message
    Failed to read wsdl file at: "http://ITGAPPS2:8001/soa-infra/servi...tm/client?wsdl", caused by: java.net.UnknownHostException. : http://itgapps1.company.com: java.net.UnknownHostException: http://itgapps1.company.com
    apps2 is our SOA server and apps1 is our OTM server.
    The WSDL files are present at the soa-infra/services/default location and are visible from the SOA console. They are active. We tried shutting them down and restarting but same error appears.
    Also the error seems to point to an issue on the OTM side as the unknown host exception refers to the OTM server.
    Has anyone faced a similar issue?
    Regards,
    Ashwin
    Hey Ashwin,
    You are missing some small but important set ups.Please check your profile values set in EBS for EBS-OTM Integration. Can you check the values set for
    OTM: Proxy Port - Should be empty
    OTM: Proxy Server - Should be empty
    OTM: Servlet URI - http://host: port/GC3/glog.webserver.servlet.umt.Login
    WSH: BPEL Webservice URI for OTM - http://host: port/soa-infra/services/default
    Also i will advice to use IP address instead of DNS in the host part of the URL as sometimes SOA, OTM and EBS are installed in seperate boxes and the DBA doesn't make the host entry for one server in the other two, so it fails to recognise the host.

    Regards
    Ayush

  4. #4
    Member ashwinrrao is on a distinguished road
    Join Date
    Oct 2007
    Posts
    75
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Re: Issue in Carrier Synchronization Program

    Hi Ayush,
    Thanks for the update. I have all the setups mentioned by you done. I have used IP addresses only. I feel it is something to do with the adapter settings as running a test from the SOA console also returns an error.
    Just one question: for the OTM Servlet URL, do you really need the GC3/glog.webserver.servlet.umt.Login part after the host and port names?
    Regards,
    Ashwin

  5. #5
    Member ayush1312 is on a distinguished road
    Join Date
    Sep 2010
    Posts
    66
    Thanks
    11
    Thanked 6 Times in 6 Posts
    Rep Power
    4

    Re: Issue in Carrier Synchronization Program

    Yes Ashwin you have to give the complete URI. As far as the issue goes, if it is failing in the SOA console then please check the error in logs. If it says its related to the Adapter then please correct it.
    You need to check the JNDI that is used in the BPEL code and correspondingly find it in you SOA Admin Console under Deployments>>DB adapter>>Configuration>>Outbound Connection Pools . Please note the data source name used by that connection pool. After that match that data source name with the JNDI name in Services>> Data Sources. Then click the datasource against that JNDI and check the database connection details, this should be the database of the EBS instance which you are using. Also you can test it from the console if the datasource is working.

    Regards
    Ayush

  6. #6
    Member ashwinrrao is on a distinguished road
    Join Date
    Oct 2007
    Posts
    75
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Re: Issue in Carrier Synchronization Program

    Thanks Ayush! These pointers are extremely helpful. I will check these and see.
    Regards,
    Ashwin

  7. #7
    Member ashwinrrao is on a distinguished road
    Join Date
    Oct 2007
    Posts
    75
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Re: Issue in Carrier Synchronization Program

    Here's what I found.
    in the Db adapter path, i found multiple connection pools. But i am interested in the shipping integration so looked at the wsh_ebs adapter.
    I see that in the properties tab, there is a datasource name -> jdbc/CustomerDbConnectionDS2
    In the general tab, there is a JNDI name -> eis/DB/wsh_EbsDbAdapter

    When I go to Services -> Data Connections, I see a data source called CustomerDbConnectionDS2. So far so good.
    When I open this, the JNDI name says jdbc/CustomerDbConnectionDS2. This matches the datasource name (default setting) but not the JNDI name. Is that an issue? For some reason, testing the connection is disabled for me.

    I hope I am making sense :-)

    Regards,
    Ashwin

  8. #8
    Member ayush1312 is on a distinguished road
    Join Date
    Sep 2010
    Posts
    66
    Thanks
    11
    Thanked 6 Times in 6 Posts
    Rep Power
    4

    Re: Issue in Carrier Synchronization Program

    Hey ashwin,

    I believe you are new to Oracle SOA and so i will strongly recommend you to take help from somebody in your organization who has that background. Its very difficult from here without looking at your set ups to tell what is the issue? Moreover login with Admin privileges to have the complete control with you.
    Also please verify the DB URL inside your connection pool to check whether it is pointing to the correct EBS instance.

    Thanks
    Ayush


 

Similar Threads

  1. Shipping - Transportation Carrier Synchronization Error
    By soujanya in forum OTM / EBS / JDE E1 Integration
    Replies: 1
    Last Post: May 4th, 2012, 08:14
  2. Carriers Synchronization concurrent program error
    By JayVal in forum Integration and Data Mapping
    Replies: 0
    Last Post: April 7th, 2011, 15:31
  3. Carrier Commitment Issue
    By fish23112002 in forum Execution
    Replies: 2
    Last Post: April 12th, 2010, 11:12
  4. EBS Freight Carriers Synchronization
    By vsevs in forum OTM / EBS / JDE E1 Integration
    Replies: 0
    Last Post: September 29th, 2009, 07:43
  5. Error on Carriers Synchronization
    By darkside32 in forum OTM / EBS / JDE E1 Integration
    Replies: 0
    Last Post: December 1st, 2008, 23:54

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56