Does NODE1_SERVERS_ON_NODE get created on its own?
I am using RAF 3.0.0.2 to manage WebSphere application server installations and configurations.
After creating a new cell using environment generation wizard, I installed WAS & created a deployment manager and a managed node. Then I created a new JVM using 'was_common_configure_create_server' action at Node level. It created the JVM. Then I tried to import it, so I can configure the JVM... but its not working. I tried import at cell, node level with configure all, server all, options. Every time it was successful, but I could not see my JVM in the configuration wizard of my RAF client. Finally, when I did import all with .drill, I see its complaining about NODE1_SERVERS_ON_NODE. Does NODE1_SERVERS_ON_NODE get created on its own? Also, I wish there is a documentation to simply create a JVM. That's the very first step any WAS admin would do after installing WebSphere. |
4 answers
|
Creating JVM itself is involved with lot of manual steps. Updating SERVERS_ON_NODE= , variable in configure.properties at node level, creating directories, copying build files.
There should be documentation for some basic WAS administration tasks, especially standing up a new environment. It's easy to import an existing environment created outside of RAF and then configure/modify it using RAF... but its a challenge to start from scratch. I have come across restarting cell, applying fixpacks, security PDFs which were helpful. |
Hi Mayur,
The NODE1_SERVERS_ON_NODE variable in the Build Forge Environment gets created by the environment generation wizard. In the same way that you updated the SERVERS_ON_NODE to take into account the new jvm you would have to update some of the BF Environment variables in order to take into account the new jvm. I'm glad you have found some of the PDF's which are available with helping out with some of the scenarios. As for adding a JVM to an existing environment, there is actually a fairly easy way to do this starting in the 3.0.x line of RAF. You can actually use the new environment generation wizard to do this for you. The environment generation wizard supports a few modes, and can be driven by a properties file. When you run through the wizard either through the command line or the web, it will generate one of these properties files in the RAFW_HOME/work directory, which will have the name <env>_<cell>.properties, where <env> is the name of the RAF environment that was given in the wizard and <cell> is the name of the cell given in the wizard. If you look into that file, you will notice it defines the topology which you created while going through the wizard. If you were to walk through the wizard again, giving all the same values as last time, except this time including the new jvm you wanted, you would notice that the <env>_<cell>.properties will now have the entries for the new jvm that you wanted in it. If you study that file and become familiar with it, you will not need to run through the environment generation wizard again to add your new jvm, you could just add the needed lines into the properties file and rerun the environment generation wizard on the command line in batch mode and it would copy the template files and do all the work that you manually did. Previously if you had run the environment generation wizard twice it would be destructive (it would delete the user/environments/<env> directory before recreating it), where as now it merely adds any new data specified in the properties file while leaving existing data alone. |
|
Thanks Jesus, Updating NODE1_SERVERS_ON_NODE variable did help.
However, I went through the new environment generation wizard again with same values as before, but it did not prompt me for any JVM related values. It updated <env>_<cell>.properties file, but it looks the same as before. Did I miss anything? <env>_<cell>.properties file defines all topology but mainly related to Cell, Dmgr, and nodes. |
Thanks Jesus, Updating NODE1_SERVERS_ON_NODE variable did help. Oh right, sorry. You can easily add nodes using the environment generation wizard but not jvms to an existing node. Only way that I'm aware of that you can have multiple nodes is if they belong to a cluster as you can specify the number of veritical cluster members in the environment generation wizard. I believe what you did is the way to add more jvm's to an existing node at the moment. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.