Adobe 38000382 JRun Guide - Page 42

About files for custom installations, Using BIN files, BIN file list

Get Adobe 38000382 - Macromedia JRun - Mac PDF manuals and user guides
UPC - 718659575946
View all Adobe 38000382 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

About files for custom installations The JRun SDK includes the following groups of files that you can use to create custom JRun installers on any supported platform: • BIN files Prebuilt binary files that you can use across platforms, separated into functional components. • filesets Raw filesets of the JRun installation. For a complete description of the contents of this directory, see "JRun components" on page 5. • Merge modules Windows Installer merge modules for Windows Installers only. For information, see Chapter 3, "Windows JRun Installers" on page 17. This section focuses on using the BIN files to build custom installers. Using BIN files The JRun SDK includes the JRun modules as binary (BIN) files. Based on your license agreement, you can access some or all of these modules. The BIN files are in the sdk_root/installers/unix directory. You can use the BIN files to create a JRun installer with either a GUI installer tool, such as InstallAnywhere, or a shell script. You can import these BIN files into any compatible installer development environment. You can also execute BIN files on a UNIX command line or from within a shell script. In Windows, you can execute the BIN files with Cygwin. The BIN files are equivalent to the Windows Installer merge modules described in the section "About merge modules" on page 19. If you do not use the BIN files, you can create a customized installer using the raw filesets in the sdk_root/filesets directory. BIN file list The following table describes the binary modules: BIN file Core Default JRun server jikes JRun Management Console File name JRun4Core.bin JRun4DefaultServer.bin JRun4Jikes.bin JRun4JMC.bin Description (Required) Includes the basic files to run JRun and serve J2EE applications. Also includes the migration tool, XMLScript, and the JSPC compiler. (Optional) Includes all files used by the default JRun server. (Optional) Includes the JSP compiler. If your web application does not use JSPs or if you precompile your JSPs, the Jikes.msm module is not required. (Optional) Includes the JMC EAR file and the admin JRun server. The JMC provides access to JRun settings through a web-based GUI. 28 Chapter 4 Platform-Independent JRun Installers

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
28
Chapter 4
Platform-Independent JRun Installers
About files for custom installations
The JRun SDK includes the following groups of files that you can use to create custom
JRun installers on any supported platform:
•
BIN files
Prebuilt binary files that you can use across platforms, separated into
functional components.
•
filesets
Raw filesets of the JRun installation. For a complete description of the
contents of this directory, see
“JRun components” on page 5
.
•
Merge modules
Windows Installer merge modules for Windows Installers only.
For information, see
Chapter 3, “Windows JRun Installers” on page 17
.
This section focuses on using the BIN files to build custom installers.
Using BIN files
The JRun SDK includes the JRun modules as binary (BIN) files. Based on your license
agreement, you can access some or all of these modules. The BIN files are in the
sdk_root
/installers/unix directory.
You can use the BIN files to create a JRun installer with either a GUI installer tool, such
as InstallAnywhere, or a shell script. You can import these BIN files into any compatible
installer development environment. You can also execute BIN files on a UNIX command
line or from within a shell script. In Windows, you can execute the BIN files with
Cygwin.
The BIN files are equivalent to the Windows Installer merge modules described in the
section
“About merge modules” on page 19
.
If you do not use the BIN files, you can create a customized installer using the raw filesets
in the
sdk_root
/filesets directory.
BIN file list
The following table describes the binary modules:
BIN file
File name
Description
Core
JRun4Core.bin
(Required) Includes the basic files to run
JRun and serve J2EE applications. Also
includes the migration tool, XMLScript,
and the JSPC compiler.
Default JRun
server
JRun4DefaultServer.bin
(Optional) Includes all files used by the
default JRun server.
jikes
JRun4Jikes.bin
(Optional) Includes the JSP compiler. If
your web application does not use JSPs
or if you precompile your JSPs, the
Jikes.msm module is not required.
JRun
Management
Console
JRun4JMC.bin
(Optional) Includes the JMC EAR file and
the admin JRun server. The JMC
provides access to JRun settings through
a web-based GUI.