ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Feature 'SegTtyp' not found - MB SAP Adapter

Post new topic  Reply to topic
 Feature 'SegTtyp' not found - MB SAP Adapter « View previous topic :: View next topic » 
Author Message
sudeepd2005
PostPosted: Mon Nov 11, 2013 6:19 am    Post subject: Feature 'SegTtyp' not found - MB SAP Adapter Reply with quote

Novice

Joined: 28 Oct 2013
Posts: 22

Hello,

I am working on SAP Adapters . As of now I was able to receive IDOC from SAP to the MB Adapter.
Problem started when I moved the same code from DEV to QA. I am getting a strange error while receiving a IDOC on SAP Input node of my Adapter flow.


Idoc Number - NULL
( ['MQROOT' : 0x115d7b370]
(0x01000000:Name):RecoverableException = (
(0x03000000:NameValue):File = 'MbErrorHandler.java' (CHARACTER)
(0x03000000:NameValue):Line = 137 (INTEGER)
(0x03000000:NameValue):Function = 'createMessage' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 0 (INTEGER)
(0x03000000:NameValue):Number = 3442 (INTEGER)
(0x03000000:NameValue):Text = 'Caught exception from DESPI' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'SAP2MB.INPUT' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'SAP2MB_PD1_IDOC.inadapter' (CHARACTER)
)
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'MbErrorHandler.java' (CHARACTER)
(0x03000000:NameValue):Line = 286 (INTEGER)
(0x03000000:NameValue):Function = 'throwableToMbException' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 0 (INTEGER)
(0x03000000:NameValue):Number = 3450 (INTEGER)
(0x03000000:NameValue):Text = 'Caught exception from DESPI' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'java.lang.RuntimeException: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'SegTtyp' not found. (http:///temp.xml, 8, 1
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'SegTtyp' not found. (http:///temp.xml, 8, 1
Feature 'SegTtyp' not found. (http:///temp.xml, 8, 1
Feature 'SegTtyp' not found. (http:///temp.xml, 8, 1
' (CHARACTER)
)
)
)
)




Thanks in advance.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Nov 11, 2013 7:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY

Have you considered that maybe your IDOC does not look the same in each of your dev /qa/prod environments?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
sudeepd2005
PostPosted: Tue Nov 12, 2013 5:54 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2013
Posts: 22

Hi fjb_saper,

Thanks for your reply.

I have checked , there is no change in the structure.
I am stuck on this from past 2 weeks , tried every possible solution to resolve the issue.
Now client is blowing some serious heat on me.
Back to top
View user's profile Send private message
new_to_wmb8
PostPosted: Tue Nov 12, 2013 8:42 am    Post subject: Reply with quote

Centurion

Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India

try to reconnect the SAP adapter configuration and check for QA that username and password is correct.
Back to top
View user's profile Send private message
sudeepd2005
PostPosted: Wed Nov 13, 2013 12:09 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2013
Posts: 22

Tried that too, but still the error persists.
Back to top
View user's profile Send private message
Simbu
PostPosted: Wed Nov 13, 2013 12:25 am    Post subject: Reply with quote

Master

Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India

Hope this post might help you to resolve this issue. Similar kind of exception reported here.
Quote:

http://www.mqseries.net/phpBB2/viewtopic.php?t=59559&sid=05ffe749160b8212435d5150a9f8cda2
Back to top
View user's profile Send private message
mapa
PostPosted: Wed Nov 13, 2013 1:43 am    Post subject: Reply with quote

Master

Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden

Are you certain the DEV and QA have the same version of the SAP Adapter?
What are those versions?

If not the same, are you deploying the bar-file created for DEV to QA or are you re-building it in another toolkit then deploying?

Some things you might want to try:

- Make sure you do a mqsireload on the EG after deployment of your updated adapter if you are redeploying.

- Try to delete the flow, msgset and adapter in QA and then deploy again.

- Do a JCO trace on the inbound adapter to see if that gives you more info.
Back to top
View user's profile Send private message Visit poster's website
sudeepd2005
PostPosted: Wed Nov 13, 2013 4:25 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2013
Posts: 22

Mapa,

Initially I had changed the connection configurations in MB Adapter , compiled the bar file & deployed.
Now I have created a new workspace , created new MsgSet & Adapters included the the adapter node in MsgFlow and deployed. Waiting to test it.

Somehow the EG is not responding now , Not going my way from past cpl of days.

Will update you folks once I test the adapter.

Thanks for the help!!!
Back to top
View user's profile Send private message
sudeepd2005
PostPosted: Fri Nov 15, 2013 2:38 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2013
Posts: 22

It worked after creating fresh workspace, connectors & Adapters.

Thanks to everyone !!!
Back to top
View user's profile Send private message
aky201086.amit
PostPosted: Fri Mar 28, 2014 4:19 pm    Post subject: Reply with quote

Newbie

Joined: 24 Feb 2011
Posts: 4

I am also facing the same issue but difference is that i am using generic Idoc routing flow (having ALE SAP adapter in pass through mode) which routes the unparsed Idocs to respective processing flows.

In processing flow, MQInput node is used to parse the input idocs (created msgset from the schema obtained from Adapter connection wizard). Used below link to configure the MQinput node.

http://pic.dhe.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.pattern.eis.doc%2Feis%2Fsap%2Fidocfanout%2Fidocflows.htm&resultof%3D%2522%2569%2564%256f%2563%2522%2520%2522%2572%256f%2575%2574%2569%256e%2567%2522%2520%2522%2572%256f%2575%2574%2522%2520

I am getting error in MQInput node while parsing the idocs.

Below is the received parsedException
(0x01000000:Name ):ParserException = (
(0x03000000:NameValue):File = 'MbAdapterDirector.java' (CHARACTER)
(0x03000000:NameValue):Line = 566 (INTEGER)
(0x03000000:NameValue):Function = 'parseIdoc' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 3472 (INTEGER)
(0x03000000:NameValue):Text = 'exception caught in parseIDOC' (CHARACTER)
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'MbErrorHandler.java' (CHARACTER)
(0x03000000:NameValue):Line = 318 (INTEGER)
(0x03000000:NameValue):Function = 'throwableToMbException' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 3450 (INTEGER)
(0x03000000:NameValue):Text = 'exception during IDOC Parsing' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'SegTtyp' not found. (http:///temp.xml, 7, 17)
Feature 'SegTtyp' not found. (http:///temp.xml, 7, 17)
Feature 'SegTtyp' not found. (http:///temp.xml, 7, 17)
' (CHARACTER)
)
)

Any suggestion on this (as per the last update of this post,created in new workspace also but no luck)...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Feature 'SegTtyp' not found - MB SAP Adapter
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.