[
https://issues.apache.org/jira/browse/OPENMEETINGS-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379269#comment-15379269
]
Ioannis Vlachos commented on OPENMEETINGS-1419:
-----------------------------------------------
Actually, the problem is right there in the connection string created. The web
installer always adds a semicolon (:) after the port (1521:/slashtest). In
order to be able to connect to oracle with Service Name, this semicolon should
not exist (it should be 1521/slashtest).
A possible solution (I don't know if it is easy) would be to check the string
entered in the "Specify the name of the database" field. If it starts with a
slash (/), then don't put the semicolon in the connection string.
> Connect to Oracle DB with Service Name through Web Installer
> ------------------------------------------------------------
>
> Key: OPENMEETINGS-1419
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1419
> Project: Openmeetings
> Issue Type: Improvement
> Components: HTML5/Installer
> Affects Versions: 3.1.1
> Reporter: Ioannis Vlachos
> Assignee: Maxim Solodovnik
> Priority: Minor
>
> OM can connect to Oracle DB with Service Name instead of SID, if you use the
> command line admin and use the correct notation ( / ) on the persistence.xml
> (e.g. jdbc:oracle:thin:@localhost:1521/openmeetings).
> However, you can't do the same thing through the web installer, since it does
> not recognise the / character in the DB url (which declares usage of Service
> Name) but only the : character (SID).
> It would be helpful if the web installer was improved, in order to support
> both SID and Service name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
