Liberty Plugin Generation for Front-end IIS Website
On the Liberty Application Server run the below commands:
On the Liberty application server, e.g. javaprod, stop the service that is running the Liberty server node. Run cmd.exe as administrator in
E:\IBM\WebSphere\Liberty\bin directory, start the server node from the cli. Example: server start hsc. This is necessary to be able to view the process in the jconsole.
Start jconsole, "E:\IBM\WebSphere\Liberty\java\java_1.8_64\bin\jconsole"
Select the process to connect to.


Connect, unsecure is fine.

P1 string = the path to the plugin root directory on the IIS frontend server, "E:\IBM\WebSphere\Plugins"
P2 string = the name given to the web server definition during setup with the Websphere Customization Toolbox, this will be the directory name in E:\IBM\WebSphere\Liberty\usr\servers\, i.e. hsc. Jfeprod for the production web server, it should be noted that hsc is the exception to this, it uses jfeprod as the p2 value, all other would be deptmap, grants, coi, etc.

Click the generatePluginConfig button.

You should get the method successfully invoked dialog box.
The plugin-cfg.xml file is created in the E:\IBM\WebSphere\Liberty\usr\serversapplicationname directory. Copy the plugin-cfg.xml file generated on the Liberty app server to the E:\IBM\WebSphere\Plugins\configwebservername on the frontend web server,
E:\IBM\WebSphere\Plugins\config\jfeprod for production.
In the command window stop the server node. Example: server stop hsc. Restart the service you stop at the beginning of this process so it no longer running under your account.
Now that we have generated a plugin we need to copy it the front-end server and make a couple of modifications.
Make a backup copy of the plugin-cfg.xml file in [\\jfeprod\e$\IBM\WebSphere\Plugins\config{_}applicationnamedirectory_|\\jfeprod\e$\IBM\WebSphere\Plugins\config\applicationnamedirectory] before proceeding.
2 lines that reference the keyrings in the plugin-cfg.xml you just generated need to be modified as seen in the following example.
FROM:
<Property Name="keyring" Value="keyring.kdb"/>
<Property Name="stashfile" Value="keyring.sth"/>
TO:
<Property Name="keyring" Value="E:\IBM\WebSphere\Plugins\config\coi\key.kdb"/>
<Property Name="stashfile" Value="E:\IBM\WebSphere\Plugins\config\coi\key.sth"/>
Note the highlighted application will be whichever app directory you're working with.
An IIS restart may be required.