Nolio KB: Installing an agent on a Weblogic server to run Weblogic actions

Document created by MaryGreening on Jul 8, 2014
Version 1Show Document
  • View in full screen mode

Nolio Official KB: What do I need to do when Installing an agent on a Weblogic server in order to run Weblogic Actions?

To properly use the Nolio Action Pack for WebLogic Application Server (WLS), the following configurations must be performed on each Nolio Agent machine that will execute WLS actions.
Follow the instructions for the specific WebLogic version.
For all versions, if the WebLogic server is using SSL configuration, you must apply SSL support by copying wlcipher.jar from /server/lib to the /lib folder in order for Nolio actions to work.
Note: The folders described in the following procedure are those where the files are typically located.
For WebLogic versions 9.2 and 9.3:
    1.    If WebLogic server is using SSL:
        Copy /server/lib/wlcipher.jar to /lib.
    2.    Copy /server/lib/Weblogic.jar to /lib.
    3.    Change directory to /conf.
    4.    If file custom.wrapper.conf does not exist:
        a.    Create a new file.
        b.    Add the following text:
        “wrapper.java.additional.20=-Dsun.lang.ClassLoader.allowArraySyntax=true”
        c.    Save.
    5.    Change directory to /server/lib.
    6.    Copy Weblogic.jar to /lib.
    7.    Copy < WLS ROOT >/modules/com.bea.core.descriptor.wl_X.X.X.X.jar to /lib.
    8.    Restart the Nolio Agent.
For WebLogic versions 10.0 up to 10.2.x:
    1.    If WebLogic server is using SSL:
        Copy /server/lib/wlcipher.jar to /lib.
    2.    Change directory to /conf.
    3.    If file custom.wrapper.conf does not exist:
        a.    Create a new file named custom.wrapper.conf.
        b.    Add the following text.
        “wrapper.java.additional.20=-Dsun.lang.ClassLoader.allowArraySyntax=true”
        c.    Save.
    4.    Change directory to /server/lib.
    5.    Run the following command:
        "/jre/bin/java –jar ./modules/com.bea.core.jarbuilder_X.X.X.X.jar"
        where X.X.X.X is the version number of the jarbuilder module in the WLS_HOME/server/lib directory.
        For example: /modules/com.bea.core.jarbuilder_1.0.2.0.jar
        This should create the required wlfullclient.jar in the WLS_HOME/server/lib directory.
    6.    Copy the created wlfullclient.jar to /lib.
    7.    Copy file /modules/com.bea.core.descriptor.wl_X.X.X.X.jar to /lib.
    8.    Restart the Nolio Agent.
For WebLogic versions 10.3 up to 10.35:
    1.    If WebLogic server is using SSL:
        Copy /server/lib/wlcipher.jar to /lib.
    2.    For 10.3.0 only:
        Copy file /modules/com.bea.core.descriptor.wl_X.X.X.X.jar to /lib.
    3.    Change directory to /server/lib.
    4.    Run the following command:
        "/jre/bin/java –jar ./wljarbuilder.jar"
    5.    Copy the created wlfullclient.jar to /lib.
    6.    Restart the Nolio Agent.
Troubleshooting: invalid type code: 31
Below are common issues that can cause invalid type code: 31 error message (Full error message below)
1.      You did not put the weblogic.jar file in the agent (or didn't restart the agent afterwards).
2.      You did not update the wrapper.conf file correctly (or didn't restart the agent afterwards).
3.      You are trying to perform cross platform actions.
Nolio Agent on a windows machine while WLS is on a Linux machine (or vise versa).
Unexpected naming exception occurred during connection. java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is: java.io.StreamCorruptedException: invalid type code: 31

 

This document was generated from the following discussion: Nolio KB: Installing an agent on a Weblogic server to run Weblogic actions

Attachments

    Outcomes