• Extract the files from the ZIP file into a directory of your choice. If a binary snapshot was downloaded, proceed to the #Starting ActiveMQ section of this document. If a source snapshot was downloaded, perform step 6 and step 7 of the #Windows Source Installation procedure. Following start-up, proceed to the #Testing the Installation section.
• The best way to unzip them is to do File:Import scales.zip in Scala since that takes care of the fact that they are stored in Windows text format (CR-LF). Macintosh OSX, Linux and Unix users: if you don't do it like this, you can unzip them via the command line with the -a (autoconvert) option.

• Osx Create Zip File Command Line
• Mac Os X Create Zip File With Password
• Mac Create Zip File

Create a virtual HDD image where macOS will be installed. If you change the name of the disk image from machdd.img to something else, the boot scripts will need to be updated to point to the new image name. Qemu-img create -f qcow2 machddng.img 128G NOTE: Create this HDD image file on a fast SSD/NVMe disk for best results. Create a password-protected ZIP file in OS X. To create a password-protected Zip file in OS X, you can use the Terminal and you don’t need to download any other programs. First, place all of the files that you want to compress into a single folder, and then rename that folder to the name that you want your ZIP file to have. Open the Terminal.

Click on 'How to' articles for in-depth mini tutorials about each single frequently asked topic.
Click back or 'FAQ' link in navigation bar to return to Frequently Asked Questions' table of contents.
FAQ's 'How to' table of contents is sorted in categories:

• How to perform supported operations (extraction, creation, editing, encryption...) for each of most common supported archive type (7Z, ACE, BR, BZ2, RAR, TAR, ZIP, ZIPX, ZST...)

• Features and history of most common supported archive formats (7Z, ACE, BR, RAR, TAR, ZIP, ZIPX, ZST...)

• Archive manager, common questions about file compression / file archiving operations and best practices

• File manager, documentation about PeaZip's file browser and file management features

• Security, all topics related to data security, such as encryption, secure delete, scanning archives for threats...

• Tips & tricks, miscellaneous suggestion about PeaZip and possible applications of functions provided by the program

'Frequently asked questions' section offers syntetic, quick hints about most common topics about program's installation, configuration and usage.
For a comprehensive tutorial and online documentation to get further help (not organized in question-answer form as in FAQ section), you can refer to 'Online support' section.

Frequently asked questions

FAQ: change application's language and settings

From Options > Localization you can select the application's language, PeaZip free archiver will display language files in peazip_folderreslang path.
You can download additional localizations from 'PeaZip Translations' project on GitHub, and manually copy them in peazipfolderreslang path. New translations are made available for users as soon as they are provided, and then will be packaged with future releases of the program for ease of use.
From Options > Settings in main menu you can deeply customize the applications behaviour; see program's online help file for more detailed description of available options, like turning on/off messages, choosing a default archive format, etc...

PeaZip introduces some concepts to improve the way archiving-related tasks are handled, bridging the gap between GUI and command line based software.

• Save archive layout: archive layout is a list of object scheduled to be archived or extracted. When creating a new archive or when extracting existing archives, files and folders can be added to the file archiving or extraction layout which is visible on the bottom of the first tab of archiving and extraction interfaces. Layout can be saved (and edited as a text file), a saved layout can be added to the current archiving or extraction layout and PeaZip will take care to verify if entries are duplicate and if they accessible. Layouts make easier to define, merge, handle, maintain and edit with external tools the lists of object to be archived or extracted (in example, for backup or restore purpouse).

• Save task definition as script: most of the tasks possible to do with PeaZip can be exported as a command line in a text file, using Save task definition buttons in Console tab, both in file archiving / conversion and in extraction interface (or button in task's window). From the console tab the task can be modified and tested. Advanced users can use those saved scripts (main menu Tools > Saved task definition scripts points to the default PeaZip's script directory) to speed up building scripts, or for learning purpose about the underlying executables, or for fine-tuning the task bejond the GUI's capabilities.

• Schedule task definition script: Schedule tab in archive/conversion and extraction interfaces is intended as a quick way to schedule a task (in example to automate backup or restore) in system's Task scheduler (Microsoft Windows Vista and newer systems).

