Meta tags:

Headings (most frequently used words):

channels, feature, update, custom, channel, using, server, installation, installing, history, artifacts, to, pack, updates, prospero, process, with, packs, version, updating, working, fixed, repository, open, offline, subscribing, reverting, components, documentation, overview, concepts, general, provisioning, metadata, usage, management, replicating, additional, galleon, artifact, versioning, register, distributing, promoting, apply, changes, the, manifests, backing, maven, versions, manifest, resolving, conflicts, operation, limitations, predefined, profile, customized, or, mirrored, repositories, selecting, stability, level, of, provisioned, checking, candidates, alternative, existing, listing, unsubscribing, from, viewing, candidate, customizing, installed, in, patterns, limit, creating, blocklist, exclude,

Text of the page (most frequently used words):
the (339), channel (130), server (128), #manifest (90), #prospero (81), wildfly (79), repository (76), and (69), org (66), artifact (65), version (60), feature (59), maven (58), channels (58), update (57), can (56), repositories (52), artifacts (48), pack (44), using (42), final (40), for (39), yaml (39), versions (38), file (37), dir (37), wfly (37), used (36), updates (36), will (35), with (35), test (34), are (32), available (31), from (30), custom (30), updated (29), groupid (29), artifactid (29), galleon (29), list (26), installation (26), name (25), packs (25), candidate (25), changes (23), this (22), new (22), one (22), installed (22), configuration (22), components (21), https (21), path (21), example (19), customizations (19), not (18), has (18), latest (18), note (18), that (18), subscribed (18), customization (18), undertow (18), following (17), command (17), provisioning (17), any (16), metadata (16), servers (16), install (16), blocklist (15), all (15), should (15), files (15), schemaversion (14), xml (14), user (14), component (13), url (13), streams (13), contain (13), information (13), apply (13), operation (13), zip (13), history (13), revert (13), process (13), resolve (12), trusted (12), two (12), provide (12), during (12), have (12), datasources (12), state (12), definition (11), use (11), required (11), local (11), modified (11), tmp (11), resolved (10), deployed (10), when (10), content (10), generated (10), provisioned (10), manifests (9), customized (9), perform (9), add (9), default (9), additional (9), jboss (9), dev (9), only (8), into (8), contains (8), stream (8), such (8), coordinates (8), installing (8), users (8), those (8), may (8), provision (8), tool (8), deploy (7), found (7), each (7), different (7), bundle (7), system (7), base (7), standalone (7), layers (7), provided (7), central (7), original (7), packages (7), stability (7), server_home (7), 2023 (6), updating (6), time (6), needs (6), might (6), their (6), more (6), some (6), existing (6), archive (6), jar (6), directory (6), set (6), order (6), receive (6), subscribe (6), revision (6), see (6), repo1 (6), maven2 (6), public (6), core (6), way (6), profile (6), open (5), changed (5), next (5), sometimes (5), underlying (5), but (5), its (5), made (5), either (5), there (5), fixed (5), they (5), them (5), applied (5), same (5), location (5), distributed (5), folder (5), filesystem (5), added (5), separate (5), features (5), offline (5), parameter (5), config (5), instead (5), suffix (5), documentation (5), alternative (5), export (5), was (5), prepare (5), reverting (5), generate (5), requires (4), resolving (4), newer (4), find (4), based (4), would (4), like (4), provides (4), registered (4), software (4), com (4), working (4), foo (4), bar (4), promoting (4), nexus (4), host (4), three (4), included (4), case (4), commands (4), between (4), recorded (4), details (4), target (4), fpl (4), mysql (4), also (4), examples (4), subscribing (4), clone (4), downloaded (4), modules (4), completed (4), seconds (4), needed (4), c5215591 (4), reverted (4), record (4), change (4), stopped (4), step (4), local_repo (4), performed (4), exclude (3), mvn (3), dfile (3), dgroupid (3), dartifactid (3), dversion (3), dclassifier (3), dpackaging (3), durl (3), extension (3), listing (3), creating (3), versionpattern (3), ones (3), compatible (3), require (3), requested (3), backing (3), providing (3), published (3), listed (3), containing (3), other (3), make (3), possible (3), distributing (3), concepts (3), how (3), main (3), then (3), promoted (3), after (3), repo (3), resulting (3), online (3), multiple (3), shared (3), register (3), single (3), configure (3), always (3), includes (3), both (3), achieve (3), model (3), datasource (3), full (3), support (3), glnew (3), which (3), specify (3), create (3), groups (3), configurations (3), snapshot (3), date (3), copy (3), prepared (3), servlet (3), websockets (3), jsr (3), continue (3), applying (3), split (3), downtime (3), summary (3), management (3), defined (3), bin (3), while (3), level (3), need (3), manually (3), current (3), steps (3), persisted (3), download (3), matching (2), pick (2), reference (2), classifier (2), certain (2), above (2), uses (2), regular (2), incompatible (2), patterns (2), cannot (2), useful (2), controlled (2), type (2), curated (2), specific (2), stable (2), before (2), static (2), others (2), determine (2), replacing (2), previous (2), intended (2), types (2), github (2), extras (2), spec (2), removed (2), patch0001 (2), never (2), associated (2), home (2), unzip (2), instance (2), under (2), present (2), group (2), unique (2), hosted (2), than (2), choose (2), versioning (2), versioned (2), defines (2), could (2), operations (2), most (2), top (2), define (2), feature_add (2), similarly (2), executed (2), allow (2), selected (2), affected (2), been (2), created (2), capabilities (2), does (2), database (2), drivers (2), part (2), cases (2), relies (2), cloned (2), spyrkob (2), workspaces (2), installer (2), replicating (2), ab39b0c6 (2), phase (2), similar (2), 02805caa (2), 25t15 (2), back (2), remove (2), unsubscribing (2), replaced (2), subscribes (2), product (2), correct (2), proxy (2), corp (2), temporary (2), cli (2), reduce (2), running (2), candidates (2), described (2), preview (2), able (2), cache (2), argument (2), access (2), place (2), profiles (2), predefined (2), usage (2), folders (2), description (2), about (2), glold (2), old (2), conflict (2), compare (2), general (2), assemble (2), projects (2), releases (2), overview (2), last, 0100, deploying, neither, pattern, finally, again, blocks, another, option, blocked, apart, still, micro, field, expressions, limiting, starting, expression, filter, limit, strategy, means, attempt, exposing, seen, below, automatically, expose, excluding, look, follows, publishing, explicitly, none, kind, rely, fully, hand, development, testing, easier, immediately, exclusively, 3rd, party, combination, tested, making, sure, regressions, mechanisms, mixed, within, ways, collections, backwards, chapter, explain, behind, blob, doc, adoc, chosen, treated, older, overwritten, warning, manager, adding, extracting, inflating, repositry, inside, simply, copied, over, incremented, packaging, lists, syntax, addition, bundles, optional, applicable, http, distribute, among, auto, recieve, internal, serving, therefore, higher, 00001, web, recent, across, normal, f7488855, event, displaying, shows, mode, prefixed, without, parameters, layer, values, select, customizing, fact, further, bellow, refer, assuming, identified, known, connector, supplying, whose, lifecycle, itself, lets, driver, irrespective, supply, offer, allows, extend, offered, jsf, implemetnation, recreate, recreating, mrrc, redhat, restored, rebuild, length, 68301, 476, 606, 69383, exporting, complete, obtained, environment, building, preparing, latter, switched, off, duration, longer, overwrite, works, comparing, 348b9d9c, states, operate, performs, earlier, examined, hash, identifier, 19z, 04z, displays, viewing, restore, past, build, unsubscribes, stopping, receiving, previously, remaining, where, prints, subscriptions, managed, subcommands, currently, being, minimum, point, alternate, since, modifications, merge, stop, start, background, null, yes, shutdown, whole, check, checking, print, prompt, confirmation, accepted, once, fine, grained, control, separately, flags, package, experimental, segregate, flag, levels, selecting, accompanying, installs, generates, specified, mirrors, copies, doesn, mirrored, xmlns, urn, include, docs, configs, adds, consist, excluded, desired, simple, standard, via, internally, later, reviewed, rolled, gallon, recording, manifest_version, first, second, compares, applies, processes, resources, avoid, resource, locking, issues, shut, down, performing, limitations, discarded, resolution, exception, rule, considered, kept, sync, stored, paths, notified, incoming, setup, modify, value, generally, conflicts, every, delegates, attempts, intercepts, request, alternatively, referenced, dictated, even, beta13, security, elytron, jaspi, looks, supported, allowed, consists, distribution, archives, usually, tasks, distributions, piece, packaged, utilizes, aims, simplify, allowing, already, assembled, large, number, dependencies, various, traditional, rebuilt, release, your, launch, bat, line, client, programmatic, api, sources, tracking, supports, designed, manage, table, contents,

