2013 runtime environment and Application Builder

Similar Questions

• page apex_admin not display for the runtime environment and application deployment using command-line

  Hello

  I installed APEX 4.2.6 EPG on Windows 7 Professional (32 bit) with Intel Core i3 processor.  Oracle XE 11.2 Win-32 DB.

  All the installation steps followed according to the Installation guide for the Apex.  It is a fresh and new installation.

  

  Install the log shows below -.

  Thank you for the installation of Oracle Application Express.

  Oracle Application Express is installed in the APEX_040200 schema.

  SQL > SELECT DBMS_XDB. GETHTTPPORT FROM DUAL;

  GETHTTPPORT

  -----------

         8082

  I did only the installation of runtime using apxrtins.

  ' Step ' grant of privileges of connection "according to the document was smooth without any problems.

  SQL > ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 20 scope = both;

  Modified system.

  SQL > ALTER SYSTEM SET SHARED_SERVERS = 5 SCOPE = BOTH;

  Modified system.

     

  I played "Creating a workspace manually" and met above question.  For installation of runtime, is this unnecessary step?  Or any other step I'm missing?  Help, please.

  Thank you and best regards,

  -Anand

  Hi Anand,

  anand_gp wrote:

  All the steps I did in my development environment and no problem following the steps.  And there is no question of the problem of the EPG or a bad image of loading because the other workspaces and applications out there are working well.  My question was, when I tried to copy an application via command line in an another 'new space and work with some new application ID', wheather my steps were correct?  If so, then why does not using the URL of the application.  And since it is in full flight development environment, where other workspace / applications work fine, how to connect to the new workspace I created using the command line?  If you look at my steps, I did provide any user name and password associated with this workspace all in creation.  When all this is going very well, so I will try in my new machine that has only run-time environment.

  Thank you

  -Anand

  I think you missed the validation part. You're going to make after the installation of the application as well as the addition of workspace

  commit;

  Hope that solves your problem.

  Kind regards

  Jitendra

• Report Generation Toolkit and Application Builder

  I'm going crazy trying to get out.

  I am trying to build an EXE using Application Builder program. The program uses the Office Report Generation Toolkit.

  I tried including the dynamic screw in the project, the computer development and the CD. I still have the same problem: the application does not start Excel. It's as if the commands are going into a black hole. It's not even an error message.

  I enclose my VI report for you to view. Any help is appreciated.

  
  

• Run the Application in the runtime environment

  Good afternoon
  
  I installed the full development and the APEX runtime environment and created an application. Now, I'm trying to figure out how to launch the application in the runtime environment...
  
  I searched the forum, but I did find something similar to this request... Or I ask the wrong question... Any help that can be provided will be greatly appreciated!
  
  Thank you in advance.
  
  Donald

  End users don't see that. You will see if you are connected to the development environment in the same browser session.

  Scott

