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 working a flow that will call Powershell scripts, but have had little luck. Initially I tried calling the .ps1 script directly (cmd /c C:\script1.ps1), but this failed. Instead of cmd /c C:\script1.ps1 I have created a .bat that calls the .ps1 script. This seems to work, but the flow always times out. I have tried exits within the ps1 and bat scripts to make sure they are exiting correctly, but that doesn't work. I have increased the timeouts, but that does not work either. This is a simple script that creates network maps and then creates a directory listing. It is a very simple flow to test with:
Start -> Service Object (cmd /c c:\Call_script1.bat) -> End
When I run the scripts directly on the iWay server they both work flawless and finish under 15 seconds.
I searched around FocalPoint and Google, but I am unable to find any info on iWay Service Objects calling a Powershell scripts. Any help would be greatly appreciated!
From our iWay folks: In the service object, you would use XDRunCmdAgent. The documentation is below. I think the answer is cmd /C lou.bat. If this does not work, please open a case with Customer Support Services for assistance. I assume the power shell script should be the same.
Thank you for your response on this. To answer your question and Lou's phone call, the flow works fine with a generic bat file. It seems like an issue with PowerShell and the script not letting iWay know that it has finished and to move onto the next step in the flow.