Migração Forms2Apex

Oracle Application Express - web application development tool (antigamente conhecido como Oracle HTML-DB)
Responder
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

Pessoal, Boooooooom dia =D
to meio sumido no forum já..

galera é o seguinte...
eu estou tentando fazer a migração de um forms simples, feito no 10g, para o Apex..
eu gero o _fmb.xml, porém quando vou importar para o Apex, ele dá um erro:

Selecionar tudo

ORA-20000: The file uploaded is not a valid Forms Module XML file.
estou procurando o porque deste erro, porém ainda não axei resposta nenhuma, não tem sentido isso, alguém sabe quando acontece este erro ??

o meu XML é basicamente isso:
Imagem

grato...
Avatar do usuário
dr_gori
Moderador
Moderador
Mensagens: 5024
Registrado em: Seg, 03 Mai 2004 3:08 pm
Localização: Portland, OR USA
Contato:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

Veja se o xml possui um "DUMP=ALL".
Se sim, você tem que gerar o xml sem essa opção!

Tem até um paper no metalink a respeito disso:

Selecionar tudo

Subject: 	ORA-20001 Error When Converting a Oracle Forms Application to Oracle APEX Application
  	Doc ID: 	801333.1 	Type: 	PROBLEM
  	Modified Date: 	16-APR-2009 	Status: 	PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:
Oracle Application Express (formerly HTML DB) - Version: 3.2
This problem can occur on any platform.
Symptoms

An Oracle Forms FormModule (FMB) file has been converted to XML, using the Oracle Forms to XML conversion tool, Forms2XML, in Oracle Developer Suite. On attempting to upload the generated XML into an Oracle APEX Forms Conversion project, the following error is thrown:

ORA-20001: 2. Forms XML file is not uploaded.
Cause
On inspection of the generated XML file (eg, opening it in a text editor such as WordPad), the second line contains the attribute Dump=”All”, similar to the following line:

<Module version="101020002" Dump="All" xmlns:APPLY_overridden="

Notice the attribute Dump="All". This indicates that when the FormModule file was converted to XML using the Forms to XML conversion tool, Forms2XML, the option DUMP=ALL was used as follows:

frmf2xml Test.fmb DUMP=ALL

This in effect creates an XML file with additional information which Oracle APEX is not expecting and hence, the ORA-20001 error.
Solution

Ensure that the DUMP=ALL option is not used when converting a FormModule file to XML, using the Forms to XML conversion tool, Forms2XML.
NOTE : This issue can also occur when trying to upload xml files for menu (mmb), object libraries (olb) modules.
References
Note 196924.1 - Forms XML Conversion Feature ( Converting Forms To XML)
[/quote]


Aproveito pra deixar outros textos bons a respeito :-)
[quote]Subject: 	Forms XML Conversion Feature ( Converting Forms To XML)
  	Doc ID: 	196924.1 	Type: 	BULLETIN
  	Modified Date: 	04-FEB-2009 	Status: 	ARCHIVED


PURPOSE
-------

This note discusses about the New Feature of Forms /XML conversion in Forms.

 

Converting the Forms to XML and vice versa
------------------------------------------
 
Forms / XML Conversion feature consists of four utilities: 

a) Convert an Oracle Forms Module into a specified XML format. 
b) Convert an XML file of that format into a Forms Module. 
c) Generate the Forms XML Schema. 
d) Validate an XML file or document against the Forms XML Schema. 


1.Converters
-------------

The utility's two converters are the Java classes Forms2XML and XML2Forms. 
The former traverses a module's object hierarchy and produces the XML.
In 10.1.2 the utility names are now frmf2xml.bat and frmxml2f.bat

The latter takes that well-defined format and converts it back into a module. 
Both tools can be invoked from the command line, taking a parameter of the file
name(s) to be processed. 
The classes are in the FORMS_HOME\forms90\java\f90xmltools.jar file.
or
FORMS_HOME\forms\java\frmxmltools.jar 

Simple examples: 

The easiest way to call these utilities is to use the scripts located in the 
FORMS_HOME\bin directory.

Converting Forms Modules to XML
-------------------------------

Syntax ->  iff2xml90 myform.fmb or iff2xml myform.fmb 

The script will accept .fmb, .olb and .mmb files.
Options: (default value in brackets)

DUMP=ALL/OVERRIDDEN dumps ALL properties or just those OVERRIDDEN (OVERRIDDEN)

OVERWRITE=YES/NO overwrite files that already exist (NO)

The output from iff2xml90 defaults to the filename with an underscore 
followed by the previous file extension, the new file has an extension '.xml'.

Examples:
---------

myform.fmb -> myform_fmb.xml
mymenu.mmb -> mymenu_mmb.xml
mylib.olb  -> mylib_olb.xml

