Symantec IGA

  • Private Community
Back to discussions
Expand all | Collapse all

404 Error When Viewing Report, HowToFix IT?

  • 1.  404 Error When Viewing Report, HowToFix IT?

    Posted Dec 27, 2011 06:33 PM

    Symptom:
    When view a report from CMC, Infoview or from Identity Manager you consistently receive the HTTP 404 error message in the browser.
    You may also find this error message in your logs:
    [color=#f70101]" 08-09-11 20:43:18:084 - {ERROR} localhost¨./CustomParams¨ Thread "Thread-1¨; Error configuring application listener of class com.ca.biek.customparams.shared.ActionXMLManager java.lang.ClassNotFoundException: com.ca.biek.customparams.shared.ActionXMLManager "[color]

    You may use the below procedure to redeploy the customparams application:

    (you can try with your installation media first, but if that does not work you may also want to consider using the WAR I attached to this post)



    Here's the Tech Note on how to address deployment of CustomParams:

    Project:
    CA Business Intelligence

    Problem:
    Failed deploying CustomParams.

    Resolution:


    The following are the steps to be followed


    [list=1]
    [*]Check the wdeploy.log file and find out if any errors are logged.
    [list=2]
    [*] LOC: $INSTALL_DIR/deployment/workdir
    [list]
    [*] Check the ca_install.log and find out if any errors are logged.
    [list=2]
    [*] LOC:$INSTALLDIR
    [list]
    [*] To deploy CustomParams
    [list=2]
    [*] If CustomParams.war file is present in "$INSTALL_DIR/
    CommonReporting3/bobje/enterprise120/java/applications/" go to step (d)
    [*] If not Present then make a war file of the contents of
    CustomParams folder located in "$SOURCE_DIR/ Disk1/cabi/caf/war"
    [*] Copy this war file to $INSTALL_DIR$/CommonReporting3/bobje/enterprise120/java/applications
    [*] Change to $INSTALL_DIR/CommonReporting3/deployment and invoke the following commands
    [list=3]
    [*] ./wdeploy.sh <appname> -DAPP=CustomParams undeploy
    [*] /wdeploy.sh <appname> -DAPP=CustomParams deploy
    [*] E.g. ./wdeploy.sh tomcat55 -DAPP=CustomParams undeploy

    [list]
    [list]
    [list]


    Please Note:
    $INSTALL_DIR refers to the installation directory of CA Business Intelligence .the default value is "C:\Program Files\CA\SC\CommonReporting3"

    $SOURCE _DIR refers to the location from where the CABI installer has been invoked.

    The above steps assume you're running on Unix, but if on Windows, simply copy the CustomParams.war to \Program Files (x86)\CA\SC\CommonReporting3\BusinessObjects Enterprise 12.0\java\applications and the run
    "wdeploy.bat tomcat55 -DAPP=CustomParams undeploy"
    then deploy on \Program Files (x86)\CA\SC\CommonReporting3\deployment.
    Tomcat and SIA have to be turned off for this to work.

    You should now able to view reports from InfoView, CMC, and also from IM.

    Please post with any questions or concerns.
    Thank you.
    Regards,

    Chris Thomas
    CA Technologies
    Principal Support Engineer
    Identity Manager Reporting Expert
    Tel: +1-631-342-4360
    Chris.Thomas@ca.com



  • 2.  RE: 404 Error When Viewing Report, HowToFix IT?

     
    Posted Dec 27, 2011 07:26 PM
    Thanks for all the great info Chris!

    Check it out folks and everyone have a very Happy New Year!

    Chris


  • 3.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jan 28, 2013 04:19 PM
    Hi,

    I'm having the same problem, I performed the procedure, but I am getting the following error. Can you help me?

    My BO version is: Business Intelligence r3.3 for Linux
    My Server: Red Hat Enterprise Linux Server release 6.3 (Santiago) and Tomcat 6.0.024

    [webuser@ppmhx06c deployment]$ ./wdeploy.sh tomcat6 -DAPP=CustomParams undeploy
    Buildfile: wcommon.xml

    undeploy_config:

    preconfig:

    undeploy:

    BUILD FAILED
    /clarity/CommonReporting3/deployment/wcommon.xml:1137: Error: APP property not set.
    Please set APP to the application you intend to undeploy

    Total time: 0 seconds
    [webuser@ppmhx06c deployment]$ ./wdeploy.sh tomcat6 -DAPP=CustomParams deploy
    Buildfile: wcommon.xml

    config:
    Loading config.tomcat6

    BUILD FAILED
    /clarity/CommonReporting3/deployment/wcommon.xml:66: Error: APP property not set.
    Please set APP to the application you intend to use

    Total time: 0 seconds


  • 4.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jan 31, 2013 03:46 PM
    Will need to test this on Tomcat6... Procedure was written for 55.


  • 5.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jun 03, 2013 05:16 PM
      |   view attached

    Chris_Thomas wrote:

    Will need to test this on Tomcat6... Procedure was written for 55.
    Hi Chris,

    The structure of DVD correct is this:

    DISK1\CABI\CAF\WAR\CUSTOMPA

    The name of folder is CUSTOMPA or should CustomParams ?


  • 6.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jun 04, 2013 11:42 AM
      |   view attached
    I verified that my installation does not have the properties files CustomParams. How can I get? Or how should create?

    Because this cause the error:

    [webuser@ppmdx02 deployment]$ ./wdeploy.sh tomcat6 -DAPP=CustomParams deploy
    Buildfile: wcommon.xml

    config:
    Loading config.tomcat6

    BUILD FAILED
    /clarity/CommonReporting3/deployment/wcommon.xml:66: Error: APP property not set.
    Please set APP to the application you intend to use


  • 7.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jun 11, 2013 05:30 PM
    Hi,

    Shared the solution on Tomcat 6 and linux Red Hat 6.

    Problem:
    First, there is a bug in DVD Business Intelligence r3.3 for Linux. The web.xml located in $SOURCE_DIR/Disk1/cabi/caf/war/CustomParams/WEB-INF in tag <param-value> c:/temp/customparameters</param-value> is wrong, because used "c:/temp/". This cause error in installation.

    The following the solution:

    1) Copy the $SOURCE_DIR/Disk1/cabi/caf/properties/CustomParams.properties to $INSTALLDIR/CommonReporting3/deployment/apps
    2) Change the tag <param-value> </param-value> in web.xml, example:

    <context-param>


    <param-name>xmlFilePath</param-name>

    <param-value>$INSTALLDIR/CommonReporting3/cacaf</param-value>
    </context-param>

    3) Make a war file of the contents of CustomParams folder located in "$SOURCE_DIR/ Disk1/cabi/caf/war" and change the web.xml.
    4) Copy this CustomParams.war to to $INSTALL_DIR$/CommonReporting3/bobje/enterprise120/java/applications
    5) Change to $INSTALL_DIR/CommonReporting3/deployment and invoke the following commands
    6) /wdeploy.sh tomcat6 -DAPP=CustomParams deploy

    Hope this helps.


  • 8.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jun 17, 2013 10:23 AM
    Thanks for posting what you did to workaround this on Tomcat 6. Regarding your claim on a potential defect with installer, I'm confused did you install with CABI 3.2 or CABI 3.3 ( I believe you're using BOE 3.1 SP5? ) and did you use the default OOTB embedded version of Tomcat that comes shipped within the 3.3 ISO (Tomcat 6) or did you opt to use your own personally downloaded and deployed version of Tomcat? When you installed what options exactly did you select when proceeding through the installer? I ask because I'd like to decipher the exact steps to reproduce the problem, because if there is something that can be fixed or improved, I'd like to work as an advocate on your behalf for change, but the problem will first need to be validated on CA lab.


  • 9.  RE: 404 Error When Viewing Report, HowToFix IT?

    Posted Jul 26, 2013 03:01 PM
    Just had this problem again and fixed it with a customer.

    replaced the working WAR to:
    [color=#fc0e0e]/opt/CA/SharedComponents/CommonReporting3/bobje/enterprise120/java/applications[color]
    Deleted the deployed custom params directory from:
    [color=#fc0e0e]/opt/CA/SharedComponents/CommonReporting3/bobje/tomcat/webapps[color]

    Opened the terminal and went to:
    [color=#fc0e0e]/opt/CA/SharedComponents/CommonReporting3/deployment[color]
    and ran:
    [color=#0e16fc]/wdeploy.sh tomcat6 -DAPP=CustomParams deploy[color]

    then changed directory to (as cabi user):
    [color=#0e16fc]/opt/CA/SharedComponents/CommonReporting3/bobje[color]
    and ran:
    [color=#0e16fc]./tomcatshutdown.sh[color]
    then
    [color=#0e16fc]./thomacatstartup.sh[color]


  • 10.  Re: 404 Error When Viewing Report, HowToFix IT?

    Posted Mar 25, 2015 05:14 PM

    Just did the same on tomcat7

     

    Stopped tomcat, inspected tomcatstartup.sh.

     

    Went to /opt/CA/SharedComponents/CommonReporting3/bobje/tomcat7/webapps/ deleted all files and folders.

     

    then went to /opt/CA/SharedComponents/CommonReporting3/deployment

    ./wdeploy.sh tomcat7 deployall

     

    Then started up tomcat.