Status: AVAILABLE |
In order to read or download dspace manual 3.1 ebook, you need to create a FREE account.
Download Now! |
eBook includes PDF, ePub and Kindle version
| ✔ Register a free 1 month Trial Account. |
| ✔ Download as many books as you like (Personal use) |
| ✔ Cancel the membership at any time if not satisfied. |
| ✔ Join Over 80000 Happy Readers |
SCALEXIO and PHS systems combined in a test factory for powertrain ECUsTests for autonomous driving based on SOTIFThe dSPACE simulation solution features an easy definition of complex, realistic traffic scenarios on real.Learn how the established hardware-in-the-loop test systems from dSPACE and a fuel cell model can support.Environment sensors, buses, and networks in autonomous vehicles can generate tens of terabytes of raw data.The ModelDesk Vehicle Configurator supports an easy basic parameterization of the ASM vehicle dynamics.Completely revised modeling guidelines for development with the dSPACE production code generator TargetLink September 24-25, 2020, Berlin, GermanyA new video podcast series with episodes covering a wide variety of topics related to embedded software.Through the acquisition of Intempora, dSPACE offers a unique, comprehensive, and reliable end-to-end.The documentation for successive TargetLink Releases already comprises these information. SCALEXIO and PHS systems combined in a test factory for powertrain ECUsTests for autonomous driving based on SOTIFThe dSPACE simulation solution features an easy definition of complex, realistic traffic scenarios on real.Learn how the established hardware-in-the-loop test systems from dSPACE and a fuel cell model can support.Environment sensors, buses, and networks in autonomous vehicles can generate tens of terabytes of raw data.The ModelDesk Vehicle Configurator supports an easy basic parameterization of the ASM vehicle dynamics.Completely revised modeling guidelines for development with the dSPACE production code generator TargetLink A new video podcast series with episodes covering a wide variety of topics related to embedded software.Through the acquisition of Intempora, dSPACE offers a unique, comprehensive, and reliable end-to-end.In an interview, dSPACE CEO Martin. See all documentation.
http://fishingas.com/userfiles/9505a-user-manual.xml
Only experienced unix admins should even attempt the following without going to the detailed Installation Instructions However, if you intend to run DSpace for a large community of potential end users, carefully review the Hardware Recommendations in the User FAQ Prerequisite Software The list below describes the third-party components and tools you'll need to run a DSpace server. These are just guidelines. Since DSpace is built on open source, standards-based tools, there are numerous other possibilities and setups. Also, please note that the configuration and installation guidelines relating to a particular tool below are here for convenience. You should refer to the documentation for each individual component for complete and up-to-date details. Many of the tools are updated on a frequent basis, and the guidelines below may become out of date. You should consult your particular distribution's documentation or local system administrators to determine what is already available. Microsoft Windows: After verifying all prerequisites below, see the Windows Installation section for Windows tailored instructions Java JDK 7 or 8 (OpenJDK or Oracle JDK) OpenJDK download and installation instructions can be found here. Most operating systems provide an easy path to install OpenJDK. Just be sure to install the full JDK (development kit), and not the JRE (which is often the default example). Oracle's Java can be downloaded from the following location. Make sure to download the appropriate version of the Java SE JDK. Make sure to install the JDK and not just the JRE At this time, DSpace requires the full JDK (Java Development Kit) be installed, rather than just the JRE (Java Runtime Environment). So, please be sure that you are installing the full JDK and not just the JRE. Be aware that Tomcat 7 uses Java 1.6 to compile JSPs by default. See information about Tomcat below on how to configure it to use Java 1.7 for JSPs. Tomcat 8 uses Java 1.7 for JSPs by default.
http://www.met-axa.ro/img/uploads/9505a-satellite-phone-manual.xml
If you use another Servlet Container please refer to its documentation on this matter. Only Oracle’s Java and the OpenJDK are supported. We recommend installing the Java 8 update 20 or later, or Java 7 update 55 or later. If you will be building the Mirage 2 theme, you will need Maven 3.3.9 or above (see DS-2458 for details as to why). Maven can be downloaded from the following location: Configuring a Proxy You can configure a proxy to use for some or all of your HTTP requests in Maven.PostgreSQL can be downloaded from. It is also provided via many operating system package managers If the version of Postgres provided by your package manager is outdated, you may wish to use one of the official PostgreSQL provided repositories: Linux users can select their OS of choice for detailed instructions on using the official PostgreSQL apt or yum repository: Windows users will need to use the windows installer: Mac OSX users can choose their preferred installation method: Install the pgcrypto extension. It will also need to be enabled on your DSpace Database (see Installation instructions below for more info). This is the default, in recent PostgreSQL releases, but you should at least check it.Then restart PostgreSQL. Oracle 10g or later Details on acquiring Oracle can be downloaded from the following location. You will need to create a database for DSpace. Make sure that the character set is one of the Unicode character sets. DSpace uses UTF-8 natively, and it is suggested that the Oracle database use the same character set. You will also need to create a user account for DSpace (e.g. dspace ) and ensure that it has permissions to add and remove tables in the database. Refer to the Quick Installation for more details. NOTE: If the database server is not on the same machine as DSpace, you must install the Oracle client to the DSpace server and point tnsnames.ora and listener.ora files to the database the Oracle server.
https://congviendisan.vn/vi/bose-freespace-51-manual
For people interested in switching from PostgreSQL to Oracle (or visa versa), you may be able to inves Servlet Engine (Apache Tomcat 7 or later, Jetty, Caucho Resin or equivalent) Tomcat 8 Version Tomcat 8.0.32 (found e.g. in Debian 9 Stretch and Ubuntu 16.04 Xenial ) has a bug which will cause PropertyBatchUpdateException or StringIndexOutOfBoundsException. This was fixed in 8.0.33. More information can be found in DS-3142. Tomcat 7 Version If you are using Tomcat 7, we recommend running Tomcat 7.0.30 or above. Tomcat 7.0.29 and lower versions suffer from a memory leak. As a result, those versions of tomcat require an unusual high amount of memory to run DSpace. This has been resolved as of Tomcat 7.0.30. More information can be found in DS-1553 Apache Tomcat 7 or later. Tomcat can be downloaded from the following location. This option may be more desireable if you have multiple Tomcat instances running, and you do not want all of them to run under the same Tomcat owner. You need to ensure that Tomcat has a) enough memory to run DSpace and b) uses UTF-8 as its default file encoding for international character support.If you want to use Java 1.7 in your.jsp files, you have to change the configuration of Tomcat 7. Look for a servlet definition using the org.apache.jasper.servlet.JSPServlet servlet-class and add two init parameters compilerSourceVM and compilerTargetVM as you see it in the example below.Jetty and Resin are configured for correct handling of UTF-8 by default. We are working on a solution within this ticket: In a nutshell, the binary release build will download pre-compiled parts of DSpace, while the building the source release will compile most of DSpace's source code on your local machine.
https://www.dermatina100.gr/images/campus-t1-pairgain-manual.pdf
It's important to notice that both releases will require outgoing internet connections on the machine or server where you are executing the build, because maven needs to download 3rd party dependencies that are not even included in the DSpace source release distribution. Binary Release (dspace- -release.zip) This distribution will be adequate for most cases of running a DSpace instance. It is intended to be the quickest way to get DSpace installed and running while still allowing for customization of the themes and branding of your DSpace instance. This approach only exposes selected parts of the application for customization. Provides all the same capabilities as the binary release. This is the location where DSpace is installed and running. This is the location where the DSpace release distribution has been unpacked. It usually has the name of the archive that you expanded such as dspace - - release or dspace - - src - release. The web deployment directory. Installation This method gets you up and running with DSpace quickly and easily. It is identical in both the Default Release and Source Release distributions. Create the DSpace user (optional).There are two version available with each release of DSpace: ( dspace-n.x-release. and dspace-n.x-src-release.zip ); you only need to choose one. If you want a copy of all underlying Java source code, you should download the dspace-n.x-src-release.zip. Within each version, you have a choice of compressed file format. Choose the one that best fits your environment. Alternatively, you may choose to check out the latest release from the DSpace GitHub Repository. In this case, you'd be checking out the full Java source code. After downloading the software, based on the compression file format, choose one of the following methods to unpack your software: Zip file. If you downloaded dspace-6.x-release.zip do the following: You no longer need to copy any PostgreSQL jars to get PostgreSQL installed.
This is entirely separate from the dspace operating-system user created above: Then you'll be prompted for the password of the PostgreSQL superuser ( postgres ). Create a dspace database, owned by the dspace PostgreSQL user.Finally, you MUST enable the pgcrypto extension on your new dspace database. If it fails or throws an error, it is likely you are missing the required pgcrypto extension (see Database Prerequisites above). Alternative method: How to enable pgcrypto via a separate database schema. While the above method of enabling pgcrypto is perfectly fine for the majority of users, there may be some scenarios where a database administrator would prefer to install extensions into a database schema that is separate from the DSpace tables. If you wish to install pgcrypto in a separate schema here's how to do that. CREATE SCHEMA extensions. CREATE EXTENSION pgcrypto SCHEMA extensions. GRANT USAGE ON SCHEMA extensions TO dspace;You will need still need to get a copy of the Oracle JDBC driver, but instead of copying it into a lib directory you will need to install it into your local Maven repository. (You'll need to download it first from this location:.) Run the following command (all on one line): Make sure that the character set is one of the Unicode character sets. DSpace uses UTF-8 natively, and it is required that the Oracle database use the same character set. Create a user account for DSpace (e.g. dspace ) and ensure that it has permissions to add and remove tables in the database. It provides a good starting point for your own local.cfg file. However, you should be aware that ANY configuration can now be copied into your local.cfg to override the default settings. See the Configuration Reference section for more details.The Mirage 2 build requires git to be installed on your server. Install git before attempting the Mirage 2 build. It must be run as a non-root user.See the Common Problems Section below for more details.
Decide which DSpace Web Applications you want to install. It comes with a variety of out-of-the-box themes, including Mirage 1 (the default) and Mirage 2 (based on Bootstrap ). More info on SWORD protocol and its usage. Deploy Web Applications: Please note that in the first instance you should refer to the appropriate documentation for your Web Server of choice. The following instructions are meant as a handy guide.We just recommend beginning with them, so that you can more easily customize your site without having to require a Tomcat restart. Smaller DSpace sites may not notice any performance issues with keeping these settings in place in Production. Larger DSpace sites may wish to ensure that Tomcat performance is more streamlined. Technique B. Simple and complete. Administrator Account: Create an initial administrator account from the command line: Visit the base URL(s) of your server, depending on which DSpace web applications you want to use. You should see the DSpace home page. Congratulations! Base URLs of DSpace Web Applications: JSP User Interface - (e.g.) Manakin) - (e.g.) According to the languages you wish to support, you have to make sure that all the i18n related files are available. See the Configuring Multilingual Support section for the JSPUI or the Multilingual Support for XMLUI in the configuration documentation. DSpace over HTTPS If your DSpace is configured to have users login with a username and password (as opposed to, say, client Web certificates), then you should consider using HTTPS. This is a very serious security risk since network traffic monitoring is very common, especially at universities. If the risk seems minor, then consider that your DSpace administrators also login this way and they have ultimate control over the archive. The solution is to use HTTPS (HTTP over SSL, i.e. Secure Socket Layer, an encrypted transport), which protects your passwords against being captured.
The following sections show how to set up the most commonly-used Java Servlet containers to support HTTP over SSL. For Production use: Follow this procedure to set up SSL on your server. This assumes the certificate was put in the file server.pem: This assumes the server CA certificate is in ca.pem: For example, assuming the client CA certificate is in client1.pem: The parts affecting or specific to SSL are shown in bold. (You may wish to change some details such as the port, pathnames, and keystore password) When generating your key, give the Distinguished Name fields the appropriate values for your server and institution. CN should be the fully-qualified domain name of your server host. Here is an example: Since you now have a signed server certificate in your keystore you can, obviously, skip the next steps of installing a signed server certificate and the server CA's certificate. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in client1.pem: Once DSpace is running, you can use the below instructions to add Apache HTTP Server in front of Tomcat in order to allow DSpace to run on port 80 and optionally port 443 (for SSL). One of the easiest routes to both running DSpace on standard ports (80 and 443) as well as using HTTPS is to install Apache HTTP Server as your primary HTTP server, and use it to forward requests to Tomcat. Install Apache HTTP Server alongside your Tomcat instance In your Tomcat's server.xml, ensure that the AJP Connector is UNCOMMENTED. Usually this runs on port 8009, but you can decide to change the port if you desire You'll then need to restart Apache HTTP Server Create a new Virtual Host in Apache HTTP Server to represent your DSpace site.Here's a basic example.By default this usually is 8009)Finally, restart your Apache HTTP Server and test things out.
DSpace does not require any unique configurations with regards to this redirection from Apache to Tomcat. So, any guides that generally explain how to redirect requests from Apache to Tomcat should also work for DSpace. The Handle Server First a few facts to clear up some common misconceptions: You don't have to use CNRI's Handle system. At the moment, you need to change the code a little to use something else (e.g PURLs) but that should change soon. These aren't really Handles, since the global Handle system doesn't actually know about them, and lots of other DSpace test installs will have created the same IDs. They're only really Handles once you've registered a prefix with CNRI (see below) and have correctly set up the Handle server included in the DSpace distribution. This Handle server communicates with the rest of the global Handle infrastructure so that anyone that understands Handles can find the Handles your DSpace has created. If you want to use the Handle system, you'll need to set up a Handle server. One is included with DSpace. Note that this is not required in order to evaluate DSpace; you only need one if you are running a production service. You'll need to obtain a Handle prefix from the central CNRI Handle site. A Handle server runs as a separate process that receives TCP requests from other Handle servers, and issues resolution requests to a global server or servers if a Handle entered locally does not correspond to some local content. The Handle protocol is based on TCP, so it will need to be installed on a server that can send and receive TCP on port 2641. You can either use a Handle server running on the same machine as DSpace, or you can install it on a separate machine. Installing it on the same machine is a little bit easier. If you install it on a separate machine, you can use one Handle server for more than one DSpace installation.
To install your Handle resolver on the host where DSpace runs: We recommend configuring your Handle server without a passphrase, as the current DSpace start-handle-server scripts do not yet support startup with a passphrase.Once the configuration file has been generated, you will need to go to to upload the generated sitebndl.zip file. The upload page will ask you for your contact information. You will not be able to continue the handle server installation until you receive further information concerning your naming authority. Now start your handle server (as the dspace user): To install a Handle resolver on a separate machine: The Handle server you use must be dedicated to resolve Handles from DSpace. You cannot use a Handle server that is in use with other software already. You can use CNRI's Handle Software -- all you have to do is to add to it a plugin that is provided by DSpace. The following instructions were tested with CNRI's Handle software version 7.3.1. You can do the following steps on another machine than the machine DSpace runs on, but you have to copy some files from the machine on which DSpace is installed. Download the CNRI Handle Software. In the tarball you'll find an INSTALL.txt with installation instructions -- follow it. After installing the CNRI Handle Software you should have two directories: once that contains the CNRI software and one that contains the configuration of you local Handle Server. Select a release. You can get the source and build it yourself, or just use the JAR file included in the release. If you run more than one DSpace Installation, you may add more DSpace Endpoints. Just increase the number at the end of the key for each: endpoint2, endpoint3. It only resolves the handles of the DSpace Installations that were running when it was started. You may need to do this if you loaded items prior to CNRI registration (e.g. setting up a demonstration system prior to migrating it to production).
The script takes the current and new prefix as parameters. For example. Google and HTML sitemaps To aid web crawlers index the content within your repository, you can make use of sitemaps. There are currently two forms of sitemaps included in DSpace: Google sitemaps and HTML sitemaps. Sitemaps allow DSpace to expose its content without the crawlers having to index every page. HTML sitemaps provide a list of all items, collections and communities in HTML format, whilst Google sitemaps provide the same information in gzipped XML format. HTML sitemaps follow the same procedure: - Index HTML based sitemap etc. You can generate the sitemaps automatically every day using an additional cron job: Statistics DSpace uses the Apache Solr application underlaying the statistics. There is no need to download any separate software. All the necessary software is included. To understand all of the configuration property keys, the user should refer to DSpace Statistic Configuration for detailed information. External database connection pool Before it builds a pool of database connections, DSpace always tries to look up an existing, pre-configured pool in a directory service (if such a service is provided). Many web application containers supply such a service and can be configured to provide the connection pool to DSpace. If DSpace does not find a pre-configured pool, each web application will fall back to creating its own pool using the settings in local.cfg. There are some advantages to using an external database pool: You can share one pool among several of DSpace's web applications—or even all of them. This can help economize database connections when one application uses many and another few. For example, if XMLUI needs 30 connections to run well at your site under peak load and OAI-PMH needs 5, you could connect them both to a pool of 35 connections, instead of letting each take 30 for a total of 60.
You can have different pool sizes for the web applications and the command line tools. For example, configure an external pool with generous settings for the web applications, and a much smaller pool for the command line applications in local.cfg. Note: the command line tools cannot use an externally configured pool, and always use the settings in local.cfg to build their own pool. External database pooling often allows for more granular configuration of pool parameters and can even provide better performance than DSpace's fallback pooling (see the Tomcat JDBC Connection Pool documentation for more information). You must configure the name of the directory object provided to your web application context(s) to match this. See below for an example in Tomcat. An example in Tomcat First, you must make the JDBC driver for your database available to Tomcat. For example, the latest PostgreSQL JDBC driver can be downloaded from the PostgreSQL project website and placed in Tomcat's lib directory. Then add a in Tomcat's server.xml to define the pool. The pool name here is global and can be anything you want: server.xml See the JNDI Datasource HOW-TO for more information about this configuration. Windows Installation Essentially installing on Windows is the same as installing on Unix so please refer back to the main Installation Instructions section. Download the DSpace source from GitHub and unzip it ( WinZip will do this) If you install PostgreSQL, it's recommended to select to install the pgAdmin III tool. It provides a nice User Interface for interacting with PostgreSQL databases. Checking Your Installation The administrator needs to check the installation to make sure all components are working. Here is list of checks to be performed. In brackets after each item, it the associated component or components that might be the issue needing resolution. System is up and running. Known Bugs In any software project of the scale of DSpace, there will be bugs.
Sometimes, a stable version of DSpace includes known bugs. We do not always wait until every known bug is fixed before a release. If the software is sufficiently stable and an improvement on the previous release, and the bugs are minor and have known workarounds, we release it to enable the community to take advantage of those improvements. Please see the DSpace bug tracker for further information on current bugs, and to find out if the bug has subsequently been fixed. This is also where you can report any further bugs you find. Common Problems In an ideal world everyone would follow the above steps and have a fully functioning DSpace. Of course, in the real world it doesn't always seem to work out that way. This section lists common problems that people encounter when installing DSpace, and likely causes and fixes. This is likely to grow over time as we learn about users' experiences. If your error looks like this: Another common error looks like this: Another common message looks like this: General DSpace Issues Tomcat doesn't shut down: If you're trying to tweak Tomcat's configuration but nothing seems to make a difference to the error you're seeing, you might find that Tomcat hasn't been shutting down properly, perhaps because it's waiting for a stale connection to close gracefully which won't happen. If they stay around after running Tomcat's shutdown.sh script, trying running kill on them (or kill -9 if necessary), then starting Tomcat again. Database connections don't work, or accessing DSpace takes forever: If you find that when you try to access a DSpace Web page and your browser sits there connecting, or if the database connections fail, you might find that a 'zombie' database connection is hanging around preventing normal operation.If they're 'idle' it's OK; they're waiting to be used. However sometimes, if something went wrong, they might be stuck in the middle of a query, which seems to prevent other connections from operating, e.g.
: If this is the case, try running kill on the process, and stopping and restarting Tomcat. While DSpace's installation process continues to improve, it is still highly manual in nature.We have not yet seen much interest in other databases amongst our (volunteer) developer team. That said, if developers are interested in supporting other databases, we always do accept code contributions (from anyone). I'm not sure offhand if custom code would be required to support SQL Server or DB2. But, at the very least, custom database migrations (we use Flyway ) would likely be required, as we have to maintain those per Database type. You'll see those migrations in this folder: Is there another form to do this or I?m doing the wrong way? Evaluate Confluence today. Looking for another version. See all documentation. We recommend upgrading to a more recent version of DSpace. See DSpace Software Support Policy. Only experienced unix admins should even attempt the following without going to the detailed Installation Instructions These are just guidelines. Microsoft Windows: After verifying all prerequisites below, see the Windows Installation section for Windows tailored instructions Oracle Java JDK 6 (standard SDK is fine, you don't need J2EE) DSpace requires Oracle Java 6 (standard SDK is fine, you don't need J2EE). Please note, at this time, DSpace does not function properly with Java JDK 7 (see warning below). Again, you can just download the Java SE JDK version. Other flavors of Java may pose problems. Apache Maven 2.2.x or higher (Java build tool) DSpace 1.7.x requires usage of Maven 2.2.x DSpace 1.7.x required usage of Maven 2.2.x, as it did not build properly when using Maven 2.0.x or Maven 3.x. This was a known issue (see DS-788 ). However, DSpace 1.8.x resolved this issue so that DSpace now builds properly with Maven 2.2.x or above. Maven is necessary in the first stage of the build process to assemble the installation package for your DSpace instance.
It is highly recommended that you try to work with Postgres 8.4 or greater, however 8.3 should still work. Unicode (specifically UTF-8) support must be enabled. Oracle 10g or greater Details on acquiring Oracle can be downloaded from the following location. You will need to recreate the community, collection, and eperson structure in the Oracle system, and then use the item export and import tools to move your content over. Servlet Engine (Apache Tomcat 5.5 or 6, Jetty, Caucho Resin or equivalent) Apache Tomcat 5.5 or later. Tomcat can be downloaded from the following location. Note that DSpace will need to run as the same user as Tomcat, so you might want to install and run Tomcat as a user called ' dspace '. You need to ensure that Tomcat has a) enough memory to run DSpace and b) uses UTF-8 as its default file encoding for international character support.If you've used DSpace 1.4.x, please recognize that the initial build procedure has changed to allow for more customization. You will find the later 'Ant based' stages of the installation procedure familiar. Maven is used to resolve the dependencies of DSpace online from the 'Maven Central Repository' server. This is the location where the DSpace release distribution has been unzipped into. This is the directory that contains your DSpace web application(s). Create the DSpace user. This needs to be the same user that Tomcat (or Jetty etc.) will run as. e.g. as root run: If you want a copy of all underlying Java source code, you should download the dspace-1.x-src-release.xxx Within each version, you have a choice of compressed file format. Unpack the DSpace software. If you downloaded dspace-1.8-release.zip do the following: After unpacking the file, the user may which to change the ownership of the dspace-1.6-release to the 'dspace' user. (And you may need to change the group). Database Setup Also see notes above PostgreSQL: A PostgreSQL JDBC driver is configured as part of the default DSpace build.