Automic Workload Automation

  • Private Community
Back to discussions
Expand all | Collapse all

Proper Way to Stop JWP

  • 1.  Proper Way to Stop JWP

    Posted Jun 29, 2017 08:15 AM
    Hi.  Just wondering if there's a different / special way to bring down the JWP and/or if there's any reason why sometimes it will not come down.

    We use the service manager ucybsmcl program to start / stop our various CP, WP, JWP processes.  75% of the time this works fine / as expected.  However, on occasion as we are trying to bring down the system, the CP's & WP's come down OK, but the JWP's do not.

    I don't see any errors in the service manager log - it DOES issue the command - just nothing happens.

    This is the command we use:

    ucybsmcl -c STOP_PROCESS -h Server:Port -n SystemName -s 'AE JWP2' -m C 

    I know I can use the S or A commands, but figured that is something I should do as a secondary measure.

    Has anyone else seen this type of issue?


  • 2.  Proper Way to Stop JWP

    Posted Jun 29, 2017 08:55 AM
    How is the JWP defined in the SMD file?


  • 3.  Proper Way to Stop JWP

    Posted Jun 29, 2017 09:21 AM

    Michael A. Lowry



    DEFINE AE JWP1;/u02/automic/java/jdk1.8.0_92/bin/java -Xmx512M -jar /u02/automic/automationengine/bin/ucsrvjp.jar -svc%port% -I/u02/automic/automationengine/bin/ucsrv.ini;/u02/automic/ae_servicemanager/bin/../../automationengine/bin



  • 4.  Proper Way to Stop JWP

    Posted Jun 29, 2017 11:57 AM
    Please note that JWP need an additional [JDBC] connexion in addition to the [ODBC] main java connector in the ucsrv.ini file 


  • 5.  Proper Way to Stop JWP

    Posted Jun 29, 2017 12:25 PM
    Karim_Azzouzi_8427  - JDBC section / connection is an option, not a requirement.  We are using the same connection string that the CP's and WP's use within the ucsrv.ini file.

    SQLDRIVERCONNECT=ODBCVAR=NNJNIORO,DSN=xxxx;UID=xxxxx;PWD=xxxxx;SP=NLS_LANGUAGE=AMERICAN,NLS_TERRITORY=AMERICA,CODESET=WE8MSWIN1252


  • 6.  Proper Way to Stop JWP

    Posted Jun 29, 2017 01:43 PM
    Laura Albrecht said:
    JDBC section / connection is an option, not a requirement.  We are using the same connection string that the CP's and WP's use within the ucsrv.ini file.
    Really? The documentation seems to suggest that it’s required. Could someone from Automic comment on this?


  • 7.  Proper Way to Stop JWP

    Posted Jun 29, 2017 01:51 PM
    I can't comment on what the "proper" way to do it is, but the way I read the documentation for the JWP installation it says "there are 2 options".  So we choose the option where we use the existing OCI string.

    It works - that's all I can say.   :)

    I'm not sure the benefit of using the [JDBC] section - the HELP doesn't list the pros/cons of each option.



  • 8.  Proper Way to Stop JWP

    Posted Jun 30, 2017 04:30 AM
    LauraAlbrecht608310 I agree that according to documentation it's optionnal , but using a separate JDBC driver for JWP is suitable.

    ODBC : is a standard Microsoft Windows interface that enables communication between database management systems and applications typically written in C or C++;

    JDBC : is a p    latform independence, allowing you to work with any operating system (including Mac and Linux), driver version

    ODBC vs JDBC :
    ODBC is an open interface which can be used by any application to communicate with any database system, in our case AE to DB while JDBC is an interface that can be used by Java applications to access databases, in this case JWP is the Java application.


  • 9.  Proper Way to Stop JWP

    Posted Jun 30, 2017 04:37 AM
    Laura Albrecht wrote:
    DEFINE AE JWP1;/u02/automic/java/jdk1.8.0_92/bin/java -Xmx512M -jar /u02/automic/automationengine/bin/ucsrvjp.jar -svc%port% -I/u02/automic/automationengine/bin/ucsrv.ini;/u02/automic/ae_servicemanager/bin/../../automationengine/bin
    That looks fine to me. I do not see anything unusual. I have also noticed that I am unable to stop JWPs via the Service Manager, but I thought it had to do with the fact that I was using a startup script between the SMgr and the JWP. When I try to stop the JWP from the SMgr, the process associated with the startup script terminates OK, but it leaves the child java process running (and orphaned). When I find the time, I will try starting it directly from the SMgr and see I observe the same behavior.


  • 10.  Proper Way to Stop JWP

    Posted Jun 30, 2017 07:04 AM
    Really? The documentation seems to suggest that it’s required. Could someone from Automic comment on this?
    Hi Michael,

    The JDBC section is optional if the ODBC section is configured to use the SQL Server native client or the Oracle client.

    Example:
    [ODBC]
    SQLDRIVERCONNECT=ODBCVAR=SNNNNNRN,Driver={SQL Server Native Client 11.0};Server=tcp:localhost,1433;Database=AEV12;Uid=automic;Pwd=automic;

    Best regards,
    Antoine



  • 11.  Proper Way to Stop JWP

    Posted Jun 30, 2017 07:35 AM

    Antoine Sauteron wrote:

    The JDBC section is optional if the ODBC section is configured to use the SQL Server native client or the Oracle client.

    That is good to know. If we can use ODBC also for the JWP, then we can rely on LDAP-based connection strings. (They are not currently supported for JDBC — See JWP should support LDAP-based Oracle JDBC strings in ucsrv.ini.)