Symantec Identity Management

Expand all | Collapse all

IM 14.3 CP1 and JBOSS EAP 7.2

Jump to Best Answer
  • 1.  IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-04-2019 10:14 AM
    ​Hello,

    We have been running with IM 14.3 and JBOSS EAP 6.4 in UNICAST mode, we have followed all the steps mentioned in the guild to be used for IM 14.3 CP1 upgrade in JBOSS EAP 6.4. When we try to run the Migration Script we get an error that JBIWW EAP 7.2 I snot valid, though the JBOSS WAP 7.2 when brought up has been working fine and we can login with a user to the console as well. This was a ZIP method that we used to install the JBOSS EAP 7.2. We are running these components on Red Hat Linux  6.

    /apps/Downloads/14.3_Layer7_Migration_Tool$./Layer7_migrate_tool.sh -s /apps/JBOSS644/jboss-eap-6.4 -t /apps/JBOSS72/jboss-eap-7.2>

    The Target is not a valid JBoss EAP 7.2, Exiting ...


    Please advise if you have seen this issue before or can advise why this message will appear? We also have tried to point the JBOSS_HOME to OLD and NEW both JBOSS directories and run the script but in both cases there are errors. Please help.

    Thank You.



  • 2.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-04-2019 10:43 AM
    If the migration script runs anything like the IM installer, it will read the version from the jboss module.xml like this:

    Jboss.home.location is pulled from the installer.properties or from the GUI during upgrade that server folder is needed as outlined below: 1. For cases where the version is older than JBoss 6, the installer would look for a file called org/jboss/version.properties inside jboss_home/bin/run.jar. it would collect major and minor integer values. 2. For 6 and above including Wildfly (which is considered 8), the FW installer will do the following: a. <xmltask source="${jboss.home.location}/modules/system/layers/base/org/jboss/as/server/main/module.xml"> <copy attrValue="true" path="/:module/:resources/:resource-root/@path" property="jboss.version.jar"/> </xmltask> Here it reads from the module.xml file and goes to the path module -> resources -> resource-root. For example, Widlfly has this info in the file: <resources> <resource-root path="wildfly-server-8.2.0.Final.jar"/> </resources> The major version is 8 and the minor version is 2. Consult product matrix for valid versions. If you see one server working, then I suggest comparing this module.xml file with the one on the other machine to see what it says. Also, the IM Installer runs the following class "GetJBossVersion": private String jboss7InfoFile = "modules"+File.separator+"system"+File.separator+"layers"+File.separator+"base"+File.separator+"org"+File.separator+"jboss"+File.separator+"as"+File.separator+ "server"+File.separator+"main"+File.separator+"module.xml"; private String jboss6EAPInfoDir = "modules"+File.separator+"system"+File.separator+"layers"+File.separator+"base"+File.separator+"org"+File.separator+"jboss"+File.separator+"as"+File.separator+ "product"+File.separator+"eap";


    You can check the version of jboss in your version 7 server by running this command:
    %JBOSS_HOME%\standalone.sh --version

    If this does not resolve (notice that we are using windows variables, for linux use the $) then the script will fail.

    Bill Patton


    ------------------------------
    And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

    Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at enterprisestudio@hcl.com. https://www.hcltech.com/enterprise-studio
    ------------------------------



  • 3.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-04-2019 10:59 AM

    hello Bill,

    Thanks for your reply. When I ran the command ​I got my version. But now the question comes that JBOSS_HOME parameter can only be set for one version of JBOSS in the system that's wither JBOSS 6.4 or JBOSS 7.2 then in that case how does the migration script decides how to get JBOSS 7.2 parameters if the JBOWS HOME is pointing to JBOWWS 6.4 right now?   Because fi we switch the JBOSS HOME to JBOSS 7.2 then it complains about JBOSS 6.4 version.

    /apps/JBOSS644/jboss-eap-6.4/bin$./standalone.sh --version
    =========================================================================

      JBoss Bootstrap Environment

      JBOSS_HOME: /apps/JBOSS644/jboss-eap-6.4

      JAVA: /usr/java/jdk1.8.0_202-amd64/bin/java

      JAVA_OPTS:  -server -XX:+UseCompressedOops -verbose:gc -Xloggc:"/apps/JBOSS644/jboss-eap-6.4/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading  -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.modules.policy-permissions=true -Xms4096m -Xmx4096m -XX:+UseG1GC -XX:+UseStringDeduplication -XX:+UseCompressedOops -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djava.security.egd=file:/dev/./urandom -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true

    =========================================================================

    10:55:48,588 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
    JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21)




  • 4.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-05-2019 06:19 AM
    hi,

    Prior to migration, if you have a Dev/Test environment, please try the following:

    Method 1:

    1. Stop IM Services
    2. Update JBOSS_HOME variable to point to new JBOSS 7.2 home dir path (for eg: /opt/JBOSS 7.2) home dir
    3. Then check echo $JBOSS_HOME returns the JBOSS 7.2 home
    4. Try the migration..

    If not successfu, try the method 2:

    Method 2:

    1. Stop IM Services
    2. Remove JBOSS_HOME variable competely
    3. Then check echo $JBOSS_HOME returns no value...
    4. Try the migration..

    Regards,
    Badhra Ambati


  • 5.  RE: IM 14.3 CP1 and JBOSS EAP 7.2
    Best Answer

    Posted 12-05-2019 06:44 AM
    Edited by Badhra AMBATI 12-06-2019 05:01 PM
    Forgot to mention, Migration utility is particular about the destination(new jboss home). It verifies /jobss7.2/bin/standalone.sh -version returns this new JBOSS home path or not..if not it throws the error you mentioned..

    Excerpt from migration_tool.sh


    #Check the source and destination App Servers
    sVer=`sh "${src}"/bin/standalone.sh -version 2>&1`
    srcJVer=`echo "$sVer" | grep "JBoss EAP" | cut -d " " -f 3 | cut -c 1-3`
    srcWVer=`echo "$sVer" | grep "WildFly" | cut -d " " -f 2 | cut -c 1-3`

    dVer=`sh "${tar}"/bin/standalone.sh -version 2>&1`
    dstJVer=`echo "$dVer" | grep "JBoss EAP" | cut -d " " -f 3 | cut -c 1-3`
    dstWVer=`echo "$dVer" | grep "WildFly" | cut -d " " -f 3 | cut -c 1-4`
    migration_tool_path=""
    migrate_from=""

    if [ "$srcJVer" = "$SRCJBOSSEAP" ];thenif [ "$srcJVer" = "$SRCJBOSSEAP" ];then    if [ -z "$dstJVer" -o "$dstJVer" != "$DSTJBOSSEAP" ];then        echo "The Target is not a valid JBoss EAP 7.2, Exiting ..." exit 1

    Original Message:
    Sent: 12-05-2019 06:18 AM
    From: Badhra AMBATI
    Subject: IM 14.3 CP1 and JBOSS EAP 7.2

    hi,

    Prior to migration, if you have a Dev/Test environment, please try the following:

    Method 1:

    1. Stop IM Services
    2. Update JBOSS_HOME variable to point to new JBOSS 7.2 home dir path (for eg: /opt/JBOSS 7.2) home dir
    3. Then check echo $JBOSS_HOME returns the JBOSS 7.2 home
    4. Try the migration..

    If not successfu, try the method 2:

    Method 2:

    1. Stop IM Services
    2. Remove JBOSS_HOME variable competely
    3. Then check echo $JBOSS_HOME returns no value...
    4. Try the migration..

    Regards,
    Badhra Ambati
    Original Message:
    Sent: 12-04-2019 10:59 AM
    From: Rakesh Puril
    Subject: IM 14.3 CP1 and JBOSS EAP 7.2

    hello Bill,

    Thanks for your reply. When I ran the command ​I got my version. But now the question comes that JBOSS_HOME parameter can only be set for one version of JBOSS in the system that's wither JBOSS 6.4 or JBOSS 7.2 then in that case how does the migration script decides how to get JBOSS 7.2 parameters if the JBOWS HOME is pointing to JBOWWS 6.4 right now?   Because fi we switch the JBOSS HOME to JBOSS 7.2 then it complains about JBOSS 6.4 version.

    /apps/JBOSS644/jboss-eap-6.4/bin$./standalone.sh --version
    =========================================================================

      JBoss Bootstrap Environment

      JBOSS_HOME: /apps/JBOSS644/jboss-eap-6.4

      JAVA: /usr/java/jdk1.8.0_202-amd64/bin/java

      JAVA_OPTS:  -server -XX:+UseCompressedOops -verbose:gc -Xloggc:"/apps/JBOSS644/jboss-eap-6.4/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading  -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.modules.policy-permissions=true -Xms4096m -Xmx4096m -XX:+UseG1GC -XX:+UseStringDeduplication -XX:+UseCompressedOops -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djava.security.egd=file:/dev/./urandom -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true

    =========================================================================

    10:55:48,588 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
    JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21)


    Original Message:
    Sent: 12-04-2019 10:43 AM
    From: Bill Patton
    Subject: IM 14.3 CP1 and JBOSS EAP 7.2

    If the migration script runs anything like the IM installer, it will read the version from the jboss module.xml like this:

    Jboss.home.location is pulled from the installer.properties or from the GUI during upgrade that server folder is needed as outlined below: 1. For cases where the version is older than JBoss 6, the installer would look for a file called org/jboss/version.properties inside jboss_home/bin/run.jar. it would collect major and minor integer values. 2. For 6 and above including Wildfly (which is considered 8), the FW installer will do the following: a. <xmltask source="${jboss.home.location}/modules/system/layers/base/org/jboss/as/server/main/module.xml"> <copy attrValue="true" path="/:module/:resources/:resource-root/@path" property="jboss.version.jar"/> </xmltask> Here it reads from the module.xml file and goes to the path module -> resources -> resource-root. For example, Widlfly has this info in the file: <resources> <resource-root path="wildfly-server-8.2.0.Final.jar"/> </resources> The major version is 8 and the minor version is 2. Consult product matrix for valid versions. If you see one server working, then I suggest comparing this module.xml file with the one on the other machine to see what it says. Also, the IM Installer runs the following class "GetJBossVersion": private String jboss7InfoFile = "modules"+File.separator+"system"+File.separator+"layers"+File.separator+"base"+File.separator+"org"+File.separator+"jboss"+File.separator+"as"+File.separator+ "server"+File.separator+"main"+File.separator+"module.xml"; private String jboss6EAPInfoDir = "modules"+File.separator+"system"+File.separator+"layers"+File.separator+"base"+File.separator+"org"+File.separator+"jboss"+File.separator+"as"+File.separator+ "product"+File.separator+"eap";


    You can check the version of jboss in your version 7 server by running this command:
    %JBOSS_HOME%\standalone.sh --version

    If this does not resolve (notice that we are using windows variables, for linux use the $) then the script will fail.

    Bill Patton


    ------------------------------
    And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

    Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at enterprisestudio@hcl.com. https://www.hcltech.com/enterprise-studio

    Original Message:
    Sent: 12-04-2019 10:13 AM
    From: Rakesh Puril
    Subject: IM 14.3 CP1 and JBOSS EAP 7.2

    ​Hello,

    We have been running with IM 14.3 and JBOSS EAP 6.4 in UNICAST mode, we have followed all the steps mentioned in the guild to be used for IM 14.3 CP1 upgrade in JBOSS EAP 6.4. When we try to run the Migration Script we get an error that JBIWW EAP 7.2 I snot valid, though the JBOSS WAP 7.2 when brought up has been working fine and we can login with a user to the console as well. This was a ZIP method that we used to install the JBOSS EAP 7.2. We are running these components on Red Hat Linux  6.

    /apps/Downloads/14.3_Layer7_Migration_Tool$./Layer7_migrate_tool.sh -s /apps/JBOSS644/jboss-eap-6.4 -t /apps/JBOSS72/jboss-eap-7.2>

    The Target is not a valid JBoss EAP 7.2, Exiting ...


    Please advise if you have seen this issue before or can advise why this message will appear? We also have tried to point the JBOSS_HOME to OLD and NEW both JBOSS directories and run the script but in both cases there are errors. Please help.

    Thank You.



  • 6.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-06-2019 07:41 AM
    ​Hello Badhra,

    In fact the unset of the JBOSS_HOME has made the script run fine this time, thanks for the suggestions and for your help. We will move further with it and update if any issues are faced. Thank you so much again.

    Rakesh


  • 7.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-05-2019 10:00 AM
    ​hello Bill,

    Yes we got the point how we can get the version and how script can but the question on the table is when there are two versions of JBOSS present on the server for the Migration Script to take a config from JBOSS 6.4 to JBOSS 7.2 on the same system how will it decide because JBOSS HOME can only be set once either to 6.4 or to 7.2 in the ".profile" of the user running the CA IM R14.3 CP1.

    Please advise.
    Thanks
    Rakesh


  • 8.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-05-2019 10:15 AM
    For the migration, JBOSS_HOME env variable should point to the new JBOSSEAP 7.2 home directory.


    Prior to migration stop IM services
    Update JBOSS_HOME Env varaiable to the new jboss7.2 home dir (what this means is at the time of running migration jboss_home only points to the new jboss7.2.)
    then run the migration



  • 9.  RE: IM 14.3 CP1 and JBOSS EAP 7.2

    Posted 12-06-2019 07:14 AM

    Hello Badhra,

    Thanks for replying back. When I switch the JBOSS HOME to go to 7.2 in profile the migration script then starts complaining about the JBOSS 6.4 older version that "source is not valid" please see below:

    /apps/Downloads/14.3_Layer7_Migration_Tool$./Layer7_migrate_tool.sh -s "/apps/JBOSS644/jboss-eap-6.4/" -t "/apps/JBOSS72/jboss-eap-7.2"
    The Source is not a valid JBoss EAP 6.4 or WildFly 8.2, Exiting ...