You have to tell your client who "xejoe" is, by specifying the connect details in tnsnames.ora or have an oracle naming service available, i.e. the tnsnames.ora method, add this stanza to the tnsnames.ora file:
tnsping xejoe ... Used parameter files: <drive:>network\admin\sqlnet.ora ... Attempting to contact (DESCRIPTION=... <connect string host:port:service_name info> ... OK (<n> msec) ... ... Or could say tns-<n> error or something *not* OK
And if you've added the port number exception to your firewall, it should be all good to go.
xejoe = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname or IP for xejoe instance>)(PORT = <port#>)) ) (CONNECT_DATA = (SERVICE_NAME = <service name>[.domain_name] ) ) )
Ahh. Apex? How about the system password set up by the installer ... I'd assume you used the "get started" shortcut, http://127.0.0.1:8080/apex/f?p=4950I get Invalid Login Credentials.
this usually won't work from a remote machine. You'll have to use
where TNS-Name is the configured "alias" (or actual TNS-Connect-String) for your XE instance.
Hmmmm. So, what's different? Are you trying the apex admin URL ...:8080/apex?p=4950 or trying to login to a workspace?was able to login at different workstation before.
But for the apex admin URL it does take credentials for a database user, and as mentioned on the login page it should be a database user with the DBA role privilege, so that is where one uses the system login and the password setup in the installer. System is a database user, it can be confusing.I agree that it can be confusing. On the other hand, it's pretty well documented... And it can't be much different in that case: The XE management application/homepage/... (4950) uses an APEX authentication scheme based on database accounts, so you can (or precisely: have to) use your system user account there as well. One of the reasons for this is that you are encouraged to administer your APEX using that application, which means you have to have something to create an APEX workspace (and users for this workspace) before you can use APEX authentication. Of course it would be possible to direct a user straight to the APEX internal administration, but for XE it seems right to have everything (database and APEX administration) in one pre-build application. And on the other hand it seems suitable to use dba accounts to manage the database instead of "just" APEX users.