[mule-scm] [mule] [12404] branches/mule-2.0.x/distributions/server/src/main/resources: Update README.txt with updated content

[dfeist]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Revision

12404

Author

dfeist

Date

2008-07-23 19:40:32 -0500 (Wed, 23 Jul 2008)

Log Message

Update README.txt with updated content

Modified Paths

• branches/mule-2.0.x/distributions/server/src/main/resources/README.txt

Removed Paths

• branches/mule-2.0.x/distributions/server/src/main/resources/INSTALL.txt

Diff

Deleted: branches/mule-2.0.x/distributions/server/src/main/resources/INSTALL.txt (12403 => 12404)

--- branches/mule-2.0.x/distributions/server/src/main/resources/INSTALL.txt	2008-07-23 13:35:56 UTC (rev 12403)
+++ branches/mule-2.0.x/distributions/server/src/main/resources/INSTALL.txt	2008-07-24 00:40:32 UTC (rev 12404)
@@ -1,94 +0,0 @@
-+----------------------------+
-|      Welcome to Mule!      |
-|----------------------------|
-| http://mule.mulesource.org |
-+----------------------------+
-Mule is a highly scalable Enterprise Services framework and messaging broker.
-Here is some useful information to get you started.
-
-+--------------+
-| INSTALLATION |
-+--------------+
-If you're reading this, it means you've already downloaded and unpacked the 
-distribution.  The only other thing you need to do to get started using Mule is 
-to set the location of your Mule installation and add it to your path.  This 
-will depend on your platform, but is usually something like the following:
-
-Linux / Unix
-------------
-export MULE_HOME=/opt/mule
-export PATH=$PATH:$MULE_HOME/bin
-
-Windows
--------
-set MULE_HOME=C:\Mule
-set PATH=%PATH%;%MULE_HOME%\bin
-
-(or by using the System utility in the Control Panel for Windows NT/2000/XP)
-
-+----------------------+
-| ADDITIONAL LIBRARIES |
-+----------------------+
-Mule has connectors for a wide variety of technologies, however in some cases in 
-order to actually use the connector, libraries are required which cannot be 
-distributed as part of Mule due to licensing restrictions.  In these cases it is 
-up to the user to obtain the needed libraries and place them in the 
-$MULE_HOME/lib/user directory.
-
-As a convenience, the very first time Mule is started, it will try to download 
-Sun Microsystems' javax.mail, javax.activation, and jsr223 (scripting) 
-libraries.  If you are behind a firewall, you may need to configure your HTTP 
-proxy settings in the file $MULE_HOME/conf/wrapper.conf in order for this 
-download to work.
-
-+--------------+
-| DISTRIBUTION |
-+--------------+
-The distribution you have downloaded contains the following:
-
-./bin          - Shell and batch scripts for controlling Mule from the command 
-                 line
-./conf         - Configuration files
-./docs         - API documentation (javadoc) for Mule and its sub-projects
-./examples     - Example applications you can run and try building yourself
-./lib/boot     - Libraries used by the Java Service Wrapper to boot up the 
-                 server
-./lib/mule     - Mule libraries
-./lib/native   - Platform-specific (non-Java) libraries
-./lib/opt      - Non-Mule libraries
-./lib/user     - This is where you should place your custom classes/libraries.
-                 This directory comes before ./lib/mule on the classpath and can
-                 therefore be used to patch the distributed Mule classes if 
-                 necessary.
-./licences     - License information for all libraries shipped with Mule
-./logs         - Output will be sent here by default when running in background 
-                 mode
-./src          - An export of the Mule source code, useful for importing into 
-                 your IDE
-./INSTALL.txt  - erm... this file!
-./LICENSE.txt  - License agreement for Mule
-./USAGE.txt    - Basic usage of Mule from the command-line
-
-+-----------------+
-| GETTING STARTED |
-+-----------------+
-Take a look at the latest documentation on our website:
-http://www.muledocs.org/Getting+Started+Guide
-
-User Guide:
-http://www.muledocs.org/User+Guide
-
-Example Applications:
-http://www.muledocs.org/Examples
-
-+----------+
-| FEEDBACK |
-+----------+
-We hope you enjoy using Mule. To help us make it a better product please tell
-us about any issues (no matter how small), suggestions or other comments you 
-have.  You can post on the Mule User's mailing list - user@... or 
-raise issues at http://mule.mulesource.org/jira/browse/MULE
-
-Enjoy!
-The Mule Team
-

