SAC Content Export Issue - Connection

[Sujit]

Recently we had an issue where the Users reported that they were not able to see the SAC Report with data when they were trying to access the report in SAC in higher environment, and it was asking for Single-Sign-On Credentials, even though correct credentials was entered, there was a failure error.

• On initial analysis from the Activity Logs in SAC, it was found that the connections were changed by the User.


• On further analysis, it was identified that during migration of a recently developed SAC Stories from SAC lower environment to SAC higher environment, the SAC connection component from lower environment was migrated to higher environment, which updated the existing connection by overwriting the SAC connection details in higher environment, subsequently pointing it to SAC on lower environment.

Connection is automatically selected and added, when Story on is selected for export

In the latest upgrade of SAC, when a Package is created to export SAC Story content from one environment to another,

• The application automatically selects the dependencies such as Folder Structure, Story and the Model(s) on which the Story is based.


• However, during the creation of the above Export Package, the underlying connection used by the story too was automatically selected and added to the export package.


• In the past, it has been observed that connection was not automatically added to the Package


• As the SAC connection in lower environment is SSO enabled the Authentication Method property in higher environment connection too changed to SSO.


• As SAC on higher environment is not on SSO platform, this resulted in connectivity error shown to the users.

 

Resolution:

Following steps resolved the issue,

• The connection Properties in SAC – in higher environment manually updated to point back to SAC – same environment.


• Connection properties were updated as listed below

o    Description

o    Port No.

o    Client

o    Host Name

o    Authentication Method

This resolved the issue, and Users were successfully able to login and access the Stories.

 

Steps to avoid re-occurrence:

When a Package is created to export SAC Story content from one environment to another,

• The application automatically selects the dependencies such as Folder Structure, Story and the Model(s) on which the Story is based.


• During the creation of the above Export Package, the underlying connection used by the Story was automatically selected and added to the Package. In the past, it has been observed that connection was not automatically added to the Package.


• As this is an additional new component added by the application, which was not the case earlier. It is mandatory to remove this connection component by explicitly unchecking the selection box, before exporting the Package to overwrite the existing components in the Target environment.


• Contents of the Package should be reviewed before Exporting from the destination environment and before Importing into the Target environment to avoid import of non-necessary components.