1 2 Previous Next 18 Replies Latest reply on May 7, 2007 5:33 PM by Clebert Suconic

    Graphic Installer for Messaging

    Ovidiu Feodorov Master

       

      Alex Pinkin wrote:

      JEMS installer currently has a "JMS server" profile which is based on jbossmq. It currently includes jmx microkernel, logging, hsqldb, jndi, jaas, jta, and jbossmq services.

      So my understanding is that we need to add "JBoss Messaging" profile to the installer. Since user can only select one profile, JBoss Messaging and current jbossmq-based "JMS Server" will be mutually exclusive.

      Is there a need to have a standalone installer for JBoss Messaging or is it ok to just add a "Standalone JBoss Messaging" profile to the JEMS installer?

      Which version of JBoss Messaging?



        • 1. Re: Graphic Installer for Messaging
          Ovidiu Feodorov Master

           

          Alex wrote:
          So my understanding is that we need to add "JBoss Messaging" profile to the installer. Since user can only select one profile, JBoss Messaging and current jbossmq-based "JMS Server" will be mutually exclusive.


          This is correct. JBossMQ and Messaging are mutually exclusive.

          • 2. Re: Graphic Installer for Messaging
            Ovidiu Feodorov Master

             

            Alex wrote:
            Is there a need to have a standalone installer for JBoss Messaging or is it ok to just add a "Standalone JBoss Messaging" profile to the JEMS installer?


            For the time being, Messaging cannot exist without the Microkernel backbone, so just adding a "Standalone JBoss Messaging" profile to the JEMS installer would suffice.

            However, with MC integration, Messaging will be become truly standalone, so we will need a separated installer.

            Let's not worry about this right now, let's start with the "Standalone Messaging" profile.

            • 3. Re: Graphic Installer for Messaging
              Ovidiu Feodorov Master

               

              Alex wrote:
              Which version of JBoss Messaging?


              1.0.1.CR4 (it's in the repository), or if you wait a few days, 1.0.1.CR5.

              • 4. Re: Graphic Installer for Messaging
                Ovidiu Feodorov Master

                One more observation, though I think you already knew that: all transformations you need to apply to a "default" configuration are contained by the "release-admin.xml" script (for both standard and standalone installations).

                • 5. Re: Graphic Installer for Messaging
                  Alex Pinkin Newbie

                  Adding "Standalone JBoss Messaging" profile to the installer is not such a big deal. However, I'm currently maxed out with other work :( So we have to either postpone this or find somebody else to implement it. If we go with the 2nd approach, I could help out by explaining what needs to be done. Izpack installer knowledge will be required to get this done.

                  • 6. Re: Graphic Installer for Messaging
                    Alex Pinkin Newbie

                    btw this task is not as simple as adding a Messaging/JBossMQ radio button to the installer. We need to have full support for mutually exlcusive packs. izpack version that we are using doesn't support this. It's supposed to be addressed in the upcoming version of the izpack due in a couple of months. It's possible to patch the version of izpack that we are using of course.

                    I'll see if we can bump up the priority of this task, but so far we have a few large tasks on the installer which have higher priority than this.

                    • 7. Re: Graphic Installer for Messaging
                      Amit Bhayani Newbie

                      As of today JBoss Messaging 1.2.0GA is integrated with JEMS Installer. So when user downloads JEMS Installer ( take the latest code from SVN https://svn.jboss.org/repos/installer/jems-installer/trunk/) and selects one of the profiles (eg all, default, ejb3, ejb3-clustered and jms ) from InstallationGroupPanel, on Packs panel there is option to either select JBoss MQ or use JBoss Messaging in mutually exclusive way. If user selects JBoss Messaging, installer gives an option to install either as standalone or clustered JBoss Messaging.

                      This is good as it gives flexibility to user to install JBoss Messaging with EJB3/EJB3 Clustered. The only problem is that its not obvious that JEMS Installer is capable of installing JBoss Messaging and JBoss Messaging team needs to doccument this well.

                      • 8. Re: Graphic Installer for Messaging
                        Vladimir Ralev Newbie

                        BTW, 'all' and 'default' in the JEMS Installer are supposed to be J2EE 1.4. Is there anything from JBoss Messaging 1.2.0GA that would break this?

                        I found the following in the user guide:

                        Even if JBoss Messaging deployment descriptors are very similar to JBoss MQ deployment descriptors, they are not identical, so they will require some simple adjustments to get them to work with JBoss Messaging. Also, the database data model is completely different, so don't attempt to use JBoss Messaging with a JBossMQ data schema and vice-versa.


                        • 9. Re: Graphic Installer for Messaging
                          Alex Pinkin Newbie

                          we still need to cover use case when user already has AS 4.x installed, and just wants to update it with Messaging. So it would be nice to have a standalone messaging installer as well.

                          • 10. Re: Graphic Installer for Messaging
                            Vladimir Ralev Newbie

                            OK, here is the the JEMS Installer (not released) that includes Messaging 1.2.GA (to test it you must run ant in the main folder):

                            http://anonsvn.jboss.org/repos/installer/jems-installer/trunk/
                            installer output: output/jems-installer-1.2.0.GA.jar

                            Currently we have some issues with the database selection because messaging still suports a limited set of databases. We will probably remove the unsupported dbms' when messaging is selected, and use the full set if the user goes with jbossmq (as before). We may also refactor the Messaging Config panel, because the only real messaging-related config is the security domain. Note that it doesn't include the mysql drivers.

                            This is the upgrade/patch installer which installs messaging on an existing AS:

                            http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_JBINSTALL-246/
                            installer output: output/messaging-installer-1.2.0.GA.jar

                            Unlike the JEMS Installer it uses directly the release-admin.xml, because it's capable of modifying "dirty" config files (we can't do that without ant in the installer right now). Here, we collect the ant properties database, ports, id from the user and pass them to the script. In installation path you must select the JBOSS_HOME. I'll also create a readme, which explains everything to the user (only mysql out of the box, names of AS configs, etc).

                            Thanks for any suggestions and feedback.

                            • 11. Re: Graphic Installer for Messaging
                              Tim Fox Master

                               

                              "vladimir.ralev@jboss.com" wrote:


                              Currently we have some issues with the database selection because messaging still suports a limited set of databases. We will probably remove the unsupported dbms' when messaging is selected, and use the full set if the user goes with jbossmq (as before). We may also refactor the Messaging Config panel, because the only real messaging-related config is the security domain.


                              Hi Vladimir -

                              Can you tell me which databases the installer will allow to be selected for JBM?

                              Also, you say the only messaging related config is the security domain, but there are a bunch of other settings too.

                              The question is, whether on not we want the user to be able to change these on install, or should we stick with the defaults?

                              I'm not familiar with the installer, but if there is a "custom install" option, then I guess that would be a good place for the user to be able to override the defaults.

                              • 12. Re: Graphic Installer for Messaging
                                Vladimir Ralev Newbie

                                We will support only those databases for which we have config files in jboss-messaging-1.2.0.GA\examples\config - mysql, mssql, portgre, sybase, db2 and oracle. (+hsql for non-clustered) If there is something else, let me know.

                                Here is a screenshot of the JEMS installer's Messaging config dialog (no db, because it uses a datasource defined earlier, which is used for other things too):
                                http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_JBINSTALL-246/screenshots/MessagingConfig-JEMS.JPG

                                And this is how it looks in the dedicated installer (db choice is for clustered configurations only, it's not very clear at the moment):
                                http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_JBINSTALL-246/screenshots/MessagingConfig-Dedicated.JPG

                                The question is, whether on not we want the user to be able to change these on install, or should we stick with the defaults?

                                I was hoping you would know :) . If you have any preferences about this comment here. We do have Advanced/Standard selector in the installer (standard is for the defaults). This Messaging Configuration dialog is displayed only if the user is in advanced mode.

                                • 13. Re: Graphic Installer for Messaging
                                  Tim Fox Master

                                   

                                  "vladimir.ralev@jboss.com" wrote:
                                  We will support only those databases for which we have config files in jboss-messaging-1.2.0.GA\examples\config - mysql, mssql, portgre, sybase, db2 and oracle. (+hsql for non-clustered) If there is something else, let me know.
                                  [/quote}

                                  That's good. Although the db2 configuration is currently untested (can we put a warning by it saying so?)



                                  The question is, whether on not we want the user to be able to change these on install, or should we stick with the defaults?

                                  I was hoping you would know :) . If you have any preferences about this comment here. We do have Advanced/Standard selector in the installer (standard is for the defaults). This Messaging Configuration diaog is displayed only if the user is in advanced mode.



                                  Yes, I think we should add the settings on this page.

                                  BTW How easy is it to tweak the installer when we add/change a config setting or database? Is it just some XML config that we need to change somwhere? If so, where?

                                  Thx

                                  • 14. Re: Graphic Installer for Messaging
                                    Vladimir Ralev Newbie

                                    It's simple if you know the names and the possible values of the variables that contain user input data. For example we generate the hsqldb-persistence-service.xml with the velocity template http://anonsvn.jboss.org/repos/installer/jems-installer/trunk/templates/jboss-messaging.sar/hsqldb-persistence-service.xml.vm

                                    based on the $database variable. (Even though the file name remains "hsqldb-persist.." the contents are overwritten.)

                                    The $database variable (and most other variables) are being created and assigned in the user input panels defined here http://anonsvn.jboss.org/repos/installer/jems-installer/trunk/userInputSpec.xml. Here we define the forms and the controls (each control is mapped to some variable).

                                    Once the user fills out the forms in the panels (all variables set), during the file-copy phase the .vm templates are processed.

                                    1 2 Previous Next