Modified: branches/mule-2.0.x/distributions/server/src/main/resources/README.txt (12403 => 12404)

--- branches/mule-2.0.x/distributions/server/src/main/resources/README.txt	2008-07-23 13:35:56 UTC (rev 12403)
+++ branches/mule-2.0.x/distributions/server/src/main/resources/README.txt	2008-07-24 00:40:32 UTC (rev 12404)
@@ -1,9 +1,9 @@
 GETTING STARTED WITH MULE
 =========================
 
-This file describes how to get started using Mule. For full details,
-see the Mule User Guide at:
-http://mule.mulesource.org/display/MULE2USER/Home
+This file describes the basics of how to get started using Mule. 
+For full deta ils,see the Mule Getting Started Guide at:
+http://www.mulesource.org/display/MULE2INTRO/Home
 
 
 Setting Up Your Environment
@@ -44,7 +44,7 @@
 /lib/user       Your custom classes and libraries. This directory comes before
                 /lib/mule on the classpath and can be used to patch the distributed 
                 Mule classes. You must restart Mule after adding files to this directory.
-/licences       License information for all libraries shipped with Mule
+/licenses       License information for all libraries shipped with Mule
 /logs           Log file output when running in background mode
 /sbin           Internal scripts (not to be run by the user)
 /src            The source code for all Mule modules
@@ -67,7 +67,7 @@
 provides you with several examples of Mule applications including
 their configuration files, which you can use as the starting point
 for creating your configuration file. For more information,
-see http://mule.mulesource.org/display/MULEINTRO/Examples.
+see http://www.mulesource.org/display/MULE2INTRO/Examples.
 
 
 Working with Configuration Files
@@ -105,145 +105,25 @@
 Additional Setup for Community Edition Users
 --------------------------------------------
 
-If you are running Mule Community Edition, you take a few extra
-steps before you can use Mule.
+If you are running Mule Community Edition, the MuleSource Public
+License is displayed page by page when you start Mule for the first time. 
+To advance a page, press Enter. At the end of the license display, 
+type y to accept the license file and proceed with startup.
 
-- License Display and Acceptance
 