Converting The XML Files Back To Forms Modules
-----------------------------------------------

Syntax ->  ifxml2f90 myform_fmb.xml or ifxml2f myform_fmb.xml

The output from the script strips the _fmb, _mmb or _olb from the 
filename and reverts the name back to the original name.

Options: (default value in brackets)

OVERWRITE=YES/NO overwrite files that already exist (NO)

PRINTTREE=YES/NO prints a forms object tree as the xml is parsed (NO)

USERID=database connection string - for record group queries (none)

Examples:
---------

myform_fmb.xml -> myform.fmb (assuming it was a FormModule)
my_form.xml    -> my_form.fmb (assuming it was a Form Module)
my_module.xml  -> my_module.mmb (assuming it was a Menu Module)
mymenu_mmb.xml -> mymenu.mmb (assuming it was a Menu Module) 

2. XML SCHEMA UTILITIES
------------------------

a) Schema Generator:
---------------------

   Schema Generator will output a .xsd file containing the XML Schema which 
all the XML files are validated against.

The .xsd file itself is not used to validate any XML files, a schema is 
generated 'on the fly' at validation time from the Forms metadata in the 
Jdapi.

The .xsd file is provided for the user to use separately from the tools in 
this package (e.g. with their own parser).

Syntax -> ifxmlsg90 or ifxmlsg : SchemaGenerator will output a .xsd file 
          containing the XML Schema which all the XML files are validated against.

b) XMLValidator:
---------------------

It can be used on the command line or called from Java to validate .xml 
files or XMLDocument Java objects respectively against the Forms XML Schema. 

Syntax -> ifxmlv90 test_fmb.xml or ifxmlv test_fmb.xml


Reference
----------

 Note 266576.1  Batch  Script for FMB to XML and XML to FMB
[/quote]


Este explica como converter todos forms pra XML atraves de um script
[quote]Subject: 	Batch Script for FMB to XML and XML to FMB
  	Doc ID: 	266576.1 	Type: 	SCRIPT
  	Modified Date: 	06-OCT-2008 	Status: 	PUBLISHED
Checked for currency 06-Oct-2008
 
Abstract

This script code converts the all the Forms modules residing in a directory to XML and vice a versa.
 

Product Name, Product Version
	Oracle Forms Developer,  9.0.X or higher

Oracle Reports Developer 9.0.X or higer

Platform 	Platform Independent
Date Created 	

26-MARCH-2004
 
Instructions

Execution Environment:
     Windows command prompt, UNIX shell

Access Privileges:
     Requires write privileges in the destination directory and read privileges in the source directory.

Instructions:
     When copying the script be aware to remove line feeds in the list of parameters for the executables.

     Please note that if you are FTPing this script from a Windows machine please do it in ASCII mode.

PROOFREAD THIS SCRIPT BEFORE USING IT! Due to differences in the way text 
editors, e-mail packages, and operating systems handle text formatting (spaces, 
tabs, and carriage returns), this script may not be in an executable state
when you first receive it. Check over the script to ensure that errors of
this type are corrected.

 
Description

The script is useful for the conversion of FMB to XML for file comparison, Changing properties of the forms, checking if the form has been corrupted. Checking the forms Builder created version
 
References

Note:196924.1 Forms XML Conversion Feature ( Converting Forms To XML)

Note:225247.1 Database Attached Libraries Are Lost after Converting FMB to XML
 
Script

========================For Windows===========================

Forms/Reports 9i

REM :WINDOWS: CONVERTS FORMS TO XML
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~			
::fmb2xml.BAT
cls 
REM CONVERTS FMB to XML 
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REM  You can set your PATH to %ORACLE_HOME%\bin
REM  You can set your PATH to %ORACLE_HOME%\bin
REM  Make ECHO ON to debug the problem and remove the REM to set the PATH explicitly.

ECHO  OFF
REM ::RunFix.bat 
REM SET ORACLE_HOME=D:\ORACLE\ids\bin
REM SET PATH=%ORACLE_HOME%\bin;%PATH%
REM SET CLASSPATH=d:\Oracle\iDS\formsxx\java\fxxxmltools.jar;d:\Oracle\iDS\formsxx\java\fxxjdapi.jar;d:\Oracle\iDS\lib\xmlparserv2.jar;d:\Oracle\iDS\lib\xschema.jar
REM formsXX : for 9.x -> forms90 or for 10.1.x -> forms
REM fxx : for 9.x -> f90 or for 10.1.x -> frm
ECHO %PATH%

Echo converting  Forms to XML....
	for %%f IN (*.fmb) do iff2xml90.bat  OVERWRITE=yes %%f 

