28 Aug 2012
August 28, 2012

WebSphere Blog Content Requests

August 28, 2012 Blog, Consulting 4 Comments

This post is place to submit suggestions for blog articles. I use suggestions posted by you to decide what are the relevant areas that people need help and support for within the Middle-Ware space.

 

If you need to ask question, then please post to the JEE and Middleware FAQ

 

Note: I am not monitoring this blog full-time, but I do answer as many as I can, when I can. Please appreciate I have limited time to help everyone, but I do try to help as many people as I possible can.

 

Regards

 

Steve Robinson – Middleware Consultant

 

4 Responses to WebSphere Blog Content Requests
  1. Maybe an example of JMS and MDB and servlet client to put / get a message in / from a JMS queue using RAD 8.5 / WAS 8.5 using both SIB and MQ

  2. Hi guys, i´m trying to create a profile in the websphere application server express v8 on ibm i (iseries), to do that i put this line in the qshell console:

    manageprofiles -create -profileName default -serverName server1 -defaultPorts -isDefault

    after 30-40 minutes, it fails and the log file show this:

    record>
    2012-08-29T08:23:07
    1346287987860
    3047
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    INFO
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    messageLogged
    0
    Is wsadmin listener available? false

    2012-08-29T08:23:07
    1346287987912
    3048
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    INFO
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    messageLogged
    0
    Returning with returnCode=-1

    2012-08-29T08:23:07
    1346287987913
    3049
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    INFO
    com.ibm.ws.install.configmanager.actionengine.ant.utils.ANTLogToCmtLogAdapter
    messageLogged
    0
    Failure detected in fatal config action.

    check the wsadmin variable in the wasprofile.properties, i put the same line and i get the same message :S, please if you guys have any ideas of this, i will be gratefully for all the eternity to all of you !!, many thanks and sorry for the inconvenience!

    • This post is for Suggestions for content to be create on this site, you shoukld really post to the JEE and Websphere FAQ as per my comment below.

      As far as what is your problem, I do ot know. Are you ure you have the correct manageprofile sytx for iseries. check the IBM information centre for example:

      http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.iseries.doc/info/iseriesexp/ae/tpro_setup.html

      Managing profiles using commands:

      Use commands to create a profile, start the server of the profile, display ports used by your server, and open the administrative console.

      Before you begin:

      This task assumes a basic familiarity with the command, other application server commands, and system commands.

      Before you can create and use a profile, you must install the product.

      About this task:

      Perform the following steps to create a profile, start the server of the profile, display ports used by your server, and open the administrative console for your server.

      This example deals with the profile environment of a standalone application server.

      Procedure :

      1.Create the server profile from the original installation:
      ◦app_server_root/bin/manageprofiles
      Assume that you create the profile by using the defaults. The following script is an example for creating an application server profile:
      ◦app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/default

      2.Change directories to the profile_root/bin directory of the new server profile.

      3.Start the server.
      Issue the startServer command.

      The server name is the same name as the profile, which, in this case, is profile_name.

      startServer -profileName profile_nameNote: The -profileName argument is not necessary if you have already changed to the profile_root/bin directory of the target profile.

      4.Display the ports.
      These are the ports assigned during profile creation.

      Use the dspwasinst QShell script to display the ports for your new profile:
      app_server_root/bin/dspwasinst -profileName profileNameThe WC_adminhost and WC_adminhost_secure ports listed are the nonsecure and secure administrative console ports, respectively.

      5.Open the administrative console.
      The server1 administrative console is defined on the WC_adminhost setting for the non-secure administrative console port or the WC_adminhost_secure setting for the secure administrative console port.

      If the value of the WC_adminhost port for your server is 20003, for example, specify the following web address in your browser:
      http://host_name_or_IP_address:20003/ibm/console/If the value of the WC_adminhost_secure port for your server is 9061, for example, specify the following web address in your browser:
      https://host_name_or_IP_address:9061/ibm/console/

  3. All, I updated the website with a new template (I hope you like it). Unfortunately, I had to re-populate all previous page comments against a new post -> [http://blog.webspheretools.com/2012/08/28/websphere-jee-faq/]. You can find previous discussion threads there. If you have any FAQ type questions, then please post against the JEE – WebSphere and FAQ post (link above).

    Alternatively, If you want to see specific content on this blog, then post your suggestions here.


[top]

Leave a Reply