deploying OO4O - OO4O and Wizards(Archived)

How do I deploy a VB application that uses OO4O? What components are required for a client application using OO4O? Is the entire 75MB package needed to install or are their specific OCX/DLL's that can be used?

If you assume they already have the correct version of the Oracle client software installed then the ORADC.OCX and OIPxxxx.dll are probably all you need to distribute (and register). If you can't be certain of that then you need to redistribute everything. There used to be a section in the help file that discussed exactly what parts need to be redeployed, but it didn't really get into how you deploy everything (client software included).


Does Instant Client support MS IIS?

I read the installation instructions for Instant Client but they consistently refer to Apache. Does IC support support IIS?
Thanks - Chris 
It would be nice if someone has an answer....i still have the same problem. It still doesn't work with IIS :( 
It would be nice if someone has an answer....i still
have the same problem. It still doesn't work with IIS
:(The installation instructions state that you should use the PATH statement to direct the dynamic loader to the folder where your OCI dlls are. You can also put the dlls in the %systemroot%System32 folder - where your inetinfo.exe (IIS) is located. I suggest the former.
You made no mention of how you attempted to setup your web application - whether you are using html, asp, (and version).
I don't mean to be rude, but you need to read the documentation, and you may need to read up on how Oracle client works. Read the documentation:
There's a good article that just came out on CodeProject:
You may have to write your own interface to use the OCI and deploy it to IIS servers. The installation method is dependant on what technology you're programming with. 
johnny b is right. it should work.
we have an IIS6.0 server with classic asp page that retrieves from an oracle 9i database. We use it trough the OLE DB.
When you follow the instruction to deploy the instant client (PATH variable and ORACLE_HOME in registry) it should work directly. From within an asp page you can do: ADODB.Connection, blablabla and .ConnectionString = "MSDAORA" blablabla
For testing the instant client connection, use sql-developer from Oracle. It is a zip-file, unpack it an run it. (java client should be on your system)
I must say i use IC version instead of I can not get this working through OLEDB. I must manualy copy some extra files from an original oracle client to get it working.

InstantClient and Java WebStart

I would be very grateful if some of the gurus here tells me how exactly to exploit InstantClient's advantages (no TNSNAMES.ORA and SQLNET.ORA in ${ORACLE_HOME}/network/admin, no installation process, no registry, etc.) by using Java WebStart. The goal is simple: I deploy 2-tier ADF JClient application and, of course, it does not work on computers without Oracle Client. For the record, I am not aware of how to manage this Oracle Client -- I am not specialist in those Oracle drivers at all. I am outsourcing a project and as a part of that I must do early deployment.
I want to avoid doing all these evil spells, namely copying the fore-mentioned files or writing something in registry, etc. I just want to provide necessary runtime environment for using JDBC OCI drivers. That's it.
Of course, I spent 2 days intensely trying to do what I describe here, with no success and with strange errors, like "cannot find 'kpuhhalo' in OCI.dll", this is when I include only one DLL from full Oracle client, when I put all InstantClient, it suddenly starts not to find other such function... I will not bore you with the full details. For a start, I would want to be told is there something special that needs to be done? I am aware of all common Java WebStart things to do and I am pretty much sure I done them.
Any advice will be some help.
Thanks for the attention.
Dimitar Panayotov.

Will the new InstantClient be deployable with ClickOnce

Will the new version of InstantClient that comes with ODT 11 beta 2 be deployable with ClickOnce? 
Unfortunately it will not be deployable via ClickOnce. One of the requirements for ClickOnce deployments is that the files deployed must be completely written using managed code; the InstanceClient essentially is an xcopy deployment of the normal Oracle Client and are (almost certainly) not written using pure managed .NET code.
I talked with Alex Keh from Oracle after one of his sessions at OpenWorld last week and expressed my desire for a purely managed code solution that can be deployed via ClickOnce. I am currently looking at other alternatives including writing my own provider that will talk to, in my case, a Java server that will run the actual JDBC code. My requirements are, however, quite different than most as I need not only ClickOnce deployability but I also need the client to obtain it's data via http and not just tcpip.
Perhaps if there is enough demand we could convince Oracle product management to consider a purely managed solution.
Tim Tow
Oracle ACE
Applied OLAP, Inc 
I also need to have my application deployable using ClickOnce but having the same problem. If you guys find any alternatives on this please let me know as well.
There is a 100% managed alternative out there. DataDirect has one, but I have never tried it. 
I see. But of course my first choice would still be a free provider. I would consider that my last alternative.

Client development

Hi all,
What I would like to know looking through the development guides (we are
still waiting to have our copy of WLE delivered and installed) is, if I
develop an ActiveX client I will want to be able to deploy them to any
number of clients, anywhere in the world, can these user just run the
activeX client application or do they have to run it through the application
builder each time.
When we am developing a client application do we run the application builder
once to get the bindings, use the bindings in the development of the client
code, and then the client code is free standing and execuatable; or do we
have to have elements of Application Builder on the client machines (this
has big implications on development if the users are on different sites
Please help a very confused developer.
John Graville.
 You should not need to run the application builder on every client machine but
you will need to package your client with the the type libraries and do all the
proper registrations.
If I recall, there should also be a tool on the ActiveX client kit that will
allow you to create a deployment pacakge with the type libraries that also does
all the registrations.

Windows Application Deployment & Client Software

+(I think I finally found the most appropriate forum for my concerns.)+
Traditionally my company has been building windows applications in "Windows Forms" using C# on .Net 2.0. These applications have most often used Oracle 10g as a data store and the built-in System.Data.OracleClient provider library for their DAL, then been distributed via an application server such as TerminalServer/Citrix.
Being a pain-in-the-butt progressive employee, I am trying to step out of this paradigm by building a WPF .Net 3.5 application that uses ODP.Net to talk to a 10g database... and most importantly, avoid TerminalServer/Citrix deployment to make the best of WPF features.
I have built a baby application (MVVM style) and a very simple database on our dev box; I have installed ODP.Net and embedded the Oracle.DataAccess.Client and Types libraries in my application. On my machine I have a full blown Oracle 11g Client installation with an Oracle Home. In that Oracle Home is my tnsnames.ora file that maps the arbitrary address name to the specific server host and port, and my application's connection string uses that address name. If I am understanding properly, the ODP.Net client library is not enough, and that it looks at run-time for an Oracle Home to resolve the address name to a host/port via tnsnames.ora, and then use the actual client software to work with my database.
My issue then is that I need to distribute the application to my users without a full-blown Oracle Client on their machines, while still refraining from strongly-typing the host name and port in the compiled application. In their TerminalServer/Citrix model, this is cake - a client is done once on the host box, uses tnsnames just like on my box, and is easily managed in once place. WPF however is pretty stunted by terminal server deployment (until Windows 2008 server where rendering is pushed all the way through to the user's machine), so I here is where I am stuck:
Is there a way to embed/distribute necessary client software with the WPF w/ ODP.Net application so that the users can enjoy the simplicity of ClickOnce deployment, have only a single application to maintain, and maintain the inherent performance that comes with ODP rather than Microsoft's weak-ass client library?
Thanks ahead of time to any who take a moment to help me out. I appreciate it.
I think I found a little more on this, but I'm still curious...
is the instant client (traditionally xcopied) compatible with:
1. Is Instant Client deployable via ClickOnce (can you setup the deployment to use xcopy to dump the client software on user's machine and then add the folder to PATH variable)?
2. Will the instant client software use a TNSNAMES.ORA file if one is present in the directory?
If there's other ways, I'm all ears.