Errors while setting up ActiveSpaces Clustering with TLS enabled for Spotfire Servers

Errors while setting up ActiveSpaces Clustering with TLS enabled for Spotfire Servers

book

Article ID: KB0079993

calendar_today

Updated On:

Products Versions
Spotfire Server All versions from 7.5 until 7.14

Description

As part of setting up Active Spaces clustering with TLS as in documentation below, we have to create a policy file.
https://docs.tibco.com/pub/spotfire_server/7.11.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-307A9023-DEE2-4427-A40F-FCAB82398415.html

When you try to run the following commands to create a as-policy.txt file, it may throw errors as shown below:
*************************************************************
as-admin> create security_policy policy_name "as-policy" policy_file "as-policy.txt" encrypt false
SYS_ERROR (action_failed -
    Failed Command: create security_policy policy_name "as-policy" policy_file "as-policy.txt" encrypt false
    Cause: security_config_error
    Message: Policy file already exists: as-policy.txt

s-admin> create security_token domain_name "AS-DOMAIN" policy_file "<Spotfire Server install folder>/nm/trust/as-policy.txt" token_file "<Spotfire Server install folder>/nm/trust/mytoken.txt
YS_ERROR (action_failed -
   Failed Command: create security_token domain_name "AS-DOMAIN" policy_file "<Spotfire Server install folder>/nm/trust/as-policy.txt" tok
n_file "<Spotfire Server install folder>/nm/trust/mytoken.txt
   Cause: arg_invalid
   Message: Recognition Exception <missing STRINGLITERAL>

s-admin> show member for metaspace 'spotfire'
YS_ERROR (action_failed -
   Failed Command: show member for metaspace 'spotfire'
   Cause: arg_invalid
   Message: Missing token at position 11 <missing EOF>
            show member for metaspace 'spotfire'
*************************************************************

Issue/Introduction

This article talks about the errors encountered while setting up ActiveSpaces clustering with TLS enabled on Spotfire Servers

Resolution

The errors are due to a missing as-common.jar file in the Spotfire Server install folder. Copy the as-common.jar file to the WEB-INF\lib folder on each Spotfire Server in the cluster to resolve this issue.