Ideally we would have an ohs with mod_plsql, like before, which worked
wonderfully. Just lie we used to be able to run PHP with ohs, but not
that's been scuttled.
After folloiwng the documentation, at 1.5.7 to verify that it works
(wasn't, ords appeared as Prepared not Active), I see this:
weblogic.application.ModuleException:
oracle.dbtools.common.config.dir.NotSpecifiedException: No value for the
config.dir setting was found. Before deploying ords please configure the
config.dir setting using the configdir command, for example: java -jar
Oracle REST Data Services configdir
/path/to/configuration/folder:oracle.dbtools.common.config.dir.NotSpecifiedException:No
value for the config.dir setting was found. Before deploying ords please
configure the config.dir setting using the configdir command, for example:
java -jar Oracle REST Data Services configdir /path/to/configuration/folder
1.5.5 starts (again!) with
Tip: The Oracle REST Data Services files, ords.war and i.war, must be
available before you start this task.
Higher up they say you don't need i.war if not using APEX:
1.5.3 [...] if you are not using Oracle Application Express, you may skip
the rest of this section about configuring Oracle Application Express
images.
I wonder who reviewed the documentation, it seems to have been thrown
together for a previous version, but not reorganized since. I know
documentation is a bit of a pain though. Maybe it ought to be broken up
into separate sections or chapters: stripped down mod_plsql / webDB / HTML
DB functionality, REST services for the savvy people who are up-to-date,
and finally APEX environment for environments running useful APEX apps.
Pat.
On Thu, May 11, 2017 at 11:30 AM, Jeff Smith <jeff.d.smith@xxxxxxxxxx>
wrote:
If you are using Oracle Application Express
That sounds about right to me. IF. Most folks installing ORDS today
probaby are using it with APEX. I’m taking tons of calls from customers
wanting it for pure REST development though, so I feel the percentage
breakdown on that changing almost every day.
Otherwise, are you asking for a WLS dist that includes ORDs?
*From:* Patrice sur GMail [mailto:patrice.boivin@xxxxxxxxx]
*Sent:* Thursday, May 11, 2017 10:20 AM
*To:* ORACLE-L <oracle-l@xxxxxxxxxxxxx>
*Subject:* ORDS documentation feedback submitted
I left feedback, they updated REST services but the documentation still
pretends or assumes people want to deploy APEX. check out 1.5.3:
http://docs.oracle.com/cd/E56351_01/doc.30/e56293/
installing-REST-data-services.htm#AELIG7184
Here we only use APEX on one server, we don't intend or want to deploy it
on every middleware server. We only want mod_plsql functionality from one
of our FM12c FR servers.
Besides, why would there even be an "Administration Server" for something
deployed in WLS which has its own interface (EM and WLS Console) when REST
and ORDS are made by Oracle which owns WLS as well. Why wouldn't these two
products work together "out of the box"? We could tick a checkbox during
installation, and it could be installed flawlessly to work with ohs and WLS.
Maybe that seems simpler to me than it is in real life though. I'm just a
customer.
-- Patrice
My profiles: [image: Facebook]
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_home.php-3F-23-21_profile.php-3Fid-3D100000206805521&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=Z7TxYgTRa8b2Qmi2Gp6fvdZIJHBIir8RWfL4YTvXYOM&m=95vboP2OVHd-Lo2ebcgGhcm-bGvIaogWCOuoHQ24Xag&s=Lv5wb2HfKq4NECE1q06TCHEtx1qLTKy8nc4eLXi3iNU&e=>[image:
LinkedIn]
<https://urldefense.proofpoint.com/v2/url?u=http-3A__ca.linkedin.com_pub_patrice-2Dboivin_a_933_5a9&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=Z7TxYgTRa8b2Qmi2Gp6fvdZIJHBIir8RWfL4YTvXYOM&m=95vboP2OVHd-Lo2ebcgGhcm-bGvIaogWCOuoHQ24Xag&s=8OiXGIqt4-YUdgYvfYppK7G1GyAkbsGGZcFtoQfMmfg&e=>[image:
Twitter]
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_PatriceBoivin&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=Z7TxYgTRa8b2Qmi2Gp6fvdZIJHBIir8RWfL4YTvXYOM&m=95vboP2OVHd-Lo2ebcgGhcm-bGvIaogWCOuoHQ24Xag&s=obdN6eN8YNu_TT6KlWjlujorR8Qz-rb0w0AG1Swh8dw&e=>
