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

Custom schema registration fails for the Binary application on sites without EventQ. What should I do?

As EventQ is not installed by default in TeamForge 19.0 (though you can install it separately, if required), the custom schema (custom_schema) registration fails for the Binary application.

Use the following curl command to register the custom_schema for the Binary application on sites where EventQ is not installed.

curl -H "Accept: application/json" -H "Content-Type: application/json" -H "X-EventQ-Session: " /orc/api/1/schemas -d '{
"api_version": "1",
"custom_schema": {
"event_time": ,
"name" : "Binaries",
"schema_id" : "binary_artifact",
"schema_version" : 2,
"fields" : [
"event_type",
"operation",
"event_time",
"schema_id",
"schema_version",
"remote_id",
"name",
"description",
"build_number",
"associated_remote_id",
"repository_id",
"repository_url",
"artifact_url",
"group_id",
"artifact_id",
"artifact_version",
"artifact_type",
"artifact_classifier",
"link_to",
"component",
"component_of",
"created_by"
],
"important" : [],
"parsed" : [],
"required" : [
"remote_id",
"event_type",
"operation",
"event_time",
"schema_id",
"schema_version",
"link_to"
],
"hidden" : [
"repository_url",
"artifact_url"
]
}
}'

Note that you may have to generate a session token and use it in the curl command along with your host name. Here’s an example X-EventQ-Session token:

 "X-EventQ-Session: eyJraWQiOiIxIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiJhZG1pbiIsImF1ZCI6WyJzb2FwNjAiLCJjdGYiLCJzdm4iLCJnZXJyaXQiXSwibmJmIjoxNTUyNDM3NjQ4LCJhbXIiOlsidXJuOmN0ZjphbXI6dXB3ZCJdLCJpc3MiOiJ1cm46Y3RmOmlzczp0Zi1pZHAiLCJleHAiOjE1NTI0NDEyNDgsImlhdCI6MTU1MjQzNzY0OCwianRpIjoiNDNlMGQzZjQtNzc4YS00MTI0LThlMzktNDdlYzZjMmE2YWM2In0.dI1ASh-nUuh-kjr3Av6tVstUFwJVIvc4k27iISZwdCDjFL63hgVtZNgm87l91UGDKgJB8efdW6__OSXjQsU_-n35466TFcERIbhMFveKzGA-V53t5Vb-jucUe0K18fuEZSA1duwXKZOf5Pyi0-tE9DwiNCUosJsjwOT1rUGbOGo" https://cu513.cloud.maa.collab.net/orc/api/1/schemas

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: ctf_19.0 faq