• After upgrading from RSA Identity Governance and Lifecycle 7.0.1 to 7.1.0 P03 or 7.0.2 P05, when trying to open any workflow in the workflow editor results the following error:

Could not access HTTP invoker service at
[https://<server>:9443/wpServices/ServerConfigService];nested exception is 
java.net.SocketException:  unexpected end of file from server

• JVM arguments are specified as follows:

HTTPS needs to be defined as the connection protocol. Since this is not currently configurable in RSA Identity Governance & Lifecycle 7.1.0 P03 and 7.0.2 P05, it needs to be manually updated in the workpoint-client.properties file and the aveksaWFArtitectear  by following the steps below. These steps will allow you to use the 'https' protocol for opening workflows in the Workflow Editor.

1. From WebSphere console, uninstall the currently deployed Aveksa Workflow Editor:

1. In the WebSphere Console go to Applications > Application Types > Websphere enterprise application page.
2. Select Aveksa Workflow Editor and click Uninstall as shown below: 

2. Update the workpoint-client.properties file in acmConfig.jar within ACM-WebSphere-7.1.0_P03.tar as follows:
   1. Using 7-Zip, open ACM-WebSphere-7.1.0_P03.tar
   2. Double click on the folder named ACM-Websphere-7.1.0_P03.
   3. Open the aveksaWFArchitect.ear.
   4. Double click on /APP-INF/lib/.
   5. Open the acmConfig.jar.
   6. Open the workpoint-client.properties file in Notepad++ or any other text editor.
   7. Go to the Connection configuration section and update following lines, replacing http with https), as follows:

serverContextPath = https://${wp-client-hostname}:${wp-client-hostport}/wpServices
client.connect.URL = https://${wp-client-hostname}:${wp-client-hostport}/wpServices/xml

3. Save the updated workpoint-client.properties file.
4. Install the updated aveksaWFArchitect.ear file, using the steps below as documented in the "Install the Workflow Architect EAR File" section of the RSA Identity Governance and Lifecycle 7.1 Installation Guide​.

Procedure

1.  In the WebSphere console, initiate the installation:
   1. From Applications menu, select Application Types > Websphere Enterprise Applications, and click Install.
   2. Browse to the folder that contains the aveksaWFArchitect.ear file that you updated and saved. Select this aveksaWFArchitect.ear.
2. Proceed through the wizard, choosing the Fast Path.  Accept default values where not indicated otherwise.
3. For clusters only: 
   1. Select Map Modules to Servers.
   2. Select all modules, select the scope from the list of Clusters and Servers, and click Apply.
   3. The server associated with the module should be listed as the cluster. Click Next
4. In the Map Virtual Hosts for Web Modules screen, click Next.
5. For WebSphere 9.0.0.x only:  In the Metadata for Modules screen, enable the metadata-complete attribute checkbox and click Next.
6. Complete the installation of the ear. This process takes several minutes to complete.
7. Save changes to the master configuration.
8. Restart the application server, replacing server1 with your server name:

cd /opt/IBM/WebSphere/AppServer/bin
./stopServer.sh server1
ADMU116I: Tool information is being logged in file
          /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3201I: Server stop request issued.  Waiting for stop status.
ADMU4000I: Server server1 stop completed.
./startServer.sh server1
ADMU116I:  Tool information is being logged in file
          /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched.  Waiting for initialization status.
ADMU3000I: Server server1 is open for e-business; process id is 20969

9. Verify by logging into the Identity Governance & Lifecycle Admin Console (https://<host-name>:9443/aveksa/main).
   1. Open any workflow from Requests > Workflows.  
   2. Select any workflow. 
   3. The selected workflow will be opened in the workflow editor successfully as shown below:

​​​​​​​​​​​​​​