BSSV Deployment failing after updating Server manager to 8.98.4.13

[RonWeasley]

Hi,
We are on WebLogic 10.3.2.0 on RedHat Linux x86-64 with tools release 8.98.4.3. We are upgrading our tools release and got the server manager (console & agents) upgraded to 8.98.4.13 in that process.
After that, our BSSV deployments are failing and we are getting the below error:

Jan 14, 2014 7:20:57 PM com.jdedwards.mgmt.targets.owl.OWLDomain startAdminServer
FINER: Start of the admin server 'AdminServer' failed: Return code '1'
Jan 14, 2014 7:20:57 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer configureJAASAuthenticator
WARNING: Error creating authentication provider: Failed to start the admin server. Check the agent log and admin server log for possible problems.
Jan 14, 2014 7:20:57 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer configureJAASAuthenticator
WARNING: Error during lookup of E1 authentication provider: Failed to start the admin server. Check the agent log and admin server log for possible problems.
Jan 14, 2014 7:20:57 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer stageDeployment
INFO: E1 BSSV custom authentication provider could not be set up. This is likely due to one or more WebLogic managed servers that were running. In order for Server Manager to configure the E1 BSSV authentication provider automatically, all WebLogic managed servers must be stopped.

Could anyone advise anything? I double-checked we are MTR-ok. The admin server stops during deployment process and never comes up.

Regards,
Ron

 

[altquark]

did you create a new BSSV package with this tools release ?

Did you manage to put the older BSSV package back and did that work ?

Are you able to manually start the Weblogic server and attach to the console ?

 

[anunay]

Hi Ron,

We are currently on 8.11, 8.98.04.07.10 and are planning to upgrade to 8.98.04.13 and are looking for known issues.

Could you please tell us if this issue has been fixed and what step did you take for the same.

Also I would appreciate if you could share any other issues that you faced?

Thanks
Anunay

 

[RonWeasley]

Hi Anunay,
The solution is to add E1BSSVAuthenticator manually. Below is the process that Oracle provides - it worked for me:

<font color="blue">
Manually Install E1BSSVAuthenticator under Weblogic Admin Console

ACTION PLAN
===============
a. Ensure only the AdminServer is running and other managed servers within the domain are stopped
b. Goto WLS Admin Console > security realms > myrealm > providers tab
c. Check if there is a E1BSSVAuthenticator listed as a Provider Type, perform below steps only if E1BSSVAuthenticator is not listed
d. Copy the E1BSSVAuthenticator.jar from C:\JDEdwards\E900\SYSTEM\Classes (on deployment server or from Fat Client System\Classes dir) to the dir C:\Oracle\Middleware\wlserver_10.3\server\lib\mbeantypes
e. Stop and start the AdminServer of WLS domain
f. Navigate to the WLS Admin Console > security realms >myrealm > providers tab
g. Click “Lock & Edit”
h. Click New button
i. Enter Name = E1BSSVAuthenticator
j. From the Type dropdown, select E1BSSVAuthenticator and Click OK
k. Go to the Providers screen by selecting “Providers” link in the breadcrumb list of links at the top of the screen
l. In the list of providers, click on DefaultAuthenticator, set the control flag to SUFFICIENT
m. Click Save
n. Go to the Providers screen again.
o. Click the E1BSSVAuthenticator set the control flag to “REQUIRED”
p. Click Save
q. Click “Activate Changes” button.
r. Stop and start the AdminServer
s. Create a new BSSV Instance from SM Console or start the already created BSSV Instance
t. During the BSSV Package deploy, the steps of creating/configuring the Authenticator will be skipped
u. Perform BSSV Package deployment and verify that the deployment succeeds
v. Perform BSSV Package re-deployment and verify that also succeed


Doc ID 1470910.1 - E1BSSVAuthenticator.jar fails to create on the Provider tab in Weblogic Server 10.3.x </font>

Hope this helps!!!
Thanks,
Ron

 

[anunay]

Thanks a lot Ron