This issue has been resolved.

It turns out that WAS was run as root and when the RTC setup was run, it created some directories in /tmp.
Such as:
/tmp/contentservice
/tmp/versionedcontentservice

Then WAS was stopped and restarted running as the WASadmin user. This was done because it was discovered that they had mistakenly started WAS as root and this was in violation of some security compliance rules.

The RTC setup was re-started and RTC tried again to write to the above directories. However, these were created by root and therefore the WASadmin user could not write to them.

This issue was resolved by logging in as root and deleting the directories.

Once WAS was started as WASadmin and the RTC setup re-started, the directories in question were created by the proper user and the setup completed.

----------------- problem described below -------------------



Hi folks

I have a client that is hosting JTS, RTC and RRC in WAS.
(all 3.0.1.x products)

This is on linux.

They are having an issue in the Register Applications section of the setup wizard.

If the WAS process runs as root, they encounter no issues.
However, running WAS as root is not permitted in their organization.

So if they run WAS as some dedicated use (wasadmin for example) the register applications page is just blank and sits there.
They have let it run for up to 20 mins and nothing happens. They get no errors and no logs are generated.

Can anyone thing of a reason why the register applications step would care/require that WAS be running as root?

What does the register applications step actually do? Is there a manual work around they could perform to get around this step in the wizard?
They have tried installing the Jazz products as root and as a non-root user.

the only factor here *seems* to be whether WAS is run as root or a wasadmin user.

Thanks

Andy