CA Service Management

 View Only
Expand all | Collapse all

Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

  • 1.  Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Jul 16, 2019 08:29 AM
    Hi,
    after migration Jaspersoft from 6.3 to 7.1.1 we are trying to integrate Jaspersoft with Service Management.
    While installer is collecting parameters for installation of the integration hangs with error: connection to server not possible (see attached file).
    Rest-Url works from browser (also see attached file).

    Protocol (install.log) shows:
    2019/07/16 14.05.47.633 INFO  [AWT-EventQueue-0] [DatabaseManager] ************************************************************************************

    2019/07/16 14.05.47.633 DEBUG [AWT-EventQueue-0] [DatabasePage] DataBase validation Done.

    2019/07/16 14.06.42.477 DEBUG [AWT-EventQueue-0] [JasperServerPage] In CABI validate page.

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.server.name....Text: gll-xxxxxx

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.server.port....Text: 8080

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.server.admin.user....Text: superuser

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.server.organization....Text: casm_insights

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.insights.admin.user....Text: jasperadmin

    2019/07/16 14.06.42.492 DEBUG [AWT-EventQueue-0] [WizardPage] Name: jasper.installed.location....Text: C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\jasperserver-pro

    2019/07/16 14.06.42.492 INFO  [AWT-EventQueue-0] [JasperServerValidator] Inside Jasper Validator.

    2019/07/16 14.06.42.508 INFO  [AWT-EventQueue-0] [JasperServerValidator] Discovered Jasper WebApp Name : jasperserver-pro

    2019/07/16 14.06.42.508 INFO  [AWT-EventQueue-0] [JasperServerValidator] Validating Jasper installation directory, looking for WEB-INF\applicationContext.xml,META-INF\jasperserverDS-jdbc.xml and optimized-scripts folder

    2019/07/16 14.06.42.508 INFO  [AWT-EventQueue-0] [JasperServerValidator] Jasper installation directory validation succeeded.

    2019/07/16 14.06.42.508 INFO  [AWT-EventQueue-0] [JasperServerValidator] Validating JasperAdmin password.

    2019/07/16 14.06.42.508 INFO  [AWT-EventQueue-0] [JasperServerValidator] Trying to parse applicationContext.xml in Jasper installation directory

    2019/07/16 14.06.42.602 INFO  [AWT-EventQueue-0] [JasperServerValidator] Password Pattern found in applicationContext.xml : ^.*$

    2019/07/16 14.06.42.602 INFO  [AWT-EventQueue-0] [JasperServerValidator] Successfully Validated JasperAdmin password against password pattern : ^.*$

    2019/07/16 14.06.42.602 INFO  [AWT-EventQueue-0] [JasperServerValidator] Validating Jasper server, trying to connect.

    2019/07/16 14.06.42.602 INFO  [AWT-EventQueue-0] [JasperServerValidator] Jasper server rest URI :HTTP://gll-xxxxx:8080/jasperserver-pro/rest/login

    2019/07/16 14.06.42.773 INFO  [AWT-EventQueue-0] [JasperServerValidator] Response Code from Jasper Server Rest Call :404

    2019/07/16 14.06.42.773 INFO  [AWT-EventQueue-0] [JasperServerValidator] Response Message from Jasper Server Rest Call :Not Found

    2019/07/16 14.06.42.773 ERROR [AWT-EventQueue-0] [JasperServerValidator] Unable to contact server gll-xxxxxx Response code : 404

    2019/07/16 14.06.42.805 DEBUG [AWT-EventQueue-0] [JasperServerPage] CABI validation Done.



    Any idea?


    Many thanks,
    Peter
    #jaspersoft 7.1.1
    #CA Service Management
    #Integrate Jaspersoft with SDM
    ​​​

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------

    Attachment(s)

    txt
    install.txt   3 KB 1 version


  • 2.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1
    Best Answer

    Broadcom Employee
    Posted Jul 16, 2019 08:48 AM
    Peter...........

    In Jasper 7.1.1 Rest API signature has changed.  As a result we have updated the common installer to accommodate this change.  Please try using 17.2 RU1 common installer to run the integration task.

    As a reminder, JasperSoft 7.1.1 is only supported/certified with SDM 17.2 RU1 at this time.

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.
    ------------------------------



  • 3.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Jul 16, 2019 10:05 AM
    Hi Paul,
    great info. 
    We will test it.
    Ciao,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 4.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Jul 16, 2019 11:38 AM
    Hi Paul,
    with SDM 17.2 RU1 installer it worked.

    We had another little problem which was solved by switching off LDAP-login temporarily as described in

    https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=131872


    Many thanks,
    Peter



    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 5.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Sep 30, 2019 10:21 AM
    Hi,
    have a new problem in a vmware-Test- and Demo-Installation.

    I have set up vmware with 2 servers
    - 1st: SM-Server (17.2.01).
    - 2nd server jaspersoft 7.1.1.
    Both Installations are running well as I can say at the moment.

    Now I'm starting integration of Jasper with SDM from RU1-media on the Jasper-Server.
    The new problem is that I'm not able to complete the integration.
    After typing the parameters for transactional reports and clicking next I get an error: Invalid Server Details Specified for CA Service Desk

    From the Reporting-Server I can:
    - http://sm141:9080/CAisd/pdmweb.exe, http://sm141:9002, ... looks good
    - on sm141 (SDM-Server) netstat says 2100 is hearing on the line ;-)
    - on Jasper-Server: http://sm141:2100  returns site-output 5

    While integration in install.log there is:
    2019/09/30 15.55.32.650 ERROR [AWT-EventQueue-0] [SLUMP] Can't logon to slump - check server daemons: java.io.IOException: java.net.ConnectException: Connection refused: connect
    2019/09/30 15.55.32.650 ERROR [AWT-EventQueue-0] [TransactionalReportsPage] Failed to login to slump



    Any idea what to do that connection from integration will work?

    Thanks and Regards,
    Peter


    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 6.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Sep 30, 2019 10:41 AM
    Hi,
    'solved' ...
    After restarting both machines (not only the services - complete machines) 
    it's now running.
    hm ...

    Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 7.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Broadcom Employee
    Posted Oct 01, 2019 02:47 AM
    Thanks for the resolution update, Peter.

    At least we have an indexed thread now to refer to, even if we don't know what was cached where that caused the hiccup.

    Kyle_R.


  • 8.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Aug 26, 2020 10:42 AM
    Hi all,
    new situation and question.
    When we want to integrate Jasper with SDM, where do we have to start the integration-process?
    - On Jasper-Server or on SDM-Server?
    We are trying it on Jasper-Server and get the same problem as described above (SM17.3 with Jasper 7.1.1).

    Errors in install-Log:
    FATAL [AWT-EventQueue-0] [NXenv] FATAL NXenv: can't find NX.env in C:/Program Files/CA/Service Desk
    ERROR [AWT-EventQueue-0] [TCP_port] java.net.ConnectException: Connection refused: connect
    ERROR [AWT-EventQueue-0] [SLUMP] Can't logon to slump - check server daemons: java.io.IOException: java.net.ConnectException: Connection refused: connect
    ERROR [AWT-EventQueue-0] [TransactionalReportsPage] Failed to login to slump

    Why does it search NX.env in C:/Program Files/CA/Service Desk on lokal machine? That's not the install-Path for it on SDM-Primary-Server.
    Parameters for slump-login are correct in parameters (checked in dialog):

    Thanks and regards,
    Peter


    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 9.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Broadcom Employee
    Posted Aug 27, 2020 02:05 AM
    Hi Peter

    1.  You can  ignore this error
    FATAL [AWT-EventQueue-0] [NXenv] FATAL NXenv: can't find NX.env in C:/Program Files/CA/Service Desk 
    This is a false alarm.


    2.  ERROR [AWT-EventQueue-0] [TransactionalReportsPage] Failed to login to slump
    Its looks like a connectivity issue, for this error please verify below.

    a) Ping the service desk manager hostname machine from 
        from the machine where common installer is opened
    b) Using telnet, from common installer opened machine, check if sdm port 2100 is accessible
    b) Check if the SDM machine's port 2100 is accessible/not blocked by firewall







  • 10.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Aug 27, 2020 03:38 AM
    Hi Vallinayagam,
    - ping is ok
    - telnet says:5 and seems to be ok
    - there seems not to be any firewall blocking 2100

    Thanks,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 11.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Dec 16, 2021 02:23 PM
    Did you solve?
    I have the same flaw in this step.


  • 12.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Dec 17, 2021 01:44 AM
    Hi Marcos,
    excuse me please that I cannot remember how at least we resolved the problem under this version-conditions.
    It's more than a year ago ;-)

    All my customers are now running 17.3 RU06 and higher with Jasper 7.2

    Best experience I had with 17.3.0.10 in combination with Jasper 7.9.

    Regards,
    Peter


  • 13.  RE: Jaspersoft 7.1.1 Integration with Service Management 17.2.0.1

    Posted Dec 17, 2021 02:44 PM
    No problem my friend. I have this error on Jasper 7.9 with SDM 17.3.0.10
    I created a case in support. Thanks.