Securing my APEX application from theft.

I have an APEX application that I have created and am delivering to a customer.
How do I make it so they can’t copy it and use it in other departments without buying a new licensee?
How can I make it so their employees can’t steal the application?
Technically speaking

I'm not sure there is a way to make it 100% secure. If you don't have any control over the customer's environment, any future developer could technically undo any licensing measures you've added. Your best bet would be to get the customer to agree to some sort of Terms of Use which would give you future legal recourse. My only other thought is to host some parts of the application on your own site which would give you more control over licensing, but then you run into problems when connectivity goes down on either end.

Similar Messages

Info : Migrating Apex Application from Non-SSO to SSO environment

Hi All,
This post is to share my experience while working on APEX. This may be useful to some apex developer.
If we migrate an apex application from a non-sso (i.e. http) to sso (i.e. https) environment, the flash chart doesn't work.
I found that in the source of a Flash Chart region, we use #HOST# variable to locate the swf file. The environment variable takes the correct path but with "http" as prefix. But to access application pages "https" is used. Because of which, the swf file couldn't be located by the application.
Work-around Solution : If I hard code the value i.e. the application path having "https" replacing #HOST# variable then the flash chart works fine. I couldn't found a way by which the #HOST# parameter value can be updated to take "https".
The same environment host other non-sso applications as well.
Any comments on this are welcomed.
Regards,
Mangal

Hi Dirk,
Thanks for the reply.
As I mentioned earlier, by Non-SSO I mean "http" and by SSO I mean "https". This is because, before migration the application was accessible using "http" and now we have to use "https" alongwith SSO to access the application. I only want to highlight the Flash Chart issue with this migration.
The problem doesn't solves with your solution as I am getting correct instance/environment name with #HOST# but prefixed with "http" and not "https". Hence the application won't be able to locate the required swf file.
Even the workaround I mentioned is only feasible, if an application has only few Flash Charts. However, if there are large no. of Flash charts in an application, then it would be a tedious task to update all flash chart source either by an application item (as you mentioned in your post) or hard coding the path itself. Also, every new Flash Chart source needs to be updated by a developer to fix this.
A better solution is required by which the Flash chart source is not touched and the #HOST# variable for the application is updated to take the "https" prefixed to the swf file path.
Regards,
Mangal
Edited by: Mangal on Mar 5, 2009 11:31 PM

Executing multiple apex applications from EBS

Hi,
We have developed an apex application which can be triggered through an application link from Oracle EBS. Now, we have a requirement to run multiple apex applications from a single EBS session simultaneously.
Can someone provide information on how this can be acheived?
Raajkumar G

Hi,
We have developed an apex application which can be triggered through an application link from Oracle EBS. Now, we have a requirement to run multiple apex applications from a single EBS session simultaneously.
Can someone provide information on how this can be acheived?
Raajkumar G

Can't install my Apex Applications from 10.2XE

Installation from 11.2 XE went without problems, but I had a problem importing my Apex applications from my old 10.2XE database.
According to the Installation Guide, 7 Importing and Exporting Data between 10.2 XE and 11.2 XE
2. Connect to 10.2 XE database as SYS user and run gen_inst.sql. This will
generate install.sql, gen_apps.sql and other .sql files. The files will
be generated in the folder containing gen_inst.sql.
=> the generated script f100.sql ends with
ERROR:
ORA-06502: PL/SQL: numeric or value error: host bind array too small
ORA-06512: at line 1
This was during:
--application/shared_components/plugins/region_type/com_oracle_de_cczarski_labelcloudplugin
begin
wwv_flow_api.create_plugin (
=> the generated script f100.sql doesn't contain "set scan off"
but does contain lines like "p_home_link=> 'f?p=&APP_ID.:1:&SESSION.',"
Running the script f100 with set scan off added results in
...page templates for application: 100
......Page template 2301643674799144
......Page template 2301746430799146
......Page template 2301820809799146
......Page template 2301944547799146
......Page template 2302037696799146
......Page template 2302118851799146
ERROR:
ORA-01741: illegal zero-length identifier
Anton

Anton,
1) When you export your application 100 from within Application Express from your old instance and you compare it to the one generated, are there any significant differences?
2) Can you export your application 100 from within Application Express from your old instance and import it back into the same (old) instance but with a different application identifier?
Joel