• Save task log
  Each task launched by PeaZip run in a separate PeaLauncher instance. If a task ends in error, or test and list tasks, the task's window is kept open to let the user inspect and the task log it generated, and the command behind the job.
  

• Console mode launch applications with their native console interface, allowing the user to spare resources and to see the native text-based progress indicator for each application, which generally is more reliable and detailed than the graphical one.
• Graphic mode (default) wraps the job in a graphical presentation making easier to read and save job log and job definition, to change underlying process priority, to pause or stop the job and to open the output path in a click. Optionally at job completion the window can auto close itself or shut down the system. This is the default mode for most job types.
  
• Graphic + console mode allows to get the best of the two modes, with a GUI to control the job and a console window to have a real-time log of ongoing activity.

FAQ: how to stop and undo archiving / extraction tasks

You can use 'Stop' button in the graphic wrapper to stop the underlying job's process; partial outcome of the task will not be automatically deleted and will remain available for inspection, as well the job log.

FAQ: manage .7Z, .ACE, .ARC, . BR, .BZ2, .CAB, .GZip, .PAQ, .RAR, .TAR, .ZIP, .ZIPX, .ZST files...

PeaZip free archiver utility supports more than 200 file archives extensions, only most common ones are associated by the installer to the application, but all supported file types can be opened from PeaZip's file browser.
Some file types are minor variations of most common archive formats (in example APK, JAR, PAK and many more variants, and COMPOUND, Microsoft Office and Open Office file formats, for structure and supported file compression standards, are very similar to zip archives) and generally can be opened, even when not explicitly supported by PeaZip, modifying the file extension.
Anyway, in those cases, additional standards may be mandatory implemented by the format (in example resource's naming conventions, checksums etc), so if you modify a file opened in that way be sure to know the specific file format standard.
Hint: a comprehensive online database of file extensions
PeaZip uses Open Source components from 7-Zip/p7zip, FreeArc, and other state of art Open Source software to offer the same GUI frontend to create, browse, test and extract 7z and ZIP archives under Linux and MS Windows as well.
PeaZip for Linux/BSD is desktop-neutral so it can be used either under Gnome or KDE desktop environment, or also other desktop managers. System integration mechanisms relies on FreeDesktop standards and requires a compliant environment, such Gnome and KDE, but basic file archiving operations are not affected.
PeaZip can

• create single or separate archives
• add/remove files from existing archives
• convert existing archives to another format (in example convert a RAR file in a ZIP or 7Z file)
  
• extract multiple archives at once
  
• browse and search archive's content
• preview objects into zip files
  
• perform partial archive's extraction, extracting only selected or filtered objects

• Use context menu entry 'Extract here' or 'Extract here (to new folder)'
  
• Use context menu entry 'Extract...' to be asked for output path and other options
• Open the archive in PeaZip in PeaZip and use 'Extract' button (you can chose output path, enter password and other options before confirming with 'Ok') to extract selected object, or Extract > Extract all in application's context menu to extract all the archive
• Open the archive in PeaZip and drag desired objects from the application to the system (the opposite can be used to add objects to the archive)
  
• Open the archive in PeaZip and doubleclick on an archived file to preview it

To enter password in PeaZip click in the locker icon in the status bar (in the file/archive browser) or the locker icon below output address field in extraction (decryption) and archiving (encryption) interfaces, or click Tools > Enter password / keyfile in main menu, or press F9.
Using a Keyfile is optional, leave it blank if you don't want to rely on two factor authentication - use of keyfile increases security over password only encryption since also having access to the keyfile will be required to perform the extraction, hampering dictionary and social engineering attacks for password guessing shortcuts.
PeaZip features an encrypted password manager (Tools > Password manager from main menu) to securely manage user's passwords.
Drag and drop is supported on MS Windows systems.
PeaZip can perform drag and drop from the system to the application, for adding files to new archive layout or for opening existing archives dragged to the application, and drag and drop from the application to the system, for file copy and for extraction form archives.
By default the application uses improved native Windows drag and drop mechanism, but optionally it can use its own custom drag and drop implementation, from Options > Settings > General.
Advantage of PeaZip's drag and drop (both types) is that the application doesn't need to copy files to system's temporary path on drag&drop operations, speeding up the operation if large files are involved (especially noticeable if files are not in the same volume of system's temp directory) and don't risking to lowen the security of the operation if the system's temp folder has security policies different from the ones of the intended output destination.
PeaZip free archiving utility is not yet integrated with Windows drag and drop's context menu handler (but it is integrated with rightclick's context menu for zipping, unzipping and advanced operations).
FAQ: is PeaZip faster/slower than... does it compress better than... ?