Text of the page (random words):
fests manifests are yaml file listing streams available in the channel for example a part of wildfly 27 0 0 manifest looks like schemaversion 1 0 0 name manifest for wildfly 27 description this manifest provides updates for wildfly 27 feature pack streams groupid org wildfly artifactid wildfly galleon pack version 27 0 0 final groupid org wildfly artifactid wildfly ee galleon pack version 27 0 0 final groupid org wildfly core artifactid wildfly core galleon pack version 19 0 0 beta13 groupid org wildfly core artifactid wildfly version version 19 0 0 final groupid org wildfly security artifactid wildfly elytron jaspi version 1 20 2 final the channel using this manifest would be defined as schemaversion 2 0 0 name channel for wildfly 27 manifest maven groupid org wildfly channels artifactid wildfly 27 0 repositories id central url https repo1 maven org maven2 when resolving artifacts using such channel the versions of artifacts will be dictated by the manifest even if newer version is available in the channel repositories note the manifest can be distributed as either a static file referenced in a channel by a url or as an artifact in a maven repository 2 2 2 open channels alternatively the channel can be defined to use the latest versions of artifacts available in its repositories schemaversion 2 0 0 name channel for wildfly 27 resolve if no stream latest repositories id central url https repo1 maven org maven2 3 general provisioning process 3 1 installation process prospero delegates provisioning server to galleon when galleon attempts to resolve components needed by the server instead of using versions provided by the feature packs prospero intercepts that request and uses wildfly channels to find the correct version of the component and resolve it from the channels repositories every time a server is provisioned it will receive the latest available components 3 2 update process when new versions of components are made available prospero can apply those to existing servers in order to find updates following steps are executed download the latest version of channel manifests from maven repositories compare component versions in the server to the latest available versions in channels if updates are available they will be applied to the server in a following process provision a new updated server in a temporary directory compare the changes between the new and old server apply changes in the new server to the base server 3 2 1 resolving update conflicts generally user modified files in the server will never be changed during the update sometimes server files might be modified both in the base server and in an incoming update an example of this might be a configuration file changed by the user to support their setup and changed in the update to modify a default configuration value in such case the user changes are persisted and not modified the new updated file configuration is created next to the old file with a glnew suffix and the user is notified that there was a conflict the user can resolve the conflict manually after the update the exception to this rule are files considered to be system paths they should not be modified by the user and will always be kept in sync with the changes provided by the updates any user changes will be replaced during the update and stored with a glold suffix an example of such files is a content of modules system folder user modified update modified system path resolution y n n a original file is used n y n a updated version is used original file is discarded y y y updated version is used original file is persisted with glold suffix y y n original file is used updated version is persisted with glnew suffix 3 2 2 update operation limitations during apply changes phase of updates any processes using server s resources need to be stopped to avoid resource locking issues the user should manually shut down the server before performing update to reduce server downtime the update operation can be performed in two steps prepare and apply in the first step a candidate update server is provisioned in a new directory the second step compares the changes between the candidate and the base server and applies them to the base server if the update is split into separate steps the prepare step can be performed while the server is running see working with update candidates for details 4 prospero server metadata in order for prospero to be able to update a server the server installation has to contain some additional metadata files those files contain information about server s current state and the subscribed channels the metadata is generated when the server is installed and can be modified using prospero commands the metadata is split between server_home galleon and server_home installation folders file description server_home installation installer channels yaml list of channels the server is subscribed to receive updates from server_home installation manifest yaml record of current versions of components installed in the server server_home installation manifest_version yaml record of channel manifests used to provision current server server_home galleon provisioning xml server_home galleon provisioned xml gallon files recording provisioned feature packs and their customizations 4 1 prospero update history the files in the installation and galleon folders should only be modified via the prospero tool not manually all metadata changes performed by prospero tool are internally versioned and can be later reviewed or rolled back by using the prospero history and prospero revert commands 5 usage 5 1 installation to provision a server prospero requires following information manifest definition location of channel s maven repositories server provisioning configuration 5 1 1 installing predefined server profile prospero provides a set of predefined profiles providing a simple way to install standard servers prospero sh install dir wfly 27 profile wildfly manifest path to wildfly manifest yaml the profile defines a feature pack name and required repositories it can also provide manifest information if that manifest is published in a maven repository 5 1 2 installing a feature pack if a desired server configuration is not provided by one of the profiles prospero can provision a feature pack based on its maven coordinates groupid artifactid the resulting server will have a default configuration provided by that feature pack prospero sh install dir wfly 27 1 fpl org wildfly wildfly ee galleon pack 2 manifest path to wildfly manifest yaml 3 repositories https repo1 maven org maven2 https repository jboss org nexus content groups public 4 directory to place provisioned server in maven groupid artifactid coordinates of the feature pack to be installed path to the manifest file list of maven repositories containing components listed in the channel file note an example wildfly manifest file is available in examples directory 5 1 3 installing a customized feature pack galleon feature packs consist of layers and packages that can be excluded or included to generate customized server in order to create a customized installation the required provisioning configuration need to be described in provisioning xml file for example following file adds configuration examples to the generated server xml version 1 0 installation xmlns urn jboss galleon provisioning 3 0 feature pack location org wildfly wildfly galleon pack zip packages include name docs examples configs packages feature pack installation the provisioning definition can then be used to create a server prospero sh install dir wfly 27 definition provisioning xml manifest path to wildfly manifest yaml repositories https repo1 maven org maven2 https repository jboss org nexus content groups public 5 1 4 using offline or mirrored repositories by default any artifacts required to provision the server will be resolved using public repositories if the system on which the installation is performed doesn t have access to the required repositories alternative repositories need to provided using the repositories argument the specified repositories can either be mirrors of public repositories or local filesystem copies of the repositories one way to generate such repository is installing the server on an online system using local cache argument prospero sh install 1 dir wfly 27 profile wildfly manifest path to wildfly manifest yaml local cache path to local_repo prospero sh install 2 dir offline wfly 27 profile wildfly manifest path to wildfly manifest yaml repositories path to local_repo offline generates a repository at path to local_repo installs the server using content of path to local_repo instead of default repositories note when using a groupid artifactid to resolve manifest from a repository the manifest artifact has to have accompanying maven metadata maven metadata xml 5 1 5 selecting stability level of provisioned server some feature packs may contain experimental or preview features not intended to be made available by default to separate those features from stable ones feature packs may segregate the features into stability levels at the provisioning time the user is able to change the default stability level of the feature pack by using the stability flag prospero sh install 1 dir wfly 31 profile wildfly manifest path to wildfly manifest yaml stability preview for more fine grained control the level of installed packages and configuration can be set separately using config stability and package stability flags 5 2 update once the server is installed it can receive updates published in the channels it is subscribed to following command can be used to update the server using the subscribed channels prospero sh update perform dir wfly 27 if any updates are available prospero will print the update summary and prompt for confirmation to continue if the updates are accepted the updated server will be prepared in a way described in update process note the server has to be stopped during update perform operation 5 2 1 checking updates prospero update list command can be used to check if any updates are available prospero sh update list dir wfly 27 5 2 2 working with update candidates when using prospero update perform command the server has to be stopped during the whole update process in order to reduce server downtime it is possible to generate an update candidate while the server is running and apply it to a stopped server in a separate step wfly 27 bin standalone sh dev null 1 prospero sh update prepare 2 dir wfly 27 candidate dir candidate dir yes wfly 27 bin jboss cli sh c shutdown 3 prospero sh update apply 4 dir wfly 27 candidate dir candidate dir start the server in background generate the candidate in candidate dir folder stop the server merge the updates found in candidate dir into wfly 27 server update candidate is a temporary server provisioned by prospero it is generated using the latest updates available in the channels but does not contain any user modifications of the original server note the candidate can only be applied to a server it was based on and only if the server has not been updated since the candidate was generated 5 2 3 using alternative repository if the repositories defined in subscribed channels are not available to the server alternative repositories can be provided using repositories parameter those repositories can point to a local copy of the repository or alternate online location prospero sh update perform dir wfly 27 repositories https proxy corp org maven central 1 the updates will be resolved from https proxy corp org maven central instead of the default repository the repositories can also be used to resolve artifact from a local copy of the repository prospero sh update perform dir wfly 27 repositories path to repository note at minimum the alternative repositories have to provide all the channel manifests that the server is subscribed to and updated artifacts 5 2 4 subscribing existing server prospero relies on additional metadata files being present in the server installation to provide updates using update subscribe command it is possible to generate required files in a server prospero sh update subscribe dir wfly 27 product wildfly 1 version 29 0 1 final 2 name of the installed server or name of the feature pack used to install the server version of installed server or feature pack the product and version information is needed to determine currently installed software and subscribe server to correct channels 5 3 channel management the server subscribes to the channels to receive updates from them the list of subscriptions can be managed using prospero channel subcommands 5 3 1 listing channels command prospero channel list prints a summary of subscribed channels prospero sh channel list dir wfly 27 server tmp wfly 27 is subscribed to following channels channel 0 manifest org wildfly channel wfly 27 repositories id central url https repo1 maven org maven2 5 3 2 subscribing to a channel command prospero channel add subscribes the server to receive updates from additional channels each channel has to have a unique name a manifest and a list of repositories the channel s artifacts will be used to resolve artifacts during next update prospero sh channel add channel name dev channel manifest org prospero channel wfly 27 dev 1 repositories file tmp dev repository 2 dir wfly 27 subscribing tmp wfly 27 to channel dev channel channel dev channel added the maven coordinates groupid artifactid of the new channel s manifest the maven repository where the manifest and artifacts can be found in 5 3 3 unsubscribing from a channel command channel remove unsubscribes the server from a selected channel stopping it from receiving updates from that channel the artifacts previously installed from that channel will be replaced with artifacts available in remaining channel during next update operation prospero sh channel remove channel name dev channel dir installation dir unsubscribing tmp wfly 27 from channel dev channel channel dev channel removed 5 4 update history each time the server is updated the previous state of the server is recorded that state includes the channels used to perform the update and the versions of artifacts used to build the server this information is used to restore the server back to past state 5 4 1 viewing history command history displays a list of all server updates prospero sh history dir wfly 27 02805caa 2023 05 25t15 07 19z update org wildfly channel wfly 27 1 0 1 c5215591 2023 05 25t15 05 04z install org wildfly channel wfly 27 1 0 0 the server state record contains following information a hash identifier date of the change type of the change installation update configuration change and a summary of channel manifests used in that update the details of each record can be examined using revision parameter prospero sh history dir wfly 27 revision 02805caa updates updated artifact io undertow undertow servlet 2...