How to restore or backup Apex application from Command line ? URGENT

We have Oracle apex 4.1 installed in Oracle 11g R2 database (windows 64-bit) 2008 R2
For some reason our database dictionary objects are corrupted.
We wanted to backup our Apex applications in some workspaces ASAP.
We are not able to access apex from http://localhost:7777/pls/apex/htmldb_login
We have an underlying database schema export (expdp).
1) Is there a way to export or backup the apex application without logging into the apex URL ? if yes how ?
2) Does Oracle has any of its own native tool to backup and restore from command line ?
Thanks in advance

My (MS Windows) experience, if I may; perhaps you'll find something useful.
You'll find the README.TXT file in /apex/utilities directory. Read it.
In order to use APEXExport, you need JDK version 1.5 or higher. Check your version by typing (and viewing the result):
C:\>java –version
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)Its directory should be part of the PATH environment variable: on my computer, directory name isC:\Program Files\Java\jre1.6.0_06\binFurthermore, Oracle JDBC class libraries must be part of the CLASSPATH environment variable. Check whether it exists (in Control Panel - System - Advanced - Environment Variables). For my 10gXE, it is here:C:\oraclexe\app\oracle\product\10.2.0\server\jdbc\lib\ojdbc14.jarI couldn't make it work; didn't know that ".\" directory must be entered into CLASSPATH as well (found that information in Arie Geller's book). Therefore, my final CLASSPATH version is:.\;C:\oraclexe\app\oracle\product\10.2.0\server\jdbc\lib\ojdbc14.jarOK, setup is done. Now, go to your /apex/utilities directory and, from the command prompt, run (mind the upper case!)java oracle.apex.APEXExportwhich will show a short help.
I chose to export the whole workspace. In order to do that, I need the workspace ID (got it from Apex's SQL Workshop; that might be a problem as you can't get there, can you? I can't tell how to find that information apart from SQL Workshop, but I'm pretty sure someone, who is much more experienced than me, will know it). OK, here's how you find it:select v('WORKSPACE_ID') from dual;Finally, here's the final step - export:C:\apex\utilities>java oracle.apex.APEXExport -db localhost:1521:xe -user scott -password tiger -workspaceid 1038408092496568The result are fxxx.sql files (where "xxx" represents application number).
I hope you'll manage to export your applications; basically, nothing special here (except that ".\" directory in the CLASSPATH variable).
Best of luck!

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Export Apex application from the command line and eliminate Apex

I had a problem to migrate version 4.0.2 to 4.1 Apex, and I can not access to Apex. I open a Thread with the problem but so far I have no answers.
Given that Apex is not working, I can think to do the following:
---Export applications that are currently installed in Apex
---Totally eliminate the apex and do a new install
Does anyone know if this is a viable option?
If Yes, what package I have to run to make the export of applications?
How do I completely remove the current installation of Apex? And leave prepared the database for a new installation from scratch, the version of Oracle we use is 11 g Enterprise Edition Release 11.2.0.1.0.
If someone can give me any advice would be very grateful.
Best regards
Gerard

Hi Patrick
+(-) Do Have you had any installation issues?+
I had some but I think that are already resolved, I have another open thread Re: Big problem in update to Apex 4.1 with the details of the problems I had.
+(-) Do Have you checked the log files?+
Where can I find them?
+(-) What is your database version?" "Does Is it XE?"+
I'm using "Oracle11g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production"
+(-) Which web server do you use to access APEX (Apache with mod_plsql, APEX Listener or Embedded PL/SQL gateway (EPG))?+
Embedded PL/SQL gateway
+(-) Which URL did you use in the past to access APEX?+
This URL: http://192.168.0.5:8080/apex/apex
+(-) What happens if you enter http://192.168.0.5:8080/apex+
If enter "http://192.168.0.5:8080/apex/" I get the following error
"Error ERR-1014 Application not found."
"application = 4500 workspace = 10"
Thanks a lot
Gerard

How to secure an Apex application?