Being PeaZip a frontend application, each time an archive is queried interprocess communication is involved: if the program / the input path / the output path is on a slow network or slow unit this may bring a slowdown.
But most of the time is usually spent on file archiving / extracting operations; in this case PeaZip is as fast as the invoked application (7z, which is command line 7-Zip executable, Paq, Pea, UPX etc...), which performance is mainly bound to the algorithm and the data compression level involved, being the underlying executables good and efficient implementations.
PeaZip features extremely fast operations, as tar/untar, split/merge files, create archives with 'store' compression level, quite fast operations (in example Deflate based algorithms, like in gzip compression), slow/quite slow operations (when bzip2, LZMA, PPMd, unrar, unace are involved), up to very slow operations when PAQ at highest compression levels are used.
Currently, fastest compression (faster than any benchmarked archiver utility) is attained with Google's Brotli and Facebook's Zstandard algorithms.
A wide range of performances and compression levels can be attained using PeaZip, the point is in chosing the right balance between the two factors.
Enforcing data security employing cryptography raises a little the computing power usage, but on average compter the impact of this factor is usually negligible; decryption of protected archives is usually even faster than encryption.
FAQ: where does compressed and extracted files go?

By default PeaZip prompts to zip / unzip in the same path of the input object, but in archiving and extraction interfaces the Output group allows to set the output path.
The button on the right of the output address bar opens a standard output selection dialog, while on the left the button shows a dropdown menu allowing to select an output path from various pre-sets: system's paths (inlcuding: current item's path, the last used path, desktop, documents etc...), paths of bookmarked elements, and recently visited paths (paths visited in the current session, and paths of previously created or extracted archives). From this menu It is also possible to set a default custom output path.
UPX is the only exception from that mechanism since it always compress the input executable file in place.
In Options > Settings first tab it is available the option 'Open output path when job completes'.
Otherwise iin the same tab is available the PeaLauncher options dropdown menu: select 'Always keep open to inspect job report' to be able, alongside other features, to click 'Open output path' button after the job is completed - otherwise by default the job's window will auto close if no error is reported.
PeaZip may be performing lengthy operations which needs to wait completion; in example PeaZip may be querying the archive for browsing (especially when flat mode is used on archives containing many files) or adding / removing files from archives (needed time depends on the size of the objects and compression options), or querying the system about files and folders to be added to archive layout.
Any time a potentially lengthy operation is requested the cursor is changed to horglass and, when possible, an animation is performed to inform the user that the operation is running and is needing some time to be completed.
On startup, PeaZip query the mounted units, so it can be slowed down if, in example, the system features remote units over a slow network, or has defective drives, or slow removable units (like CD/DVD) are being loaded in the same time.
Another potential source of slowness, both for PeaZip and underlying backend processes, may be slowed-down disk subsystem, i.e. by high degree of fragmentation, or cuncurrent disk usage by antivirus/antimalware (especially if inspecting program's or work files), p2p, file indexing programs (like Google Desktop, Picasa etc), system updates, paging, etc...
[to run disk-bound speed tests, please take in account that on most systems files are cached after first usage, so becomes accessible in less time in following tests]
Some algorithms featured by PeaZip free archiver (PAQ, ARC and 7Z at highest level of compression...) requires big amounts of memory, so it is recommended to avoid extreme settings which results in the system to page to disk, that is some orders of magnitude slower than RAM.
FAQ: why the progress bar has stopped, or reached the max, and the job is still running?

The graphic progress bar is accurate in tracking the job progress form most archive formats (feedback depend on the backend binary handling the archive), but the native console mode is more detailed as displays more real time information about the process.
In Options > Settings first tab, in 'Backend binaries interface' dropdown menu, you can set PeaZip to display both the GUI and the console window if you want to have both a graphical interface to control the job and a detailed, real time report on ongoing activities in the console window.


PeaZip free archiver can be integrated to Microsoft Windows system in the following ways

• You can rightclick on an object or a group of objects and use the PeaZip's entries in context menu or 'SendTo' menu to directly send input object(s) to a specified PeaZip's function.
• You can drag object(s) on PeaZip's program icon and the program will try to decide how to handle the object(s) provided by the user.
• You can drag objects to an open PeaZip instance to put the application in full control of the process
  
• You can doubleclick on files of types associated with PeaZip to open them.

You can reconfigure the application's system integration running the configuration tool in Options > System integration (which automatically requires administration rights if needed), or selecting 'Custom installation / Configuration' in the installer to access to more options.
PeaZip run on any full Win32 Microsoft Windows desktop system (or compatible, as Wine and ReactOS) for any type of personal computer or tablet (recent releases GUI is designed to be touch-friendly in terms of clickable area and functions discoverability), so at current level of development is not known of being possible to run it on Windows RT-only devices.

PeaZip is a standalone, almost self contained zip / unzip application: you can unpack peazip_portable package (.tar.gz) in any path and just click on peazip binary; see FreeDesktop_integration folder in program's path to know how to integrate PeaZip with the desktop environment (Gnome, KDE...).

How do I make my system aware of PeaZip functionalities?
PeaZip installable packages authomatically create application's icon, list PeaZip in available applications and create some KDE ServiceMenu entries to reach most used program's functions (archive, open, extract here, extract to new folder).
FreeDesktop_integration folder (featured both in installable and in standalone versions) contains .desktop files and simple instructions to add PeaZip to start menus and context menus of desktop environments following the FreeDesktop standards (like Gnome and KDE), and Nautilus scripts folder which can be manually copied to user's Nautilus script's folder to add PeaZip's functionalities to Gnome's context menu.
What if I cannot run PeaZip due to unresolved dependencies.
If the system report missing libraries the first time you are running PeaZip binary, you can generally find missing libraries on your installation media or you can search them online using your installation or update manager, or even in a web based .rpm or .deb repository; generally missing libraries are standard, well known and widely available gtk/gkd components (the most common is libgdk_pixbuf library).
What are hardware/software prerequisites?
PeaZip should run on x86-compatible CPU due to some performance critical sections written in ASM, but pure Pascal replacements exists for those units, allowing to port PeaZip to other architectures (i.e. ARM).
CPU and, mainly, RAM requisites are bound top the chosen algorithm and compression level, ranging to few KB for simpler algorithms (like when storing files without compression in tar/gz/zip formats) to above than a GB for most powerful and complex algorithms at highest compression level, like LZMA, PPMd and PAQ). Needless to say, it is the choice of the file compression algorithm the most important factor in determination of job's speed, even if usually the most advanced algorithms are also the ones which scales better in performances in multicore enviroments.
As for software prerequisites, all needed software invoked by the frontend is included in PeaZip packages (being available under suitable licenses, as open source or royalty free) so no custom package is needed to be installed to make PeaZip work (with the possible exception of some standard gtk/gdk related libraries needed to run PeaZip, PeaLauncher and Pea binaries, which may miss in some system, but are well known, trustable and widely available).
If you don't want non open source software in your system, like unrar.so (which brings specific license restrictions about reverse engineering) or unace binary (closed source, royalty free), you simply need to delete them from /res/ path in program's folder.