• Management of an APEX with walk-APIs - it APEX runtime environment?

  People,
  
  APEX Version: 4.2.1
  Database EE 11 GR 2
  Listener: EPG
  
  TLDR: Go at the end of the question for this thread in bold.
  
  I work in an environment where we have maintained by Oracle Forms applications and Oracle APEX on a database only internal production data. We want to take a redacted together these data (PII or personal Identifiable Information removal) and some applications of the APEX and put them on a separate external server for public consumption. The internal production environment is running APEX with the runtime and development environments. The external server runs APEX with just the execution with the query, only the applications environment. While two of the external applications are public applications without authentication (both work very well), there is an application that will have a relatively small number of users who authenticate with the application to access more detailed information than the general public. Still no PII or something like that, a little more information. Users are users of workspace APEX. The three applications are in the same workspace.
  
  I have to assume that I'm not the only person with the above configuration, but I had a moment difficult to work right. Although the documentation does not have the API, it is not always clear which API you would use and why.
  
  For example, in the internal production environment when a user connects to the authenticated application, they get access to the application (if they are in the right group) or they get an error page indicating that they have no access to the application. In the external runtime application that they will always have a ' ORA-06550: line 4, column 55: PLS-00201: identifier ' WWV_FLOW_F4000_PLUGINS.» ' INTERNAL_4155_SESSION_SENTRY' must be declared ORA-06550: line 4, column 1: PL/SQL: statement ignored ' error, which "sort of" makes sense because the application referenced (4155) is part of the installation of development and is not included as part of the runtime install only (either by the way, this seems like a bit of an oversight on the part of the APEX team). It is pretty obvious that the export and import of the workspace (and its users) 'something' got zero and some type of password reset is requested. Of course, end-user password reset request is not included in a single installation of runtime...
  
  So, off to the API to see if I can "reset" on the single runtime installation external users so that they do not have to reset their passwords when first connecting. Wow... Lots and lots of API. Understand that you must set the security with the APEX_UTIL group id. SET_SECURITY_GROUP_ID API takes some time. After much wandering around, I settled on the apex_util API and the WWV_FLOW_USERS view as a good place to study...
  
  However, when we query the view WWV_FLOW_USERS on each side, all of the columns "expected" that one would expect because of this behavior are identical between the installation of development / internal enforcement and the only external runtime installation. Things like CHANGE_PASSWORD_ON_FIRST_USE and FIRST_PASSWORD_USE_OCCURRED are identical (and btw, not the values that you expect them to be... FIRST_PASSWORD_USE_OCCURRED is N for all users except the user ADMIN). The only values that differ between the two environments are as CREATED_BY, CREATION_DATE, LAST_UPDATED_DATE, and LAST_UPDATED_BY columns.
  
  Things that work just great:
  
  < li > the installation itself! Very easy to move backward between each environment (runtime only or runtime and development).
  < Li > integration with SQL/Developer is fantastic. It is very cool to be able to right-click on an application in the internal environment and deploy it to the unique runtime environment. Ideally, it would be nice to be able to move workspaces APEX in the same way.
  
  Things that do not seem to be large:
  
  < Li > when that documentation tells you what each API, it doesn't tell you why you want to use it, or what you would use it for. Having a section "useful use case" in the documentation would be great. Yes, there is the example of code (which of course does not mention that you need to set the id of Group of security for most of them to work), but the code example is not really tell you why and what each of the attributes you can set with her (for the API set for example) will actually... For example the documentation does not really that many fields are not yet used, and even if the values are the exact opposite of what you would think they would be.
  
  So, my immediate question:
  
  What API will allow me to have users exported with a workspace to use applications that are authenticated in a single installation of runtime?
  
  And my follow-up question (s):
  
  You can actually use the API defined to manage a runtime environment and is at - it a good resource that explains the how and why rather than just the choice of the API.

  Well, after a lot of trying things, I finally had things to work.

  It seems that export and import a workspace "expires" users to your workspace. Despite the fact that, in the development environment / the ACCOUNT_EXPIRY (which is a date) has a whole bunch of different values and seems to work perfectly, when you import a workspace that the ACCOUNT_EXPIRY column is ready on the date you did import previous internal enforcement. For some reason, this is an indication that your account has expired at the time when you look at the WWV_FLOW_USERS table. Not one of the columns expected, but on the contrary this date column...

  So let's take a look at the [url http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35127/apex_util.htm#autoId126]Unexpire account of the workspace of the documentation procedure:]

  UNEXPIRE_WORKSPACE_ACCOUNT Procedure
  
  Unexpires developer and workspace administrator accounts and the associated passwords, enabling the developer or administrator to log in to a workspace.
  
  Syntax
  
  APEX_UTIL.UNEXPIRE_WORKSPACE_ACCOUNT (
      p_user_name IN VARCHAR2);
  
  Parameters
  
  Table 21-107 describes the parameters available in the UNEXPIRE_WORKSPACE_ACCOUNT procedure.
  
  Table 21-107 UNEXPIRE_WORKSPACE_ACCOUNT Parameters
  Parameter           Description
  
  p_user_name  The user name of the user account
  
  Example
  
  The following example shows how to use the UNEXPIRE_WORKSPACE_ACCOUNT procedure. Use this procedure to renew (unexpire) an Application Express workspace administrator account in the current workspace. This action specifically renews the account for use by developers or administrators to login to a workspace and may also renew the account for its use by end users to authenticate to developed applications.
  
  This procedure must be run by a user having administration privileges in the current workspace.
  
  BEGIN
      FOR c1 IN (select user_name from wwv_flow_users) loop
          APEX_UTIL.UNEXPIRE_WORKSPACE_ACCOUNT(p_user_name => c1.user_name);
          htp.p('Workspace Account:'||c1.user_name||' is now valid.');
      END LOOP;
  END;   
  
  See Also:
  "EXPIRE_WORKSPACE_ACCOUNT Procedure" and "WORKSPACE_ACCOUNT_DAYS_LEFT Function"
  

  It's very nice and all, but there are some things missing in the example above:

  (1) you must call the procedure of apex_util.set_security_group_id with the ID of the workspace you want to unexpire accounts.
  (2) you will need to issue a COMMIT for steps to engage the unexpire.

  Question: How are you supposed to know you need to do the above two steps?

  Take a look at what the API documentation has for the description of the SET_SECURITY_GROUP_ID procedure:

  SET_SECURITY_GROUP_ID Procedure
  Use this procedure with apex_util.find_security_group_id to ease the use of the mail package in batch mode. This procedure is especially useful when a schema is associated with more than one workspace. For example, you might want to create a procedure that is run by a nightly job to email all outstanding tasks.
  

  Note that there is no mention that you will need to call the SET_SECURITY_GROUP_ID procedure for almost all other API calls in the APEX_UTIL package (or at least many of them)...