REM for 10.1.x the batchfile name = frmf2xml.bat
ECHO FINISHED CONVERTING

DO STOP
ECHO Press Enter Key .......
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

REM :<-:<-:<-:<-:<-:<-:<-:<-Script End:<-:<-:<-:<-:<-:<-:<-:<-:<-

REM :WINDOWS: CONVERTS XML TO FORMS
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~			
::xml2fmb.BAT
REM CONVERTS XML to FMB 
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REM  You can set your PATH to %ORACLE_HOME%\bin
REM  Make ECHO ON to debug the problem and remove the REM to set the PATH explicitly.

cls 
ECHO  OFF
::RunFix.bat 
REM SET ORACLE_HOME=D:\ORACLE\9ids\bin
REM SET PATH=%ORACLE_HOME%\bin;%PATH%
REM SET CLASSPATH=d:\Oracle\iDS\formsxx\java\fxxxmltools.jar;d:\Oracle\iDS\formsxx\java\fxxjdapi.jar;d:\Oracle\iDS\lib\xmlparserv2.jar;d:\Oracle\iDS\lib\xschema.jar
REM formsXX : for 9.x -> forms90 or for 10.1.x -> forms
REM fxx : for 9.x -> f90 or for 10.1.x -> frm
ECHO %PATH%

Echo converting  XML to Forms FMB....
	for %%f IN (*.xml) do ifxml2f90.bat  userid=SCOTT/TIGER@MyDB OVERWRITE=YES %%f  
REM  For record group queries  	for %%f IN (*.xml) do ifxml2f90.bat USERID= OVERWRITE=YES %%f  

REM for 10.1.x the batchfile name = frmxml2f.bat
ECHO FINISHED CONVERTING
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

REM :<-:<-:<-:<-:<-:<-:<-:<-Script End:<-:<-:<-:<-:<-:<-:<-:<-:<-

=====================For UNIX=================================

Forms/Reports 9i

# UNIX CONVERTS FORMS TO XML
#UNIX  FMB2XML
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~			
::fmb2xml.sh
clear
# CONVERTS FMB to XML 
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#  You can set your PATH to $ORACLE_HOME/bin
#  Make ECHO ON to debug the problem and remove the REM to set the PATH explicitly.

# export ORACLE_HOME=/opt/ORACLE/ids
# export PATH=$ORACLE_HOME/bin:$PATH
# export CLASSPATH=$ORACLE_HOME\formsxx\java\fxxxmltools.jar;d:\Oracle\iDS\formsxx\java\fxxjdapi.jar;$ORACLE_HOME\lib\xmlparserv2.jar;$ORACLE_HOME\lib\xschema.jar
REM formsXX : for 9.x -> forms90 or for 10.1.x -> forms
REM fxx : for 9.x -> f90 or for 10.1.x -> frm

# ECHO $PATH

Echo converting  Forms to XML....
	for f in `ls *.fmb` 
	do iff2xml90.sh  OVERWRITE=yes $f 
	done
REM for 10.1.x the batchfile name = frmf2xml.sh
ECHO FINISHED CONVERTING
ECHO Press Enter Key .......
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

# :<-:<-:<-:<-:<-:<-:<-:<-Script End:<-:<-:<-:<-:<-:<-:<-:<-:<-

#UNIX CONVERTS XML TO FORMS
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~			
::xml2fmb.sh
# CONVERTS XML to FMB 
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#  You can set your PATH to $ORACLE_HOME/bin
#  Make ECHO ON to debug the problem and remove the REM to set the PATH explicitly.

# export ORACLE_HOME=/opt/ORACLE/ids
# export PATH=$ORACLE_HOME/bin:$PATH
# SET CLASSPATH=$ORACLE_HOME\formsxx\java\fxxxmltools.jar;d:\Oracle\iDS\formsxx\java\fxxjdapi.jar;$ORACLE_HOME\lib\xmlparserv2.jar;$ORACLE_HOME\lib\xschema.jar
REM formsXX : for 9.x -> forms90 or for 10.1.x -> forms
REM fxx : for 9.x -> f90 or for 10.1.x -> frm
# ECHO $PATH

Echo converting  XML to Forms FMB....
	for f IN  `ls *.xml` do ifxml2f90.sh  userid=SCOTT/TIGER@MyDB OVERWRITE=YES $f  
REM for 10.1.x the batchfile name = frmxml2f.sh

ECHO FINISHED CONVERTING
REM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#---:<-:<-:<-:<-:<-:<-:<-:<-Script End:<-:<-:<-:<-:<-:<-:<-:<-:<-
 
 
Disclaimer

