This section provides solutions to common issues with TeamForge-Binary integrations.

The TeamForge-Binary integration is down after enabling SSL. What should I do?

TeamForge-Binary integration is found to be down soon after enabling SSL on sites which initially had SSL disabled. You must update the base URL, go URL and end point URLs stored in Postgres to access your Binary servers.

Run the following query with the psql-wrapper script (/opt/collabnet/teamforge/runtime/scripts/psql-wrapper) to update the base URL, go URL and end point URLs.

update integrated_application set base_url='https://<url>', go_url='https://<url>', end_point='https://<url>' where name='Binaries';

Binary initialization fails at the end of provision. Why?

If SOAP services are not completely up and running during service startup, binary initialization fails at the end of provision. As a workaround, reinitialize binary with this command:

teamforge reinitialize -s binary
Tags for this page: faq