• APEX 3.2 error upgrading of Runtime Environment

  After successfully after improved our development of 3.1.2 to 3.2 environment did us a upgrade of our production environment where only a runtime environment is installed.
  The statement was made following the documentation for installation/upgrade of the APEX

  SELECT * 
    FROM apex_030200.wwv_flow_upgrade_progress
   WHERE upgrade_error IS NOT NULL
  ;

  The result was the following:
  

  UPGRADE_ID UPGRADE_ UPGRADE_SEQUENCE UPGRADE ACTION UPGRADE_ERROR                                                         UPGRADE_COMMAND
  ---------- -------- ---------------- -------------- --------------------------------------------------------------------- ------------------------------------------------------------------
           1 19.03.09              704 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_PROJECTS to public
           1 19.03.09              705 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_ACC_PROJECTS to public
           1 19.03.09              706 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_ACC_TABLES to public
           1 19.03.09              707 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_ACC_FORMS to public
           1 19.03.09              708 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_ACC_RPTS to public
           1 19.03.09              709 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_ACC_QUERIES to public
           1 19.03.09              710 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_REV_FORMS to public
           1 19.03.09              711 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_REV_RPTS to public
           1 19.03.09              712 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_REV_QUERIES to public
           1 19.03.09              713 error on grant ORA-04042: procedure,function,package, or package body does not exist grant execute on APEX_030200.APEX_MIGRATION_REV_TABLES to public

  Since there was no error in the table when we went to our development environment, I have reviewed the install scripts.
  The first glance the ORA is a bit confusing because the objects are procedures, functions, packages or package bodies but views.
  These views are created only during the installation/upgrade a development environment.
  
  After you have selected the dba_registry

  SELECT version
       , status 
    FROM DBA_REGISTRY
   WHERE comp_id = 'APEX'
  ;

  the view of the dictionary said a valid installation of APEX. So I guess it's just a small bug with the runtime environment upgrade that could be ignored.
  
  Anyone have the same experiences during the upgrade of its execution environment?
  
  Big names
  
  Andreas

  Hi Andreas,

  Thank you for bringing This problem to our attention. As you said, this is a minor bug with an upgrade of the runtime environment and errors can be ignored.

  Mistakes refer to views that are not created during the installation/upgrade a runtime environment. The point of view of the Migration of applications are not part of a runtime installation, and that's why these errors should not be in the APEX_030200.wwv_flow_upgrade_progress table. Bug 8351256 has been noted to follow up this issue.

  Kind regards
  Hilary