EXCEPT WHERE EXPRESSLY PROVIDED OTHERWISE, THE INFORMATION, SOFTWARE,
PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS. ORACLE EXPRESSLY DISCLAIMS
ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NON-INFRINGEMENT. ORACLE MAKES NO WARRANTY THAT: (A) THE RESULTS
THAT MAY BE OBTAINED FROM THE USE OF THE SOFTWARE WILL BE ACCURATE OR
RELIABLE; OR (B) THE INFORMATION, OR OTHER MATERIAL OBTAINED WILL MEET YOUR
EXPECTATIONS. ANY CONTENT, MATERIALS, INFORMATION OR SOFTWARE DOWNLOADED OR
OTHERWISE OBTAINED IS DONE AT YOUR OWN DISCRETION AND RISK. ORACLE SHALL HAVE
NO RESPONSIBILITY FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR LOSS OF DATA THAT
RESULTS FROM THE DOWNLOAD OF ANY CONTENT, MATERIALS, INFORMATION OR SOFTWARE.

ORACLE RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES TO THE SOFTWARE AT ANY
TIME WITHOUT NOTICE.

 
Limitation of Liability

IN NO EVENT SHALL ORACLE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE,
DATA OR USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN
CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE OF, THE SOFTWARE.

SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY.
ACCORDINGLY, SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

aooo vlw

vou testar qui....
eu tinha procurado no metalink mais acho qui procurei errado =D

vlwwww
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

cara, vlw pela ajuda
mais aqui não funcionou também...

eu não uso esse DUMP=ALL para transformar para XML

e o erro, acontece até para os XML´s dos arquivos de exemplo da Oracle.
Para funcionar essa migração ai, tem que instalar alguma coisa a mais no Apex ??
Avatar do usuário
dr_gori
Moderador
Moderador
Mensagens: 5024
Registrado em: Seg, 03 Mai 2004 3:08 pm
Localização: Portland, OR USA
Contato:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

Estranho. Teu forms já foi criado no 10g. Caso ele fosse de uma versão mais antiga, é sugerido antes converter o forms pra 9i ou 10g e depois transformar pra XML.

Já tentou criar o forms com DUMP=OVERRIDEN ?

Outros links interessantes:

Converting an Oracle Forms Application
http://download.oracle.com/docs/cd/E143 ... m#CHDEBFAD

Conversions Between Forms and XML Formats
http://www.oracle.com/webapps/online-he ... /vtTopicId./
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

=/

já tinha lido esses documentos antes....
não sei mesmo o porque do erro, já instalei em 2 bancos diferentes e o mesmo erro acontece....

a versão dos meu bancos são 10.2.0.4.0, e a versão do meu IDS é 10.2.0.2
meu Apex é a ultima versão 3.2, o banco e o Apex estão instalados em Linux, o apex funciona no IAS 10.2.0.2 Linux e no Windows a mesma coisa...

vou instalar o IDS 10.1.2.3 para ver se a versão do FRMF2XML é diferente...
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

é galera
não consegui resolver este problema...

vou abrir uma S/R no metalink, e se eles resolverem eu posto aqui...
o que eu fiz agora, foi cria um outro banco em VMWare e instalar o Apex..
ai deu tudo certo....
VLW
Avatar do usuário
dr_gori
Moderador
Moderador
Mensagens: 5024
Registrado em: Seg, 03 Mai 2004 3:08 pm
Localização: Portland, OR USA
Contato:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

Tai algumas coisas inexplicaveis.
Eu instalei o XE no Ubuntu 9.04, e o banco starta. Mas não consigo acessar ele via WEB (porta 8080). Tudo esta configurado certo, eu procurei um monte na internet sobre isso e parece que a soução foi a mesma: Instalar denovo :-(
Avatar do usuário
Daniel_Azevedo
Rank: Programador Júnior
Rank: Programador Júnior
Mensagens: 19
Registrado em: Qui, 12 Nov 2009 1:19 pm
Localização: Caxias do Sul - RS
Daniel Azevedo
Analista de Sistemas
Oracle EBS
Oracle Apex
Forms, Reports, PL/SQL, Designer

e ai colegas! Qual ferramenta vocês estão utilizando para migrar seus forms para Apex?
gokden
Rank: DBA Pleno
Rank: DBA Pleno
Mensagens: 264
Registrado em: Dom, 19 Ago 2007 8:18 pm
Localização: Ribeirão Preto - SP
Lucas de Souza

OCA Developer
Analista de sistemas

no próprio Apex tem uma função que faz isso, qui é o Application Migration...

quando você loga no Apex no canto direito tem uma caxinha escrito Migration, e um escrito embaixo: Application Migration...

lá é um bom lugar para começar :D
Responder
  • Informação
  • Quem está online

    Usuários navegando neste fórum: Nenhum usuário registrado e 3 visitantes