As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I don't know if this is the exactly for you but you might try to define XDXMLExtract Service (com.ibi.agents.XDXMLExtract). It allows you to use XPATH expression to locate your element (for example < Header >) and then to define optional name for the root of the extracted subtree (like < Hdr >)
Otherwise... why not to use transform?
Regards, Rivo
iSM 6.0 iDM 7.6.5 - 7702 WF 7.6.4 - 7702
All output formats
Posts: 23 | Location: Tallinn, Estonia | Registered: July 31, 2009
1. Create an XML file listener. 2. Create an XML to XML Transform. Use the file you wish to modify as the input dictionary and data. Use the same file as the output dictionary. Use "Automap" to map the input to Output. In the Output column right click on the "Header" element. Rename it to "Hdr". 3. Create a process flow with your transform followed by a file(write) object. 4. Create your channel using all those elements.
I am not sure of your level of knowledge so I do not know if this is too high level, or too detailed.
Let me know if you have any questions.
------ Livin' down on the cube farm. Left, right, right.
iWay 5.6 Windows Excel, Tab-delimited, XML
Posts: 23 | Location: Minnesota | Registered: July 27, 2009
can not use transform. the xml coming in will not always be the same Structure. The only thing that will always be there is the the parent tag </Header> witch needs to get rename because it is now a researved word in Unix.
IWay SM 5.6, 6.01, 6.1, 6.9, 7.0 EDI, XML, XSD, WF 8.0, DM 77,8.0 asp.net, SQL Server
I ay this jokingly, but it is shades of truth. "Your requirements are wrong". Why does it have to be in iWay?
To me it looks like what you are trying to do is better suited to an OS tool instead of a iWay. In my experience iWay does not handle variablity of this sort with ease. I notice your signature says you are in Windows. If you can wait until the file would be on the UNIX platform SED or AWK would be the ticket.
Otherwise maybe RivoU suggestion of XMLXDextract shold be investigated.
------ Livin' down on the cube farm. Left, right, right.
iWay 5.6 Windows Excel, Tab-delimited, XML
Posts: 23 | Location: Minnesota | Registered: July 27, 2009
exactly for you but you might try to define XDXMLExtract Service (com.ibi.agents.XDXMLExtract). It allows you to use XPATH expression to locate your element (for example < Header >) and
I've used XDXMLExtract before to rename a node. However, I don't think it would work in this case. The service will only bring back the node specified and all child nodes, not sibling nodes. I have an open case on this issue Ray, I'll let you know when I hear back.
Mike. Vancouver, BC
iWay Adapter Manager version 5.5.005.SP5(i55005SP511) running on Windows platform iWay Service Manager version 5.6.000.SM running on Windows platform.