I have created an Apex web based application and like to distribute the URL to public.
Any user can query something and can insert new records (but not update or delete).
How can I prevent my site from malicious attacks?
Eg. some bots trying to insert junk data million times.
Some junk trying to run automated queries to fetch all data from database
Any other suggestions welcome.
Thanx

Hi
Session State protection
Example:
http://apps2fusion.com/at/64-kr/400-preventing-url-tampering-using-apex-session-state-protection
Explaination
http://theheat.dk/oracle/ukoug2007/Lorenzen-apex.ppt
Regards,
Iloon
Don't forget to mark replies helpful or correct ;)

HELP! Need help in restoring APEX application from database backup

I accidentally deleted many pages from my development APEX environment when I thought I was deleting from QA. By the time I discovered it, it was too late to do a flash back. The DBQ I am working with is now trying to recover from a database backup, but we are not having much success. Can someone point me to any documentation that may exist on exactly what to restore from what schemas? It is not intuitively obvious what should be extracted and restored? Any help would be GREATLY appreciated!

I have older exports, but I would loose 2 weeks of work by going back to them. I need to be able to restore from a database backup so I get back my changes. What we tried to restore didn't bring back the deleted pages so we must have done something wrong.

Accessing an APEX page, from an external application, passing a parameter

Hi,
We are tring to allow users access to a suite of reports we have developed within an APEX application, from an external source. Ideally we want to embed a URL that when activated, would access the APEX page, but would populate the APP_USER so the full functionality of the report can be fully utilised (region access etc). I have tried serveral options, such as:-
f?p=193:4.::NO:193::APP_USER:MR036668
i.e App no 193, page 4 and trying to populate APP_USER with "MR036668" but get the folowing error:-
Error ERR-1002 Unable to find item ID for item "APP_USER" in application "193".
Can anyone help?
Thanks
Mark

Hi ,
Please try this
Please open your application in APEX then go to shared component then create application item which is named as global item referenced by all the pages
F193_USERNAME
f?p=193:4:1903218616592015::::F193_USERNAME:Markieb1888
otherwise
you can pass LIKE THIS
f?p=181:1:1914838104983187::NO::P111_USERNAME,P111_PASSWORD:Matt,Baker
please let me give some more details to help you.
thanks
Mark
Edited by: Websoft on Sep 9, 2009 6:17 AM

APEX application deployment

Hi All,
I will soon be exporting my first APEX application from a development database to a test database. I do not want to export the data which the application is built on as the development database contains sample data instead of the "real" data. Before exporting my application, I will of course install APEX 3.2.1 in the test environment and then import the "real" data into the test database so that once the application has been exported and installed in the new environment, the APEX application will already have its data in place.
On page 14-12 in Chapter 14 of the Oracle Application Express Application Builder User's Guide, I saw the following section:
Exporting an Application
When you export an application, Oracle Application Express generates a text file containing PL/SQL API calls.
To export an application:
1. Navigate to the Export page:
a. On the Workspace home page, click the Application Builder icon.
b. Select an application.
c. On the Application home page, click Export/Import.
d. On the Export/Import page, click Export and then click Next.
2. From Application, select the application to be exported.
3. From File Format, select how rows in the export file will be formatted:
■ Choose UNIX to have the resulting file contain rows delimited by line feeds.
■ Choose DOS to have the resulting file contain rows delimited by carriage
returns and line feeds.
4. From Owner Override, optionally select another owner. By default, the application is owned by the owner identified in the application attribute owner.
5. From Build Status Override, select one of the following:
■ Run Application Only - Developers can only run an application
■ Run and Build Application - Developers can both run and edit an application
Selecting Run Application Only is an effective way to protect an application from modifications from other developers.
6. From Debugging, select one of the following:
■ Yes exports the application with debugging enabled.
■ No exports the application with debugging disabled.
7. From Exporting Supporting Object Definitions, specify whether to export
supporting object definitions with your application.
8. From Export Comments, specify whether to export comments for this application.
See "Adding Developer Comments" on page 6-22.
9. Use the As of field to export your application as it was previously defined. Specify the number of minutes in the field provided.
10. Click Export Application
Since I do not have any images, themes, static files, workspace users, cascading style sheets, etc, to export, it makes no sense to use the “Packaged Application” method to perform the export. All I need is the application definition that contains all my interactive reports, forms, etc.
The next step would then be to Import the application into the target Oracle Application Express instance and install the application.
This method should be OK for my needs, right?
Thanks

