Hello Mr. Ady. warm regards too from Bandung.

you say you have already set the oai.url to localhost, but what i mean is
the SOLR that should be set to localhost, not the oai.url. Oai.url must be
set to dspace baseUrl that have been configured in dpace.cfg

here is my oai configuration, i hope this help you

#---------------------------------------------------------------#
#--------------------XOAI CONFIGURATIONS------------------------#
#---------------------------------------------------------------#
# These configs are used by the XOAI                            #
#---------------------------------------------------------------#

# Storage: solr | database
storage=solr

# Base solr index, keep in localhost because its the setting
solr.url = http://localhost:8080/solr/oai
# OAI persistent identifier prefix.
# Format - oai:PREFIX:HANDLE
identifier.prefix = repository.widyatama.ac.id
# Base url for bitstreams
bitstream.baseUrl = http://repository.widyatama.ac.id:8080/xmlui

# Base Configuration Directory
config.dir = /opt/dspace/config/crosswalks/oai

# Cache enabled?
cache.enabled = false

# Base Cache Directory
cache.dir = /opt/dspace/var/oai

# OAI base URL, added by Esa
oai.dspace.url = http://repository.widyatama.ac.id:8080/xmlui

#---------------------------------------------------------------#
#--------------OAI HARVESTING CONFIGURATIONS--------------------#
#---------------------------------------------------------------#
# These configs are only used by the OAI-ORE related functions  #
#---------------------------------------------------------------#

### Harvester settings

# Crosswalk settings; the {name} value must correspond to a declated
ingestion crosswalk
# harvester.oai.metadataformats.{name} = {namespace},{optional display name}
# The display name is only used in the xmlui for the jspui there are
entries in the
# Messages.properties in the form
jsp.tools.edit-collection.form.label21.select.{name}
harvester.oai.metadataformats.dc =
http://www.openarchives.org/OAI/2.0/oai_dc/, Simple Dublin Core
harvester.oai.metadataformats.qdc = http://purl.org/dc/terms/, Qualified
Dublin Core
harvester.oai.metadataformats.dim = http://www.dspace.org/xmlns/dspace/dim,
DSpace Intermediate Metadata

# This field works in much the same way as
harvester.oai.metadataformats.PluginName
# The {name} must correspond to a declared ingestion crosswalk, while the
# {namespace} must be supported by the target OAI-PMH provider when
harvesting content.
# harvester.oai.oreSerializationFormat.{name} = {namespace}
harvester.oai.oreSerializationFormat.ore = http://www.w3.org/2005/Atom

# Determines whether the harvester scheduling process should be started
# automatically when the DSpace webapp is deployed.
# default: false
harvester.autoStart=false

# Amount of time subtracted from the from argument of the PMH request to
account
# for the time taken to negotiate a connection. Measured in seconds.
Default value is 120.
#harvester.timePadding = 120

# How frequently the harvest scheduler checks the remote provider for
updates,
# messured in minutes. The default vaule is 12 hours (or 720 minutes)
#harvester.harvestFrequency = 720

# The heartbeat is the frequency at which the harvest scheduler queries the
local
# database to determine if any collections are due for a harvest cycle
(based on
# the harvestFrequency) value. The scheduler is optimized to then sleep
until the
# next collection is actually ready to be harvested. The minHeartbeat and
# maxHeartbeat are the lower and upper bounds on this timeframe. Measured
in seconds.
# Default minHeartbeat is 30.  Default maxHeartbeat is 3600.
#harvester.minHeartbeat = 30
#harvester.maxHeartbeat = 3600

# How many harvest process threads the scheduler can spool up at once.
Default value is 3.
#harvester.maxThreads = 3

# How much time passess before a harvest thread is terminated. The
termination process
# waits for the current item to complete ingest and saves progress made up
to that point.
# Measured in hours. Default value is 24.
#harvester.threadTimeout = 24

# When harvesting an item that contains an unknown schema or field within a
schema what
# should the harvester do? Either add a new registry item for the field or
schema, ignore
# the specific field or schema (importing everything else about the item),
or fail with
# an error. The default value if undefined is: fail.
# Possible values: 'fail', 'add', or 'ignore'
harvester.unknownField  = add
harvester.unknownSchema = fail

# The webapp responsible for minting the URIs for ORE Resource Maps.
# If using oai, the dspace.oai.uri config value must be set.
# The URIs generated for ORE ReMs follow the following convention for both
cases.
# format: [baseURI]/metadata/handle/[theHandle]/ore.xml
# Default value is oai
ore.authoritative.source = xmlui

# A harvest process will attempt to scan the metadata of the incoming items
# (dc.identifier.uri field, to be exact) to see if it looks like a handle.
# If so, it matches the pattern against the values of this parameter.
# If there is a match the new item is assigned the handle from the metadata
value
# instead of minting a new one. Default value: hdl.handle.net
#harvester.acceptedHandleServer = hdl.handle.net, handle.myu.edu
harvester.acceptedHandleServer = hdl.handle.net, handle.myu.edu

# Pattern to reject as an invalid handle prefix (known test string, for
example)
# when attempting to find the handle of harvested items. If there is a
match with
# this config parameter, a new handle will be minted instead. Default
value: 123456789.
#harvester.rejectedHandlePrefix = 123456789, myTestHandle


2013/5/31 ady [via DSpace] <[email protected]>

> Hi Esa,
> thank you for the hint, but i already set the oai.url to localhost yet the
> problem remain.
> i haven't try the cache thing though... i'll give it a shot
>
> warm regards from makassar,
> adywp
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://dspace.2283337.n4.nabble.com/forbidden-oai-import-tp4664487p4664517.html
>  To unsubscribe from forbidden oai import, click 
> here<http://dspace.2283337.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4664487&code=ZXNhLmZhdXppQGdtYWlsLmNvbXw0NjY0NDg3fDE5MjIwODIyMDU=>
> .
> NAML<http://dspace.2283337.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
Thanks,


Esa Fauzi




--
View this message in context: 
http://dspace.2283337.n4.nabble.com/forbidden-oai-import-tp4664487p4664551.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to