Build your application into a *.war file and deploy that file on your web application server. The uitest.war file that comes with the AppProjector download is an example of such a deployable application.

Mainsoft for Java EE generates a script that you can use to run your console application outside your development environment.

Yes and VistaDB 3.x supports the Allow Partially Trusted Callers attribute as well. We have customers using Re-invent.com which is a shared ASP.NET host.

The AppProjector has been designed to work on all J2EE-compliant web application servers and has been tested on Tomcat, JBoss and WebLogic.

We found the question of installation so troublesome with mismatch of versions and users patially installing the software we bundle the complete java jvm and libraries (including J3D?) and in a subdirectory of our installation directory. No troubles since we did that. Topic Java3DFAQ .

Yes, you can adapt the Java EE application you've developed to any standards-compliant Java EE application server such as JBoss or WebLogic. You will have to modify the generated server specific deployment descriptors and potentially change your code if you make direct calls to server-specific APIs or server specific extensions. With Mainsoft for Java EE, Portal Edition, the .NET Framework provided by Mainsoft is based on the JSR 168 specifications. Therefore, if you use the .

No. The AppProjector works with the native JVM found in older versions of windows and IE. It also works with the Sun Java desktop environments (Java 1.3or later) that come pre-installed on most new computers.

Easy. The AppProjector's application model is easily adapted to your existing EJBs. The XML screen definitions and data aware controls in the AppProjector cleanly separate the presentation layer from the business logic.

The AppProjector web viewer client can be embedded into an HTML web page or can be used in a separate browser frame on those pages of your application where you would like the benefit of improved interactivity. The other HTML pages don't need to be modified.

IT Works® ManagER is the primary interface used by the network administrator. Open the Help Desk panel of IT Works® ManagER, right click on a computer, drag the software package(s) to the desired computer and select Deploy. Sit back and relax. In minutes the software will be deployed to the selected computer or groups of computers.

Yes. Applications developed with the Enterprise or Portal Editions can be deployed in a clustered environment. If you are using Grasshopper, you can deploy to Tomcat only in a single CPU, non-clustered server. The Mainsoft for Java EE runtime libraries consist of JAR files that are compliant with the Java specification. These files can either be added to the classpath of the Java EE application server, or they can be included in the WAR file of the application being deployed.

The deployment time varies from implementation to implementation depending upon the amount of customization as well as extent of back end integration required.

ParaWeb automatically reads any application developed by ParaGrafix, so you can use application files developed for desktop Frontline with little or no modification. All you need to do is write some HTML pages with input forms, some output HTML templates, and a simple script detailing what output (DXF, GIF files, etc. ) should be generated. To see examples of HTML pages interacting with ParaWeb, click here

Visual WebGui deployment can be done simply by copying the project directory without the source files with copy paste to the a virtual IIS directory or you can use the Microsoft web application setup project and use it exactly as you would create an ASP.NET installation. A Visual WebGui project is actually an ASP.NET project with extra references.

Mainsoft applications are pure Java applications and as such they do not impose runtime requirements beyond those of Tomcat or the application server you decided to use. For system requirements of Linux deployments, refer to the article, Configuring your Linux box to deploy your Grasshopper application.

Yes. Aware IM applications are fully portable between the supported databases. Aware IM will automatically create and manage database tables for a specific database engine based on the object definitions within Aware IM applications.

Assuming that you have already installed our server and /or simulator on a nearby Windows machine with IP connectivity to the Linux host, this is the deal: Copy our jar file containing our support for Java to the host (the same jar file we use to support Java locally) Set the class path used by the host so that it can locate your application's class files and our jar file Open up a spare port on the host and specify the port number and either of the host address or host node name when you de.

Yes, you will be able to answer calls, play announcements, pass text strings through a text-to-speech engine, record messages, and detect keypad input. You will not be able to use speech recognition except in a clumsy way because the drivers for voice-modems tend not to allow programs fully duplexed access to the audio streams in a call.

You DO NOT deploy if you still have some control over the aircraft. Just because the engine quit or you lose a rudder cable or an aileron, you can still steer the aircraft and have a choice of landing sites, even if trees. Trees make good emergency sites. You DO deploy if you lost control and the chute will slow down your descent rate. Examples, broken elevators and resultant nose dive, mid air collision, some other structural failure.

Yes, create a war file and name it file.war and place in the root directory of your web space (mainwebsite_html or /var/www/html/ ) The contents will automatically be deployed when the JVM is restarted.

application must be delivered in a set of JAR files and all application resources, such as images, configuration files, and native libraries must be included in the JAR files. The resources must be looked up using the method ClassLoader.getResource() or an equivalent method. Java Web Start only transfers JAR files from the web server to the client.

For deploying a Web application like the default-web-app, please read the "Deploying With Exploded Directory Format" section of Getting Started Guide that comes with OC4J. For OC4J 1022, you can set the attribute development to "true" for the orion-web-app in your orion-web.xml file and that will save your generated code in the persistence directory. <orion-web-app deployment-version="9.0.2.0.0" development="true" jsp-cache-directory=".

See also "SQLException: Invalid column type error" and "How can I use SQLJ in a middle-tier environment".

The Studio currently has a Deployment Wizard to help deploy an application. Currently this is a fairly primitive method of transferring files over to the server machine via FTP or a mounted fileshare. You can either use the wizard, or simply copy the entire directory structure where an application is saved, over to the server machine. By convention, applications should be placed in the INSTALL_ROOT/deployment directory of the server. Then run: and restart the server.

Yes. If you wish to deploy only a Web module then you can utilize the default application OC4J is configured with. This is a two step task: First, tell the container about the WAR file to be deployed. Open the <J2EE_HOME>/config/application.xml file in an editor. Add a new <web-module> tag and specify the attributes for your WAR file. Secondly, tell the OC4J HTTP server about the new WAR file and provide a URL to access it. Open the <J2EE_HOME>/config/http-web-site.

Yes. You may package both security and datasource configuration files with your application archive (EAR) file. When the application is deployed, the files will be used by OC4J to establish connections or validate user credentials. This is a standard packaging mechanism employed by Oracle JDeveloper when it deploys applications. To achieve this, provide the files you want to accompany the deployment in the same directory as the J2EE application.xml file.

This is not supported or recommended. However users have successfully deployed the mapviewer.ear file downloaded from OTN into a 3rd party J2EE compliant container, such as JBoss. You will need the Oracle JDBC driver (classes12.jar or ojdbc14.jar) and Oracle XML parser (xmlparserv2.jar) in the J2EE container's library path. The latest versions of both should work. Note that for WebLogic, it appears that you must manually unpack the mapviewer.ear file and then deploy from the unpacked directory.

No. The plugin for Sun Java System Application Server 8.x Platform Edition does not support High Availability.

Yes. The AppProjector is designed to run on any web application server that implements the J2EE Servlet specification 2.1 or later.

The Flash Detection Kit helps developers and first-time users easily implement Flash content on their websites.