Topic
3 replies Latest Post - ‏2013-08-07T14:37:29Z by jhanders
MandarChatufale
MandarChatufale
18 Posts
ACCEPTED ANSWER

Pinned topic xscmd for Standalone wxs server

‏2013-08-07T11:10:56Z |

Hi,

I have a standalone websphere extreme scale server. I start the catlog server and container server by running below bat files from ObjectGrid\gettingstarted folder

  • startcat.bat
  • startcontainer.bat (with localhost as command line arg)

 By running above bat files, it starts the catalog and container server and then i am able to connect to these server through the java program.

Now to Monitor the cache, i execute xscmd.bat file which is present in ObjectGrid\bin folder. executing this bat file w/o any argument should connect to the server with dafault configuration . Refer following link 

http://pic.dhe.ibm.com/infocenter/wxsinfo/v8r6/index.jsp?topic=%2Fcom.ibm.websphere.extremescale.doc%2Ftxsxscmd.html

But even after executing the xscmd file,it does not connect to the catalog server. Passing the hostname and port as jvm arguments also does not help.

ObjectGrid\bin folder contains startOgServer.bat file. What is use of this bat file?

Please let me know if i am missing any configuration?

Thanks

 

 

 

 

  • jhanders
    jhanders
    257 Posts
    ACCEPTED ANSWER

    Re: xscmd for Standalone wxs server

    ‏2013-08-07T12:54:38Z  in response to MandarChatufale

    startcat and startcontainer scripts are sample scripts that give you a sample grid to run a sample client with.  You will see in the end they are just calling the startXsServer from the bin directory like you would for your own grid in production.  It is a way to get you started in using the product quickly.  Specifically startOgServer script is the previous start server script that we had before 8.6 that always starts up by default with the ORB like it always has in previous releases so as to maintain compatibility.  The startXsServer script was added in 8.6 to start with XIO by default.  You can use both to start either transport, but the default without provided a transport argument is as I stated.

    Regarding xscmd you will need to provide at least the command that you want to run.  So for instance xscmd.bat -c showMapSizes should work for you as long as you didn't modify any of the settings for the host and port for the getting started sample.  I assume for the command argument for host and port you used -cep localhost:2809 as part of your xscmd.bat commandline.  If that is failing to work we would need to see the exception to know what failure you are seeing with trying to connect.

    I hope that helps give you the direction you need.

    Jared Anderson

     

    • MandarChatufale
      MandarChatufale
      18 Posts
      ACCEPTED ANSWER

      Re: xscmd for Standalone wxs server

      ‏2013-08-07T14:29:07Z  in response to jhanders

      Hi Jared,

      Thank you for the reply and detailed explanation.

      I think i missed to mention that i have trail version of standalone websphere extreme scale client. 

      I tried executing xscmd.bat alond with arguments

      xscmd.bat -cep localhost:2809

      Currently nothing is there in my cache. I,ve just started the catalog and container server.

      When i execute above command i get following message

      Starting at: 2013-08-07 16:14:16.743
       
      Usage: xscmd -c <cmdName> | -h <cmdName> | -lc [<cmdGroupName>] | -lcg
                   [-tt <type>] [-prot <protocol>] [-trf <filePath>] [-ks
                   <filePath>] [-ksp <password>] [-user <username>] [-al <alias>]
                   [-cgp <property>] [-kst <type>] [-cep <endpoints>] [-ssp
                   <profileName>] [-tsp <password>] [-arc <integer>] [-trs
                   <traceSpec>] [-tst <type>] [-to <serverTimeout>] [-cxpv
                   <provider>] [-ro <filename>] [-sp <profileName>] [-pwd
                   <password>] [-ca <support>] [-cgc <className>] [-ts <filePath>]
       
      Options:
        -al,--alias <alias>                  Alias name in the keystore.
       
        -arc,--authRetryCount <integer>      The retry count for authentication if
                                             the credential is expired. If the
                                             value is set to 0, then authentication
                                             retries do not occur.
       
        -c,--command <cmdName>               Specifies the name of the command to
                                             execute
       
        -ca,--credAuth <support>             Set the client credential
                                             authentication support [Never,
                                             Supported, Required].
       
        -cep,--catalogEndPoints <endpoints>  Specifies one or more catalog service
                                             endpoints in the format
                                             <host>[:<listenerPort>][,<host>[:
                                             <listenerPort>]]. Default endpoint:
                                             localhost:2809
       
        -cgc,--credGenClass <className>      Specifies the name of the class that
                                             implements the CredentialGenerator
                                             interface. This class is used to get
                                             credentials for clients.
       
        -cgp,--credGenProps <property>       Specifies the properties for the
                                             CredentialGenerator implementation
                                             class. The properties are set to the
                                             object with the setProperties(String)
                                             method.
       
        -cxpv,--contextProvider <provider>   Context provider.  Examples: IBMJSSE2,
                                             IBMJSSE, IBMJSSEFIPS.
       
        -h,--help <cmdName>                  Invokes general command-line help
       
        -ks,--keyStore <filePath>            Absolute path to keystore. Example:
                                             /etc/test/security/server.public
       
        -ksp,--keyStorePassword <password>   Specifies the password to the keystore.
       
        -kst,--keyStoreType <type>           Keystore type. Example: JKS, JCEK,
                                             PKCS12.
       
        -lc,--listCommands <cmdGroupName>    List all commands for a command group
       
        -lcg,--listCommandGroups             List all command groups
       
        -prot,--protocol <protocol>          Protocol.  Examples: SSL, SSLv2,
                                             SSLv3, TLS, TLSv1.
       
        -pwd,--password <password>           eXtreme Scale password security
                                             credential
       
        -ro,--redirectOutput <filename>      Specifies the file name of the file to
                                             which xscmd command output is
                                             redirected (applies to commands run on
                                             DataPower XC10 appliance only)
       
        -sp,--secProfile <profileName>       Specifies a profile name.
       
        -ssp,--saveSecProfile <profileName>  Save security parameter values in
                                             security profile.
       
        -to,--timeout <serverTimeout>        Server connection timeout in seconds
       
        -trf,--traceFile <filePath>          Specifies the absolute path to the
                                             generated trace file for xscmd command
                                             output
       
        -trs,--traceSpec <traceSpec>         Specifies the trace specification for
                                             xscmd command output
       
        -ts,--trustStore <filePath>          Absolute path to truststore. Example:
                                             /etc/test/security/server.public
       
        -tsp,--trustStorePassword <password> Truststore password
       
        -tst,--trustStoreType <type>         Truststore type. Examples: JKS, JCEK,
                                             PKCS12.
       
        -tt,--transportType <type>           Transport layer security configuration
                                             type.  Examples: TCP/IP,
                                             SSL-Supported, SSL-Required.
       
        -user,--username <username>          eXtreme Scale user name security
                                             credential
       
      Ending at: 2013-08-07 16:14:17.351

      Also i execute one more command by passing the grid name and mapset , i get below message

      extremescaletrial860\ObjectGrid\bin>xscmd.bat -c showMapSizes -g Grid -ms mapset
       -m Map1 -cep localhost:2809
      Starting at: 2013-08-07 16:32:37.280
       
      CWXSI0068I: Executing command: showMapSizes
       
       
      CWXSI0022E: The specified data grid name Grid and map set name mapset were not f
      ound.
       
      Ending at: 2013-08-07 16:32:40.121

       

      Please let me know if i am missing any configurations

       

       

       

       

      • jhanders
        jhanders
        257 Posts
        ACCEPTED ANSWER

        Re: xscmd for Standalone wxs server

        ‏2013-08-07T14:37:29Z  in response to MandarChatufale

        The first output is the help text.  You need to provide -c or some other required argument which is why you get that.

        Your mapset name wrong in the second one.  It is mapSet instead of mapset for the configuration for the getting started sample.

        If you don't provide the grid mapset and map name it will automatically do all of them.  So just do -c showMapSizes -cep localhost:2809 without the -g, -ms, and -m options and you should get some good output.