CWWKB8016E 480 Liberty Server, WOLA connector from CICS to z/OS Connect EE

The reason code 480 is:

Description: The client was not able to become authorized to invoke the register function.
Action: This is an unexpected condition. Ensure that the target server is running and that the zosLocalAdapters service is configured in the server instance.

When I check the server.xml for the zosLocalAdapters configuration element it shows:

     <zosLocalAdapters
         wolaGroup="group"
         wolaName2="name2"
         wolaName3="name3" />

This appears to be correct and will be security checked against the CBIND class for profile BBG.WOLA.group.name2.name3 The documentation for z/OS Connect EE V2 topic on Registering CICS with the WebSphere optimized local adapter (WOLA) shows step 2 for confirming the WOLA registration from the zCEE server which matches your supplied server messages.log:

 [8/5/16 9:14:19:709 GMT] 00000015
 com.ibm.ws.zos.channel.wola.internal.WOLAChannel             I
 CWWKB0501I: The WebSphere Optimized Local Adapter channel registered with the Liberty profile server using the following name: group name1 name2
 [8/5/16 9:14:23:227 GMT] 00000021
 om.ibm.ws.app.manager.rar.internal.RARApplicationHandlerImpl A
 J2CA7001I: Resource adapter ola installed in 1.930 seconds.

The BBOOUT log shows the "BBOC START TRUE" successfully enabled as described in step 4a of the documentation:

 BBOC Fri Aug  5 10:04:49 2016 0000083 WOLA TRACE 1: Enabling BBOATRUE
 exit.…
 BBOC Fri Aug  5 10:04:49 2016 0000083 WOLA TRACE 1: Exit enabled
 successfully.…
 BBOC Fri Aug  5 10:04:49 2016 0000083 WOLA TRACE 0: Return Code: 0
 Reason Code: 0…
 BBOC Fri Aug  5 10:04:49 2016 0000083 WOLA TRACE 0: Elapsed time:
 0.000000 seconds…
 BBOC Fri Aug  5 10:04:49 2016 0000083 WOLA TRACE 0: Elapsed CPU time:
 0.000497 seconds

The cause is most likely an authorization problem for module BBGZSCFM.

Can you confirm the following...

Create SERVER profiles for z/OS.

Create SERVER profiles for the optimized local adapter authorized service. Use the following Time Sharing Option (TSO) commands:

     RDEF SERVER BBG.AUTHMOD.BBGZSAFM.LOCALCOM UACC(NONE)
     PERMIT BBG.AUTHMOD.BBGZSAFM.LOCALCOM CLASS(SERVER)   ACCESS(READ)   ID(wlpuser1)
     RDEF SERVER BBG.AUTHMOD.BBGZSAFM.WOLA UACC(NONE)
     PERMIT BBG.AUTHMOD.BBGZSAFM.WOLA CLASS(SERVER)  ACCESS(READ)  ID(wlpuser1)

Create a SERVER profile for the authorized client module BBGZSCFM and permit the Started Task user ID of the Liberty server to the profile. This action enables a Liberty server to load the z/OS Authorized client services. To enable a server that is running as WLPUSER1 to access the authorized client module:

 RDEF SERVER BBG.AUTHMOD.BBGZSCFM UACC(NONE)
 PERMIT BBG.AUTHMOD.BBGZSCFM CLASS(SERVER) ACCESS(READ) ID(wlpuser1)

Create SERVER profiles for optimized local adapter authorized client service. Use the following TSO commands:

     RDEF SERVER BBG.AUTHMOD.BBGZSCFM.WOLA UACC(NONE)
     PERMIT BBG.AUTHMOD.BBGZSCFM.WOLA CLASS(SERVER) ACCESS(READ) ID(wlpuser1)

Can you confirm these security settings?

Refer to the z/OS Connect Enterprise Edition V2 topic Configuring the Liberty Angel process and z/OS authorized services.