-When you start Mule for the first time, the MuleSource Public
-License is displayed page by page. To advance a page, press Enter.
-At the end of the license display, type y to accept the license
-file and proceed with startup.
-
-
-Testing the Installation
-------------------------
-
-After Mule has started successfully, it displays "Mule Server 
-initialized." The default port for the Mule AdminAgent is 60504.
-To test the connection, open another window and type the following
-command to search for port 60504:
-
-Windows Console:    netstat -an|find "60504"
-Unix Command Shell: netstat -an|grep 60504
-
-
-Basic Usage
-===========
-
-There are three general types of tasks you can perform to configure
-and customize your Mule deployment:
-
-- Service component development: developing POJOs, services, or beans
-that contain the business logic and will be used as service components
-in a Mule deployment.
-
-- Integration: developing routers, transformers, and filters, and configuring
-everything in the Mule configuration file.
-
-- Extending Mule: developing new transports, connectors, and other modules
-used by Mule.
-
-This section provides a high-level overview of the steps you take to
-perform these tasks.
-
-
-Create a Service Component
---------------------------
-
-A service component is a class, web service, or other application that
-contains the business logic you want to plug in to the Mule framework.
-You can use any existing application, or create a new one. Your service
-component does not need to contain any Mule-specific code. All the
-Mule-specific instructions will be configured for the service that
-wraps the service component.
-
-To assist development, you can use the Mule IDE, an Eclipse plug-in
-that provides an integrated development environment for developing
-Mule applications. You can download the Mule IDE from the MuleForge at:
-http://www.mulesource.org/display/IDE/Home
-
-If you want more advanced information on writing service components,
-see: http://mule.mulesource.org/display/MULE2USER/Working+with+Services
-
-
-Configure the Service
----------------------
-
-You create a service definition in the Mule configuration file that
-points to the service component, routers, filters, and transformers.
-It also specifies the endpoint on which this service will receive
-messages and the outbound endpoint where messages will go next.
-For more information, see:
-http://mule.mulesource.org/display/MULE2USER/Configuring+the+Service
-
-Following is more information on configuring routers, filters,
-and transformers for the service.
-
-- Routers
-
-Inbound routers specify how messages are routed to a service,
-and outbound routers specify how messages are routed after the
-service has finished processing them. There are several default
-routers that come with Mule that you can use, or you can create
-your own routers. For more information, see:
-http://mule.mulesource.org/display/MULE2USER/Using+Message+Routers
-
-- Filters
-
-Filters specify conditions that must be met for a message to be
-routed to a service. There are several default filters that come
-with Mule that you can use, or you can create your own filters.
-For more information, see:
-http://mule.mulesource.org/display/MULE2USER/Using+Filters
-
-- Transformers
-
-Transformers convert incoming payload data to the type required
-by the service component. After the service has finished processing
-the message, they can also convert the message to a different type
-as needed by the outbound transport. There are several default
-transformers you can use, or create your own. For more information, see:
-http://mule.mulesource.org/display/MULE2USER/Using+Transformers
-
-
-Configure Mule
---------------
-
-Each Mule instance has one Registry. The Registry acts as a
-runtime registry of all the Mule components, including models, agents,
-connectors, endpoints, and transformers. You configure the server URL
-for the Mule instance, the working directory where it writes temporary
-files, and more. For more information, see:
-http://mule.mulesource.org/display/MULE2USER/Configuration+Overview
-
-
-Extend Mule
------------
-
-Mule provides transports for many different channels, including File,
-FTP, HTTP, JMS, JDBC, Quartz, and many more. There are also community-
-created transports on MuleForge (http://muleforge.org/). If you need
-to send messages on a channel other than those provided, you can
-create a new transport. You can also create a custom connector for
-a transport. A connector is the Java class in the transport that
-contains the actual logic for sending and receiving messages on
-that channel. For more information, see:
-http://mule.mulesource.org/display/MULE2USER/About+Transports
-
-For information on using the Mule project wizard to create new
-Mule projects (transports and other types of modules), see:
-http://mule.mulesource.org/display/MULE2USER/Tools
-
-
 Where Do I Go Next?
 ===================
 
 This document has provided a brief overview of getting started
 with Mule. Following is information about where to go next.
 
+- For information on more ways to run Mule and how to get started using
+the examples, go to the Getting Started Guide at: 
+http://www.mulesource.org/display/MULE2INTRO/Home 
+
 - For complete information on using Mule, go to the Mule User Guide at:
-http://www.mulesource.org/display/MULE2USER/Home.
+http://www.mulesource.org/display/MULE2USER/Home. You will need to register
+to view these pages, but registration is free and only takes a few moments.
 
 - If you need assistance and are a Mule Enterprise customer,
 see the support page at: http://www.mulesource.org/display/MULE/Support
@@ -257,4 +137,4 @@
 
 - If you experience problems with the Mule software or documentation,
 please log an issue in the MuleSource issue-tracking system, located at:
-http://mule.mulesource.org/jira/browse/MULE
+http://mule.mulesource.org/jira/browse/MULE
\ No newline at end of file

---

To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email