Leave feedback
  • Question

    Application Deployment on HP UNIX

Enter a new topic
  • Basavaraj Patil Basavaraj Patil
    0 likes 3185 views

    Hi All,

    It may be a very dumb question, please bear with me.

    What is the usual application deployment practice in terms of file system. If the product is installed under "/opt/strs/streamserve-5.4.0.GA.500", then where does the streamserve projects we develop should be deployed?

    Also, what are the design practices to setup folders for incoming RDI files, moving the process files to backup folder etc? 

    Kindly clarify.

    Thanks,

    Basavaraj

    Wednesday 12 May, 2010
  • Best Answer
    Henrik Wejdmark Henrik Wejdmark StreamServe Employee Administrator
    2 likes

    One more thing if you are using Persuasion...

    If you follow FHS, which I recommend, and use /var/spool/strs for your spool directories, you can't use Control Center to submit test files. The reason is that the management gateway is not allowed, for security reasons, to write outside of the management gateway root. The easiest workaround for this is to create a link in /var/opt/strs/mgwroot that links to /var/spool/strs ("ln -s /var/spool/strs /var/opt/strs/mgwroot/spool"). You can now use this linked directory to submit test files, but you should still use /var/spool/strs for your input connectors.

    This, of course, should only be needed in your TEST and DEV environments.

    //Cheers

         Henrik

    Wednesday 12 May, 2010
  • Vyv Lomax Vyv Lomax Administrator
    0 likes

    Moved to Administration.

    Wednesday 12 May, 2010
  • Henrik Wejdmark Henrik Wejdmark StreamServe Employee Administrator
    2 likes

    Hi!

    I would suggest following established UNIX standards (usually called FHS: Filesystem Hierarchy Standard). FHS specifies that 3:rd party software must be installed in /opt. Corresponding variable data must be stored under /var/opt and data to be process in /var/spool.

    Following this standards then gives the following for a StreamServe installation:

    1. You must install StreamServe under /opt/strs (or /opt/streamserve)
    2. You must deploy projects (in Persuasion create your management gateway root) under /var/opt/strs (or /var/opt/streamserve if you installed the binaries under /opt/streamserve)
    3. You must create input spool directories under /var/spool/strs (or /var/spool/streamserve...)
    4. You must create output spool directories in a similar fashion but according to the receiving application.
    5. You should specify StreamServe log files under /var/log or even under /var/log/strs (/var/log/streamserve...). You can also link the StreamServe log files into this location.

    Where backups are stored is not discussed in FHS, but a common place is /var/opt/strs/bak.

    You should then use absolute paths in your project when referring to the spool directories. This makes sense as the spool directory is a specified interface between StreamServe and other applications so they need to be in a specified location. This also allows the SysAdmin to move StreamServe around (if he wishes) without effecting any external applications StreamServe is integrated with. In other words, see the spool directories as a contract between StreamServe and the other application.

    If you use internal spool directories, for instance if you have a looped project, you should place them under /var/spool/strs, but could place them under /var/opt/strs if you truly see them as internal to StreamServe only. Placing them under /var/opt/spool makes the different processing steps more decoupled in case you would like to add another non-StreamServe step or replace one of the steps with a non-StreamServe software.

    The same thinking applies to all *nix operating systems StreamServe supports, but whith one difference. In HP-UX /var/opt is used as described above, but in the other *nix /var/lib is used instead, so in Linux, AIX or Solaris you would deploy your projects under /var/lib/strs. Why that's the case is a question for the historians...

    Note: The "must" and "should" here are not because of technical limitations but set by FHS to get a unified directory layout.

    //Cheers

          Henrik

    Wednesday 12 May, 2010
  • Henrik Wejdmark Henrik Wejdmark StreamServe Employee Administrator
    2 likes

    One more thing if you are using Persuasion...

    If you follow FHS, which I recommend, and use /var/spool/strs for your spool directories, you can't use Control Center to submit test files. The reason is that the management gateway is not allowed, for security reasons, to write outside of the management gateway root. The easiest workaround for this is to create a link in /var/opt/strs/mgwroot that links to /var/spool/strs ("ln -s /var/spool/strs /var/opt/strs/mgwroot/spool"). You can now use this linked directory to submit test files, but you should still use /var/spool/strs for your input connectors.

    This, of course, should only be needed in your TEST and DEV environments.

    //Cheers

         Henrik

    Wednesday 12 May, 2010
  • Basavaraj Patil Basavaraj Patil
    0 likes

    Many thanks. That answers my question in a best possible way.

    Cheers,

    Basav

    Thursday 20 May, 2010