STAF Process Container not recognizing browser window

Before we investigate more fully, can you confirm that SAFS, STAF, and RFT are actually talking to each other correctly?

Do you have a successful execution and outcome of SAFS\Project\runTIDTest.bat?
The logs for these will be in SAFS\Project\Datapool\Logs.

What version of IBM Rational Functional Tester do you have installed?

Do you have a successful execution and outcome of SAFS\Project\runRFTTest.bat?
The logs for these will be in SAFS\Project\Datapool\Logs.

Do you see RFT successfully getting launched and shutdown during that RFTTest?

Can you provide the processcontainer.ini file that should have been produced by STAF ProcessContainer on exit?

Does your INI file file include sections like these below:

[SAFS_ENGINES]
First=org.safs.tools.engines.SAFSROBOTJ

[SAFS_ROBOTJ]
TESTDOMAINS=HTML JAVA WIN Flex
AUTOLAUNCH=TRUE
DATASTORE="C:\SAFS\datastorej"

[SAFS_DRIVER]
DriverRoot="C:\SAFS"


{:{>
Carl

Was RFT already installed when you installed SAFS? SAFS attempts to detect RFT at install time and perform some RFT setup, if found.

Did you follow this:
safsdev.github.io/sqabasic2000/SetupRobotJ.README.htm

The test results presented by RFTTest.txt indicates RFT was NOT attached to SAFS or STAF and could not be "seen" by the driver. If you saw RFT get launched and then go away, then likely it was because RFT did not like the version of the DatastoreJ project and upgrading it might help.

If there is an Error Log in RFT you should see what it is trying to tell you. Consider seeing if you can manually open\connect to the Functional Tester project at SAFS\DatastoreJ with RFT. It could be that the RFT project needs to be "updated" to conform to the new project format for your version of RFT.

You might not need to uninstall, but you might have to run the SAFS\SetupRationalClasspath.wsf file by double-clicking on it. Can you provide your System CLASSPATH environment setting. We should see what is and isn't in it. For example, are the SAFS Rational JAR files listed in the CLASSPATH?
The location from which you ran the install should also have a setup.log we could review to see if RFT was present at the time of the install.

Again, if you can manually go into that datastoreJ project from inside RFT you may find an RFT error log telling you what it might not have liked about running TestScript.

We can get additional information if you attempt a run with the SAFS DEBUG Log running:
safsdev.sourceforge.net/sqabasic2000/SAFSDevelopment.htm#exploredebuglog

If you have a browser that can play Flex SWF files:
safsdev.sourceforge.net/sqabasic2000/Using_Debug_Log.swf

This can be simplified down to:
Make sure STAF is running,
Launch SAFSTESTLOGStartup.bat,
Run your test,
Launch SAFSTESTLOGShutdown.bat,
Review the DEBUG Log.

The Debug might let us know what problems were encountered in launching or using RFT.

You can also attempt the following to run the SAFS RFT Engine Manually and see if it tells you what it doesn't like.
The normal working flow for the entire operation would be:

Launch STAF (if not already running)
Launch SAFS\Project\SAFSTESTLOG_Startup.bat (Debug Log CMD window appears and remains--watch this one for activity.)
Launch SAFS\Project\SAFSStartupSAFSProject.bat (Debug log shows launching of SAFS services. CMD window appears only briefly.)
Launch RFT manually and connect to the DatastoreJ Project
Place RFT into the Functional Tester Perspective
Right-Click the DatastoreJ "TestScript" and select "Run" (RFT goes into playback mode and remains there. Debug Log shows STAF connection.)
Launch SAFS\Project\runRFTTest.bat (Test window appears. SAFS Monitor Window appears. Lots of Debug Log activity until it stops)
Launch SAFS\Project\SAFSRobotJShutdown.BAT (RFT should shutdown. It may take a couple of attempts. The delay to shutdown can be a minute or two.)
Launch SAFS\Project\SAFSTESTLOG_Shutdown.bat (Debug Log should shutdown and CMD window goes away)

Note: in your SAFSRobotJShutdown.BAT, make sure the last STAF command is written as:

staf local sem pulse event safs/robotjdispatch

Older versions of this script have it written for an older version of STAF.