• LV Application Builder: fixed error "the system cannot find the file specified."?

  Hi all

  I don't mind banging my head out of something that feels complex, but it's still frustrating to be baffled by something that seems simple... I have LabVIEW 2014 and Application Builder. I've built a program that works perfectly as a VI, and then compiles and runs without fault as a .exe. But I can't get the installer to work. I get the following error:

  

  The suggestions in this thread and this KB article, I created a new specification to build installer, then a new application build spec, then a new project with all my screws in, build and test setup at each stage. None of this seems to make a difference.

  I ran the installer as an administrator, I created the Advanced installation directories (in which case it does not have the privileges to create folders) and built an installer without the performance in. None of this worked either. Finally, I played a bit with put all my subVIs in a library.

  So I guess it's a quirk in my program from the tutorial worked. Does anyone have any experience or advice on what specific aspects of a piece of Nice program with AB installers? It is a primary VI, less than a dozen, some Type Defs and no material integration subVIs. Seems to be a program fairly simple and straightforward, but maybe something in it is persona non grata with Application Builder?

  Are you running in deep subfolders with long folder names and file names? Perhaps some of the paths are getting too much time managing?

• Application Builder error

  Hello

  I use LV 8.6 and Application Builder. My Labview vi uses some third party vi to control a linear motor. The vi works well not respected. Can I complie an exe without errors, but when I run the exe, (on the same PC), I get the below error. (Connect.vi is the third party VI used to start communication with the motor). In this case with my vi and vi example of a third. I also have an exe from one of the vi from the engine supplier that works.

  On the error, I don't know why he mentioned NEITHER-488, I've never used (I don't think) so why it causes an error?

  Thank you

  Richard

  

  
  

• 2013 Runtime will run 2009 applications?

  I installed the Runtime 2013 (32 bit) and tried to launch an application 2009 (32-bit) (double click on the app). It did not work.

  Are not engines not backward compatible?

  Thank you

  Jeff

  No, you must install the corresponding to the version of LabVIEW runtime engine used for the build. You can install more than one version, and the executable file will automatically use the right one.

  In your case, you need to install both versions of the runtime: 2013 (32 bit) and 2009 (32-bit)

• steps to update of application in the development environment runtime environment

  Hello

  I have APEX 4.2.6 development environment and same version runtime environment.  There is little change, which happened in the forms and the underlying objects in the DB (developing approx.).  Help me please in the list of the steps needed to apply these changes to the runtime approx.  To my knowledge, I should 1st sync DB objects and then take application export development and import at run time.

  Can you let me know how to synchronize objects DB?  Dump export and import is not possible because "runtime" environment has the most recent data changes.  Otherway is to make changes to the DB object individually and manually.  Is it possible that this can be done using scripts/tools?

  And what about import application?  Is it just connect to the 'runtime' DVRs. SQLPLUS and run @f110.sql?  Please let me know the exact steps.

  Thank you and best regards,

  -Anand

  Hi anand_gp,

  You mean (for the import of application), I need to execute all the steps below to update the existing application (get the workspace ID, approx. set ID, etc.,)?

  And thank you to provide links on how to modify objects in the DB.  I'll go through them.

  Yes, and it will create a new application in your workspace.

  If you want to have the same id of the application (whether it is your production application), you can delete the existing application using APEX_INSTANCE_ADMIN. REMOVE_APPLICATION (remember to commit after each step) and then import with above in the light of the steps.

  If you want to have both the old and the new application in your production work space, you can use the alias of the application while publishing the URL.

  When you deploy a new version of the application, simply change the alias of the application, so that it becomes your current application.

  I hope this helps!

  Kind regards

  Kiran

• Application upgrade to sqlplus in the "Runtime environment".

  Hello
  
  We have a production server to top "Runtime environment" installed 4.0.2. It wasn't a problem to import our application for the first time in SQLplus by running the sql export script. But when we try to update already installed the application in SQLplus with a new version, we get an error:
  
  SQL > @c:\f101.sql;
  REQUEST 101 - test.xxx
  Set credentials...
  Check the compatibility...
  Last API extended: 20100513
  Your current Version: 20100513
  This import is compatible with the version: 20100513
  COMPATIBLE (you should be able to perform this import without problem).
  Set Application ID...
  Start
  *
  ERROR on line 1:
  ORA-20001: 101 Application has not been deleted. Import will not be attempted.
  ORA-06512: at "APEX_040000.WWV_FLOW_API", line 327
  ORA-06512: at line 4 level
  
  How we solve this problem?
  
  NOTE:
  (1) We MUST import the application with the same app ID,
  (2) we cannot use SQL Developer or Web management interface (this is installation of Runtime Environment) - the SQLplus is one option
  
  Many thanks in advance,
  Alexander

  OK, nevermind, I think I know what the problem is. I tried it in the sql workshop and that's why it worked for me.

  To do it (with the name of your workspace):

  DECLARE
  l_ws NUMBER: = apex_util.find_security_group_id('NAMEOFYOURWORKSPACE');
  BEGIN
  wwv_flow_api.set_security_group_id (l_ws);
  wwv_flow_api.remove_flow (101);
  END;

• Application Builder takes a lot of time and the Popup messages during construction

  Hi all

  My request is slightly larger with over 300 of VI. Between the build process that I receive pop-up messages requesting files from the library GMath etc... are changes u want to save the files... ? When you click on OK button it starts to save these files of the library and when he saves nearly half the number of files in the grave application builder fails and causes LabVIEW close. As the build process takes more than 2 hours and the final result is always a unsuccessful construction due to the accident of application builder I am wasting my time.

  Kind regards

  Pavan

  Here's what I'd do:

  • Open the main VI
  • Press Ctrl + Shift + Run to recompile all the screws in memory
  • Wait until the end
  • Save all the

  If there is, repeat for each dynamic called screw

• How can I remove J2SE Runtime Environment 5.0 update 11. Application of transformation error when you use Add/Remove programs

  Cannot remove J2SE Runtime Environment 5.0 update 11 or Java or Java 2 Runtime Environment SEv1.4.2_6.

  Add/Remove Programs DOES NOT WORK.  Message received when you try to remove programs is, "error application of transformations".

  Java (TM) 6 Update 21 is installed on my computer.

  Please let know us the step by step procedure to remove the old Java programs.  Thank you.

  E-mail address is removed from the privacy *.

  use revo uninstaller

• Possible to set the availability of applications in a runtime environment only?

  Hello
  I use apex 4.1.1.00.23.
  I wonder if it is possible to 'freeze' a production application APEX in an installation of runtime only, during an upgrade. I want to prevent strange behavior for logged in users. In the application builder, you can set the availability of the application. I thought antinutritionnel the application during the upgrade. Is this possible in a single TERM env? How? Or (better) alternatives?
  Thanks in advance.
  JB

  Hello

  Try this statement:

  begin
     wwv_flow_api.set_security_group_id(apex_util.find_security_group_id(''));
     wwv_flow_api.set_flow_status(, 'UNAVAILABLE');
  end;
  

  Kind regards
  Erik-jan

• Application Builder «Browse to LabVIEW.exe» error

  LabVIEW gurus...

  I'm currently building a standalone version of my project.  When I run the application (which is built successfully), LabVIEW makes me search the LabVIEW.exe file.  However, I want this application to run on a computer that will not have installed LabVIEW, and looking up if this file is not an option.

  I know that the reason for this problem is that I use 2 named StrLen and MoveBlock within the library LabVIEW.exe call library functions (to access data from a pointer to a pointer).

  LabVIEW.exe presents itself as one of the dependencies in my project, but I can't understand how to add it to my specifications of generation.  I tried to build a Setup program and include the LabVIEW runtime environment, but this does not work either.

  Any suggestions would be greatly appreciated!

  I'm using LabVIEW 8.6.

  Thank you

  Jason

  In the call to the dll just type LabVIEW without any path. This should work (I used it on 7.1) to automagicallylink it.

  The functions are also in the lvrt.dll which is the main part of the runtime engine.

  Felix