Additional Architectural Considerations and Use Cases

There are more architectural considerations and use cases around the use of FlexApp Packaging Automation than those described in Architecture and Multi-Admin Usage. Here are additional use case examples that can help you plan your installation of FPA.

Considerations

Some of the considerations are the following:

  • Do you need to be able to perform multiple captures simultaneously?
    • Maybe you do not need a Primary Packaging Manager; only a single Capture Agent.
  • Do you need to integrate with an existing automation workflow?
    • In addition to not needing a Primary Packaging Manager, maybe you do not use a dedicated Capture Agent and prefer to install the FPA Capture Agent on a machine to run synchronous or in-line with an existing process or script.

Automated captures as a part of DEVOPS

For automation workflows that output updated applications on a regular basis, you can incorporate a single Capture Agent machine without the need for a Primary Packaging Manager.

  • The existing automation server would get the FPA Remote CLI installed, and optionally, a Defaults.JSON file created with encrypted credentials and presets.
  • The automation workflow would be appended with a call to the FPA Agent Service to start a capture of a script or silent installer, asynchronously or synchronously, on a remote Capture Agent machine:
  • Copy 
    Agent-Client.exe Create Package /AgentAddress <https://agent-server:9074> /AgentUsername "fpa_services" /AgentPassword "<pass>" /Name "<PackageName>" /PackageVersion <n.n.n.n> /Path "\\fileserver\share\my-new-software-packages" /Installer "\\fileserver\share\my-software\silent-installation-script.ps1" /PathUsername "<domain\user>" /PathPassword "<pass>" /PuAddress <https://ProuServerAddress:8000> /PuUsername "<domain\user>" /PuPassword "<pass>"

On-Agent scripted synchronous captures

It is also possible to bypass the Agent Service of a Capture Agent and execute a capture directly on the Capture Agent machine via the command line. This can help with scenarios where you need to run scripts on the Capture Agent before a capture and then continue the script upon completion.

  • The script could invoke a capture directly, in-session even, bypassing the Agent Service.
  • Copy 
    fpa-packager.exe Package /Name "<PackageName>" /PackageVersion <n.n.n.n> /Path "\\fileserver\share\my-new-software-packages" /Installer "\\fileserver\share\my-software\installation-script.bat" /NoSystemRestore
  • The Package-Create process would end when the capture is complete and the script could continue and could then take action by moving the new package, etc.
  • If executed in-session against an installer or script that is not silent, the user can interact with the installer during capture.