Apple macOS / OSX / Darwin

Lazarus IDE support for Carbon widgetset is alpha (a solution could be using alternative libraries, as Qt, but I would prefer the native, default widgetset), and moreover I can rarely have full access to OSX systems; however the Lazarus support for OSX is quickly progressing, and my interest in porting PeaZip to OSX platform remains very high.
I hope to be able to deploy PeaZip free archiver for OSX in future, and any help and feedback from users of Lazarus IDE on Apple macOS / OSX / Darwin will be welcome.
For the moment, on BSD-family page are available some suggestion about running PeaZip on Apple Mac OSX using emulation / wrapping methods.

Using ActiveMQ > Getting Started

Introduction

This document describes how to install and configure ActiveMQ 5.x for both Unix and Windows’ platforms.

Document Organization

The Getting Started Guide for ActiveMQ 5.x document contains the following sections:

• Installation Procedure for Windows
• Installation Procedure for Unix
• Starting ActiveMQ
• Testing the Installation

Pre-Installation Requirements

Hardware:

• ~ 60 MB of free disk space for the ActiveMQ 5.x binary distribution.
  (you need additional disk space for storing persistent messages to disk)
• ~ 300 MB of free disk space for the ActiveMQ 5.x source or developer’s distributions.

`Operating Systems:**

• Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.
• Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.

Environment:

• Java Runtime Environment (JRE)JRE 1.7 (1.6 for version <=5.10.0)
  (a JDK is required if you plan to recompile source code)
• The JAVA_HOME environment variable must be set to the directory where the JRE is installed
  (Unix: the binary “java” has to be resolvable by the PATH variable; execute “which java” to verify)
• Maven 3.0.0 build system
  (only if you plan to recompile source code)
• JARs that will be used must be added to the classpath.
  (only if you plan to recompile source code)

Installation Procedure for Windows

This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.

Windows Binary Installation

This procedure explains how to download and install the binary distribution on a Windows system.

1. Download the latest release
   (see Download -> “The latest stable release” -> “apache-activemq-x.x.x-bin.zip”)
2. Extract the files from the ZIP file into a directory of your choice.
3. Proceed to the #Starting ActiveMQ section of this document.
4. Following start-up, go to the #Testing the Installation section of this document.

Windows Source Installation

This procedure explains how to download and install the source distribution on a Windows system.

1. Download the latest release
   (see Download -> “The latest stable release” -> “apache-activemq-x.x.x-source-release.zip”)
2. Extract ActiveMQ from the ZIP file into a directory of your choice.
3. The recommended method of building ActiveMQ is the following:

   where [activemq_install_dir] is the directory in which ActiveMQ was installed.

4. If you prefer to use an IDE, then you can auto-generate the IDE’s project file using maven plugins:

   or

   Feel free to use any other applicable IDE. Please refer to the plugin reference for more details.

5. Start ActiveMQ from the target directory, for example:

   NOTE: Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.

6. Proceed to the #Testing the Installation section.

   Warning

   If you are building ActiveMQ 4.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.

Windows Developer’s Release

This procedure explains how to download and install the latest developer’s snapshot.

1. Open the release archive: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
   (open one of the SNAPSHOT directories)
2. Select the version of ActiveMQ to download (if necessary, scroll down to see the ActiveMQ snapshots).
3. Extract the files from the ZIP file into a directory of your choice.
4. If a binary snapshot was downloaded, proceed to the #Starting ActiveMQ section of this document.
   If a source snapshot was downloaded, perform step 6 and step 7 of the #Windows Source Installation procedure.
5. Following start-up, proceed to the #Testing the Installation section.

Installation Procedure for Unix

Unix Binary Installation

This procedure explains how to download and install the binary distribution on a Unix system.
NOTE: There are several alternative ways to perform this type of installation.

1. Download the activemq zipped tarball file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:
   (see Download -> “The latest stable release”)
2. Extract the files from the zipped tarball into a directory of your choice. For example:

3. Proceed to the #Starting ActiveMQ section of this document.

4. Following start-up, go to the #Testing the Installation section.

Using Homebrew installer on OSX

If you use OSX as your platform, you can use Homebrew package manager to easily install Apache ActiveMQ.

1. After installing Homebrew package manager successfully, just run

   You can expect the following output:

ActiveMQ will be installed in /usr/local/Cellar/apache-activemq/x.x.x/ directory (where x.x.x denotes the actual version being installed).

Now you can proceed to #Starting ActiveMQ and #Testing the Installation sections.

Unix Source Installation

This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous #Unix Binary Installation section for details on how to install ActiveMQ without a browser.

1. Download the latest source release
   (see Download -> “The latest stable release” -> “activemq-parent-x.x.x-source-release.zip”)
2. Extract the files from the ZIP file into a directory of your choice. For example:
3. Build ActiveMQ using Maven:
   The preferred method of building ActiveMQ is the following:

   If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):

   If you prefer to use an IDE then you can auto-generate the IDE’s project file using maven plugins:

   or

   Feel free to use any other applicable IDE. Please refer to the plugin reference for more details.
   NOTE: Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.

4. Proceed to the #Starting ActiveMQ section of this document.
5. Proceed to #Testing the Installation section.

Unix Developer’s Release

This procedure explains how to download and install the latest developer’s snapshot.

1. Open the release archive: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
   (open one of the SNAPSHOT directories)
2. Select the version of ActiveMQ to download (you may have to scroll down to see the ActiveMQ snapshots).
   The filename will be similar to: activemq-x.x.x-tar.gz.
3. Extract the files from the gzip file into a directory of your choice. For example:
   For a binary developer’s snapshot:

   For a source developer’s snapshot:

4. If a binary snapshot was downloaded, to make it executable, the ActiveMQ script may need its permissions changed:
5. For a binary snapshot, proceed to the #Starting ActiveMQ section of this document.
6. If a source snapshot was downloaded perform steps 6 - 8 of the #Unix Source Installation procedure.
7. Proceed to the #Testing the Installation section.

Starting ActiveMQ

There now follows instructions on how to run the ActiveMQ Message Broker.

On Windows:

From a console window, change to the installation directory and run ActiveMQ:

where [activemq_install_dir] is the directory in which ActiveMQ was installed, e.g., c:Program FilesActiveMQ-5.x.
Then type:

`NOTE:** Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.