By simply doing an application export, all you will export is the metadata associated with your application (page definitions, items, processes, validations etc).
No "Customer Data" will be exported neither will any tables or PL/SQL packages that are owned by your parsing schema.
If you aim is simply to export the APEX application and no tables, pl/sql units, data etc, then doing a simple application export should be good enough. Thats all we ever do and then add the PL/SQL units / table data on top as additional scripts.
Hope that helps
Duncs
http://djmein.blogspot.com
As a courtesy, please remember to mark helpful or correct responses accordingly :)

Move APEX Installation from one database to another one

My task is to move an APEX installation to a new one.
Exact: The customer wants to downgrade from Enterprise Edition to Standard Edition.
Database version is 9.2.0.8 (both), APEX version is 2.2.1
What I've done:
- Full database export (from EE)
- Delete EE-software, reboot server
- Install. SE-software, reboot server, create db
- Full database import
around 40 db objects are invalid after recompile:-(
2. try:
- create db (SE)
- Install. of APEX 2.2.1
- Import of the schemas flows_020200, flows_files and the APEX user-schemas
- recompile
all db objects are valid, but the APEX applications belongs to a workspace "unknown" so no workspace have access to its applications:-(
Has anybody an idea or a recipe for me?
Many thanks
Ralph

Hi, Scott –
Thanks for your post on this thread last Friday evening, May 2. I posted my message on Wednesday April 30, and after receiving no response after two days, we decided to go ahead with my planned migration on Friday afternoon. We completed it shortly after 5:00 PM (just six hours before you posted your response). Everything seemed to go well, but based on your expert opinion, we've decided to scrap the TARGETDB installation and redo the migration according to your recommendations.
It seems that exporting each Apex application individually from the SOURCEDB and importing it individually to the TARGETDB would be a laborious and lengthy process, but if Oracle provides no faster and more convenient alternative, then I guess this is something we’ll have to do.
However, this has sparked more questions….
Like I said in my previous post, we’re relatively new to Apex. When I mentioned exporting/importing Apex workspaces, I was imprecise in my terminology. I know you can export Apex applications from the SOURCEDB Apex installation and import them into the TARGETDB Apex installation using the Web based Apex Admin tool. But can/should you do the same with workspaces? Or do you recreate corresponding empty Apex workspaces on the TARGETDB and then import the appropriate Apex applications into them?
What would you suggest to be the best way to do this?
Thanks again for your help!
--JP

Problems passing value to an APEX application URL

Greetings,
My environment is:
Apex 4.0.1
Oracle 11g
Apex Listener (Weblogic 10g)
I am trying to pass a value to an Apex application from outside of Apex. Here is the URL I am using:
http://<servername>:<portno>/apex/f?p=138:2:0::::F138_ID:abcde
What happens when I enter this URL is the Login page is presented and I can successfully log in. I am directed to page 2 but the value of F138_ID is empty. I have tried it with an application item and a page item but still no value is passed. I have tried creating the page item where the value is populated from the application item. I have tried setting the value in a PL/SQL process. (:P2_ID := :P138_ID;) again no luck.
Should this work? And if so, does anyone have any idea why it isn’t?
Thanks for your help,
Larry

Thanks Sarvan,
Unforunatly that did not work. I have been working with it some more and noticed that if the page I am trying to access has an Authentication of 'Page is Public' the passing of the value works as expected. It is only when Authentication is set to 'Page Requires Authentication' (i.e. the user needs to provide a userid and password) that it fails. Do you have any idea how to get around this?
Thanks
Larry

Error when calling a procedure from my apex application

Hello.
I want to create a small APEX application that can configure asynchronous change data capture (distributed hotlog) on certain tables.
Basically, what the application should do is to simply create change tables. Everything else is set up as prerequisite.
My problem is that when I run the following script from schema apex_cdd (using sqldeveloper) , it works; but if I run it from my apex application by calling it when pressing a button as a pl/sql process, it doen't work.
BEGIN
apex_cdc.enable_table_capture
     (     i_owner => 'staging_cdcpub',
          i_change_table_name     => 'g_changeTable',
          i_change_set_name     => 'Source_changeSet',
          i_change_source          => 'orcl01_cs',
          i_source_schema          => 'My_src',
          i_source_table          => 'G',
          i_column_type_list     => 'STARTDATE DATE,STATUS CHAR(1),NAME VARCHAR2(10),ENDDATE DATE,DESCRIPTION VARCHAR2(255),ID NUMBER(8,0),VALUE NUMBER(10,2)'
END;
If I look in the trace file, i see that the error is:
CDCdebug:in ChangeTable.java enableDisabledTriggers: ORA-06550: line 1, column 8:
PLS-00201: identifier 'SYS.DBMS_CDC_SYS_IPUBLISH' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
oracle.jdbc.driver.OracleSQLException: ORA-06550: line 1, column 8:
PLS-00201: identifier 'SYS.DBMS_CDC_SYS_IPUBLISH' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
Other remarks:
- My procedure calls: sys.DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE.
- I gave the same rights that I gave for apex_cdc schema to flows_030200 and APEX_PUBLIC_USER schemas (just to see if it works), but it doens't.
Is APEX calling the procedure from another schema ?
Does anyone has an idea why this procedure crashes if called from APEX application, but works ok if called from the same schema APEX application runs on, but using SQLDeveloper ?
Any thoughts are appreciated.
Radian

The procedure apex_cdc.enable_table_capture i created myself with no authid mentioned explicitly, so it uses definer rights, by default.
BUt this procedure is simply a wrapper for sys.dbms_cdc_publish.create_change_table.
When I look on the security model for this sys.dbms_cdc_publish, i see it runs under invoker rights. (http://www.psoug.org/reference/dbms_cdc_publish.html).
The code is like this:
CREATE OR REPLACE PROCEDURE enable_table_capture
          i_owner               IN VARCHAR2,
          i_change_table_name     IN VARCHAR2,
          i_change_set_name     IN VARCHAR2,
          i_change_source          IN VARCHAR2,
          i_source_schema          IN VARCHAR2,
          i_source_table          IN VARCHAR2,
          i_column_type_list     IN VARCHAR2
     IS
     BEGIN
          EXECUTE IMMEDIATE 'alter session set REMOTE_DEPENDENCIES_MODE=SIGNATURE';
          EXECUTE IMMEDIATE 'begin add_log@orcl01(i_tableName => ''G''); end;';
sys.DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE(
owner => i_owner,
change_table_name => i_change_table_name,
change_set_name => i_change_set_name,
source_schema => i_source_schema,
source_table => i_source_table,
column_type_list => i_column_type_list,
capture_values => 'both',
rs_id => 'y',
row_id => 'n',
user_id => 'n',
timestamp => 'y',
object_id => 'n',
source_colmap => 'n',
target_colmap => 'y',
options_string => NULL);
END enable_table_capture;

APEX Application accessing data from two different databases

Hi All,
Currently as we all know that APEX Application resides in database and is connected to the schema of that database.
I want APEX Application to be running and accessing data from two different databases. Elaborating my question,
Currently, my APEX Production Application is connected with XXXX Schema of DB1 Database(Where APEX Resides). Now I want to add some pages into this APEX Application for REPORT Purpose, But I want to connect this REPORT APEX Pages to get data from Different Schema YYYY for Database DB2.
Is it possible to configure this scenario?
The reason for doing this is to avoid the REPORT related (adhoc queries) resource utilization effect on Production DB1 Database.
Thanks
Nil

1. If you do the joining of two or more tables in DB1 then all data is pulled over to DB1 and then the join is executed: so more data over the databaselink and more work for DB1. Better keep the joining stuff where the data resides and just pull exactly that data over that you need.
2. Don't know about your different block sizes. Seems a nice question for one of the other forums (DBA or SQL).
3. I mean create synonyms on DB1 for reports VIEWS in DB2.
Hope all is clear!

Securing my APEX application from theft.

Similar Messages

Maybe you are looking for