Is it possible oracle forms and report without applet? I have Oracle Forms and Report server 11gR2 with Weblogic server 10.3.6
Whenever I am try to run oracle forms and report on new machine,that ask me java plugin missing. Then it need to manually installation of that plugins.
Can I Oracle Forms and Report can run without applet(java plugin).
Related
I am trying to connect with Oracle 12c database using SSRS 2012.
Getting the following error. I cannot change any property of Oracle db but can change the version of SSDT if required.
A connection to an Oracle db requires Oracle Client software to be installed. It sounds like you do not have it installed or have a lower version.
To use data from an Oracle database in your report, you must have a
dataset that's based on a report data source of type Oracle. This
built-in data source type uses the Oracle Data Provider directly and
requires an Oracle client software component.
Oracle Connection Type (SSRS, Power BI Report Server, and Report Builder) - MS Docs
Check out the MS Docs for links are more information. Unfortunately, our OPs did this and haven't done this myself.
We use Oracle ebs R12.2.5 enterprise edition(11i to R12 re-implementation project)
I took the existing forms.fmb file , did the retrofitting changes compiled using forms builder- SUCCESSFULLY compiled.
But when i put the .fmd file in server path and try to compile I get the below message.
can someone help with this, why this error occurring
Error
Forms 10.1 (Form compiler):Version 10.1.2.3.0
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
FRM-10043: Cannot open file
But the file is there in the path. so my question is if we compile a form in forms 11g builder , will that run in 10g version ?
You must modify .fmb file in the same version what the unix server is having. You can open 11g form into 10g form.
By looking your error it seems it is oracle form's 10g Version 10.1.2.3.0 then you should open that fmb file in your local system with the same oracle form's version then edit it and deploye to unix it will be successfully compiled.
Do not use Oracle Forms Builder 11g to Create 10g Forms. Create your Forms for 10g using Oracle Forms Builder 10g. There are certain 10g libraries/forms packages that are not applicable to 11g.
Check out this article about Oracle Forms and EBS version compatibility for R12 written by Prasad Akkiraju, Senior Manager in the Applications Technology Integration from Oracle.
Our organization has a Windows server running SQL Server Reporting Services (SSRS). We use SSRS to build reports that access an Oracle database. We were able to get SSRS to connect to our Oracle database by installing Oracle Data Access Components (ODAC) for Windows on our server. We installed the Xcopy versions - both 32-bit and 64-bit (don't know if we needed to do both; SSRS used to only accept 32-bit drivers). We were able to successfully set up a data source in SSRS that connected to the Oracle database.
However, we write our reports on development machines using SQL Server Report Builder 3.0. When building a report that uses a shared data source on the server - the one that accesses our Oracle database, we get the error
The selected data extension ORACLE is not installed or cannot be loaded...
What do we need to do to be able to write reports from our development machines that use a shared data source to our Oracle database?
You need to install ODAC on your development machines as well. Even though you are configuring your report to use a shared data source on the server, Report Builder 3.0 will use connection drivers on the local machine to build and preview report data.
Report Builder 3.0 still seems to be a 32-bit application (as of 6/3/2016), so you only need to install 32-bit ODAC package.
I'm developing a web application using asp.net and mysql. When i run it using visual studio it works fine. But when i'm trying to publish it following errors are coming.Please guide me what to do.
Message in Settings tab:
The database provider is not specified for this connection string. Incremental database publishing is supported only for SqlClient as well as Entity Framework code First models.
I have an application I am writing that accepts files of various formats. Then I write code for each format (csv, excel, xml) to convert it and enter it into a SQL Server database. This is fine but I was just looking into SSIS and wondering if this would help.
The main question though is how do I run these packages within my own code? Is it easy to pass parameters? If I move this web app to another server does it depend on other components being on that server (maybe SQL Server 2012 installed)? Or is it just some DLLs I can reference from my web app?
All the demos I see are about using the SSIS tool but I am more interested in how difficult it is to call packages with parameters from my code.
The BIDS/SSDT installation includes a complete client SDK that makes it pretty simple to run SSIS packages via code.
This MSDN article explains how to load and run a package via C# in detail but the actual code boils down to:
using Microsoft.SqlServer.Dts.Runtime;
.
.
.
Application app = new Application();
Package pkg = app.LoadPackage(PKG_FILE_NAME, null);
DTSExecResult pkgResults = pkg.Execute();
The Package object has a lot of properties and methods you can look into, in particular there is a Parameters collection that allows you to pass parameters into your SSIS package before execution.
There is a very cool library called EzAPI where you can generate your own packages and call them from within C#. It gives you a lot of flexibility to generate SSIS on the fly and execute.
http://sqlsrvintegrationsrv.codeplex.com/releases/view/21238
I built a couple console apps inside this project to test some of these methods and you might find the examples useful:
https://github.com/thevinnie/SyncDatabases
Look at "BuildingAPackage" and "BuildALookupPackage"
You can programmatically build SSIS packages using C# or VB.NET and then run the packages. You can also load an existing package programmatically to execute it. I have little experience with building packages this way since most of the packages can be built easily using the following tools.
Read the article Building Packages Programmatically on MSDN for more details.
I feel that it is easier to build the packages through these IDEs depending on which version of SSIS you are targeting. You can also create initial packages through SQL Server Import and Export Wizard and save the SSIS packages to the local disk, which you can later modify according to your needs.
SSIS Version Development IDE Visual Studio Shell
------------------- ----------------------------------------------- -------------------
SSIS 2005 Business Intelligence Development Studio (BIDS) Visual Studio 2005
SSIS 2008 - 2008 R2 Business Intelligence Development Studio (BIDS) Visual Studio 2008
SSIS 2012 SQL Server Data Tools (SSDT) Visual Studio 2010
You need to reference the appropriate SSIS specific DLLs in your code to create/load SSIS packages.
However, you will need a SQL Server Integration Services license to run the package. You cannot simply reference the DLLs alone. The license is usually part of your SQL Server license, if you already have one.
Response to your comment:
We will have SQL 2012 or 2008R2 on a separate server.. So I just need to paste the needed DLLs on my web server and reference them. correct ?
The packages will execute on that server. You are just remotely invoking to execute them and you should reference the appropriate DLLs in the code within your web/other form of external application. I usually schedule the packages to run on the database servers under SQL Server Agent Job. You can try that if that is an option for you.
Package parameters are read-only from an external application. You'll need to pass them in as variables (which I have done). If you are dealing with an existing package with parameters, you may consider writing a script task that populates the parameters from the variables (which I have not done).