On Unix:

From a command shell, change to the installation directory and run ActiveMQ as a foregroud process:

From a command shell, change to the installation directory and run ActiveMQ as a daemon process:

More help

For other ways of running the broker see Here. For example you can run an embedded broker inside your JMS Connection to avoid starting a separate process.

Testing the Installation

Using the administrative interface

• Open the administrative interface
• • URL: http://127.0.0.1:8161/admin/
  • Login: admin
  • Passwort: admin
• Navigate to “Queues”
• Add a queue name and click create
• Send test message by klicking on “Send to”

Logfile and console output

If ActiveMQ is up and running without problems, the Window’s console window or the Unix command shell will display information similar to the following log line (see stdout output or “[activemq_install_dir]/data/activemq.log”):

Listen port

ActiveMQ’s default port is 61616. From another window run netstat and search for port 61616.

Osx Create Zip File Command Line

From a Windows console, type:

OR

From a Unix command shell, type:

Monitoring ActiveMQ

You can monitor ActiveMQ using the Web Console by pointing your browser at http://localhost:8161/admin.

From ActiveMQ 5.8 onwards the web apps is secured out of the box.
The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.

Or you can use the JMX support to view the running state of ActiveMQ.

Mac Os X Create Zip File With Password

For more information see the file docs/WebConsole-README.txt in the distribution.

Stopping ActiveMQ

For both Windows and Unix installations, terminate ActiveMQ by typing “CTRL-C” in the console or command shell in which it is running.

If ActiveMQ was started in the background on Unix, the process can be killed, with the following:

Mac Create Zip File

Configuring ActiveMQ

The ActiveMQ broker should now run. You can configure the broker by specifying an Xml Configuration file as a parameter to the activemq command. An alternative is to use the Broker Configuration URI to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also

Also see Configuring Transports to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.

See the Initial Configuration for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code

If you want to use JNDI to connect to your JMS provider then please view the JNDI Support. If you are a Spring user you should read about Spring Support

After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the Configuration section.

Additional Resources

If you are new to using ActiveMQ, running the Web Samples or the Examples is a good next step to learn more about ActiveMQ.

The Commercial Providers listed on the Support page may also have additional documentation, examples, tutorials, etc… that can help you get started.