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 am needing to run a process written as a Windows command file (cmd) prior to having an ETL request do its work. I added the cmd file as a pre-extract procedure in the ETL request. When run, it appears to be treated as an FEX procedure based upon the errors received.
My questions are whether a) it is possible to run a Windows cmd file as a procedure within an ETL request and b) if not possible, where can I find documentation that contains the FEX commands so that I can translate the cmd functionality to an FEX procedure.
Actually, I would like to know about the documentation regardless of whether I can use the cmd or not.
Regards, Clint
Posts: 2 | Location: Overland Park, KS | Registered: November 28, 2005
If you have an InfoResponse ID, login on the Tech Support web site and then access i-Base. By logging in first, you can download the PDF file and/or view the HTMLHelp version.
It has been quite a while since I worked on this, so I'm not exactly sure whether the following is correct. However, it may be enough to point you in the right direction.
The key is that all of the ETL procedures need to be FEX procedures. I created one with the following. Of course the locations and file names will differ for you, but I'm sure you can figure it out.
As I recall, this did work, but as I said it has been quite a few months since then. We never did put that ETL into production, and I have a lot of different things I tried, so I'm not 100% sure if this is the right one.
Good luck!
Clint
Posts: 2 | Location: Overland Park, KS | Registered: November 28, 2005