As of SBM 11.3, it doesn't look possible to remove TLS 1.0 from both the Server.xml ( Tomcat ) and the SChannel Registry key ( IIS ) and have deploys reach the "Completed" status. The deploy itself will succeed and your changes will get deployed. It is just the callback from the Application Engine to the Repository telling the system the deploy completed that fails so the status stays in "Waiting" forever.
INFO -- Application Engine callback at 4/14/15 3:29 PM. INFO -- The following errors or warnings were received: ERROR -- Parser Error at file C:/Program Files/Serena/SBM/ Application Engine /mst50586/application.xml, line 7, char 12 Message: no declaration found for element 'Locale' Failed to complete the import at 4/14/15 3:29 PM.
This may happen if the GSOAP application pool identity does not have access to the Application Engine directory. Check which identity is used for the GSOAP pool in IIS and then check the NT security of the Application Engine folder in the SBM installation directory. If GSOAP is using an identity like Network Service, make sure Network Service has full control over that folder.
Looking at the folder c:\Program Files\Serena\Business Mashups\ Application Engine \bin\resourcetmp\TTResourcePackage\ the administrator will notice a subfolder and within pairs of .txt and .res files. One or more .txt
"ORA-06552 PL/SQL Compilation unit analysis terminated" "Character set name is not recognized" This error was seen when an Oracle db was exported from an Oracle 10 db and imported to Oracle 11g
In the Process Apps Blueprints section, find the version of the blueprint that matches the current Release Control Version, and has the comment, “Created by importing …” Deploy the blueprint.
\Log directory, it will be clear that the deploy promote succeeds with a message similar to Sent the process app to Application Engine , awaiting callback .
If the AE SBM (ALF) Event was exported and used prior to 10.1.3 then deploying the Process Application that raises the event will implicitly change the event definition to use new constant names, "ItemId_TableRecId", "ItemId_TableId" and "Project_ProjectId"; this will cause the issue with the second Process Application that imported the event definition.
The Application Repository callback URL handed to the Application Engine may vary or be inconsistent. This URL can be different depending on which AR communicates with the AE.
