Jetty server starts and generates the warning “Failed to located Inbound WebService security profile, aborting redeploy”
Article ID: KB0079042
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Web Services Server Plug-in | 11.3.0 |
Description
iProcess Web Services Server Plug-in Jetty starts but displayed the message:
**TIBCO** Inbound WebService checking whether to redeploy
**TIBCO** WARNING: Failed to located Inbound WebService security profile, aborting redeploy
The issue normally occurs after updating the Jetty to use a different version of the Java JRE.
For example, Jetty was using a Java 1.6.0 JRE but has been updated to use a Java 1.7.0 or 1.8.0 Java JRE
The default security profile called "Inbound" is held in the iProcess database table EAIWS_SECURITY_PROFILE
Jetty is unable to read the definition of the security profile from the database.
**TIBCO** Inbound WebService checking whether to redeploy
**TIBCO** WARNING: Failed to located Inbound WebService security profile, aborting redeploy
The issue normally occurs after updating the Jetty to use a different version of the Java JRE.
For example, Jetty was using a Java 1.6.0 JRE but has been updated to use a Java 1.7.0 or 1.8.0 Java JRE
The default security profile called "Inbound" is held in the iProcess database table EAIWS_SECURITY_PROFILE
Jetty is unable to read the definition of the security profile from the database.
Issue/Introduction
iProcess Web Services Server Plug-in Jetty starts but displayed the message:
**TIBCO** Inbound WebService checking whether to redeploy
**TIBCO** WARNING: Failed to located Inbound WebService security profile, aborting redeploy
Environment
TIBCO iProcess Engine 11.6.1
TIBCO iProcess Web Services Server Plug-in 11.3.0
All supported platforms and databases
Resolution
The resolution is to re-create the "Inbound" security profile.
1. Stop the Jetty server
2. Delete the security profiles in the iProcess database using the SQL:
delete from EAIWS_SECURITY_PROFILE;
3 Start Jetty
4 Run securitymanager.sh and create a security profile with the name Inbound (just enter the name and create – no need to specify any other settings)
5 Restart Jetty
Jetty will start and be able to load the Inbound security profile.
Any custom security profiles will also have to be re-created using the securitymanager
Before performing the above ensure that the following scripts under JETTY_HOME/jetty-6.1.25 have the same path for JAVA_BIN
jetty.sh
passwordmanager.sh
securitymanager.sh
urladmin.sh
This will ensure that all the utilities use the same versions of Java.
On a Windows platform the scripts have extension .cmd rather than .sh
1. Stop the Jetty server
2. Delete the security profiles in the iProcess database using the SQL:
delete from EAIWS_SECURITY_PROFILE;
3 Start Jetty
4 Run securitymanager.sh and create a security profile with the name Inbound (just enter the name and create – no need to specify any other settings)
5 Restart Jetty
Jetty will start and be able to load the Inbound security profile.
Any custom security profiles will also have to be re-created using the securitymanager
Before performing the above ensure that the following scripts under JETTY_HOME/jetty-6.1.25 have the same path for JAVA_BIN
jetty.sh
passwordmanager.sh
securitymanager.sh
urladmin.sh
This will ensure that all the utilities use the same versions of Java.
On a Windows platform the scripts have extension .cmd rather than .sh
Additional Information
TIBCO iProcess Web Services Server Plug-in Installation Guide
Feedback
Yes
No
Powered by
