Oracle SOA URL´s

All possibles URL´s for Oracle SOA applications.


They are:

• Console - http://localhost:port/console
• EM console for BPEL - http://localhost:port/em 
• OSB console - http://localhost:port/sbconsole
• Human task application - http://localhost:port/integration/worklistapp
• Rules composer - http://localhost:port/soa/composer

TIP: If you don´t know which values for localhost and port, ask it to your SOA Admin.

Those information are in SOA console, looking for servers information.

Setting Up UMS Drive on SOA Server 11g

Some information about the content of this post

For some changes described bellow you will need to restart the SOA Server. My suggestion for you is make the necessary changes and restart the server once time.

All problems founded here while I was doing this setup were resolved with the steps defined follow.

The configuration of the SOA server:

• Oracle Enterprise Manager 11g version 11.1.1.6.0;
• WebLogic Server version 10.3.5.0.

The UMS drive is not installed on SOA Server by default, so before you will start these steps will be necessary install the UMS drive. This step is very simple, you only need access the console in the path Console> Deployments >Install, and then choose component named "UMS Adapter.rar" and complete the necessary steps (next, next and next).

Developers: The JDeveloper tool has the UMS service installed, but this component is hidden by default. You need to change a file for see and use the UMS service in your composite. For do it you need to open the folder {Install_JDev11.1.1.6}\jdeveloper\integration\seed\soa\configuration, open the file "soa-config.xml" and modify the item ${UMS_ADAPTER_COMPONENT_NAME_L} removing the property "preview=true".

Creating JKS files (Identity and Trust). These files must be used to mantain the secure storage and management of private keys and trusted certificate authorities (CA's). For your better understanding look this link:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/security/ConfigureKeystoresAndSSL.html#WLACH03024.

Follow the steps bellow...

STEP 1: Acquiring the SSL certificates for future connections

Firstly you need to have Open-SSL installed and then you can to store the certificates in your local machine. Run the following sample command to see the result:

IMAP gmail server
openssl s_client -connect imap.gmail.com:993 >
imap-gmail.cert

SMTP gmail server
openssl s_client -connect smtp.gmail.com:465 >
smtp-gmail.cert

Tips: Existing others protocols what you can use to setup it, but in this case I will use the protocols SMTP for send messages and IMAP for receive messages. The ports used in this example were the default ports listed.

Copy the follow content after to run the openssl command line above for both files IMAP and SMTP certificates:

-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

After run the openssl command lines, you need copy the content lines between BEGIN CERTIFICATE and END CERTIFICATE as indicated above and past then in a notepad and save everything in files named imap-gmail.cert or smtp-gmail.cert according to content for each files.

STEP 2: Creating JKS (Java Keystore) files

Important: When weblogic is installed these files are created automatically, so you don't need to create new JKS files and then, you can jump this step and following to the next step. On the next step you will import the credentials created on step 1 for your JKS file, so if you choose not create the custom JKS files, you will need to know the password of this standard JKS files.

In this sample, we will create some custom JKS files for better show the complete setup about JKS files.

Exporting environment variable

Verify where is the default JDK path in your server and put it here!

For sample:

export JAVA_HOME=/vol01/oracle/product/11.2.0/jdk

echo $JAVA_HOME

Creating identity file

For understand the next commands, read more about it on the Oracle´s documentation: 
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html.

$JAVA_HOME/bin/keytool -genkey -alias PutHereYourServerName -keyalg RSA -keysize 1024 -validity 365 -keypass changeitnow -keystore  YourIdentityFile .jks -storepass  changeitnow  -dname "CN=PutHereYourServerName, emailAddress= PutHereYourMail , OU= PutHereYourOrgUnit , O= PutHereYourOrgName , L= PutHereYourCity , S= PutHereYourStateCode , C= PutHereYourCountryCode "

Options for dname parameter what you will replace:

• CN=commonName
• OU=organizationUnit
• O=organizationName
• L=localityName
• S=stateName
• C=country

Important: The password used in this syntax was the changeitnow, change it when you will execute this command line and, the file "YourIdentityFile .jks" was the name used in that sample.

Exporting root certificate

$JAVA_HOME/bin/keytool -export -alias PutHereYourServerName -file root.cer -keystore YourIdentityFile.jks -storepass changeitnow

Creating trust file

$JAVA_HOME/bin/keytool -import -alias PutHereYourServerName -file root.cer -keystore YourTrustFile.jks -storepass changeitnow

List all files

For you verify if your above commands works correctlly, run it commands: 
 

$JAVA_HOME/bin/keytool -list -v -alias PutHereYourServerName -keystore YourIdentityFile.jks  -storepass changeitnow

$JAVA_HOME/bin/keytool -list -v -alias PutHereYourServerName -keystore YourTrustFile.jks -storepass changeitnow

$JAVA_HOME/bin/keytool -printcert -file root.cer

STEP 3: Importing certificates into Weblogic's keystore

To import the certificates is very simple, you need use a Java tool named keytool used on previous steps. That command will put the certificate credentials acquired above into the JKS files.

$JAVA_HOME/bin/keytool -import -keystore YourIdentityFile.jks -alias gmail.com -storepass changeitnow -file smtp-gmail.cert

$JAVA_HOME/bin/keytool -import -keystore YourTrustFile.jks -alias gmail.com -storepass changeitnow -file imap-gmail.cert

 

Oracle SOA Gateway ou Oracle Integration Repository

Pessoal, isso é uma coisa legal que não vi ninguém usando por aí nos projetos, acho que alguns já ouviram sobre mas também não vou discorrer muito sobre o assunto, mas deixo links abaixo para quem desejar aprofundar mais sobre o assunto.

Na release 12c do EBS surgiu uma funcionalidade chamada Oracle iREP  ou Oracle SOA Gateway. Ele consistem basicamente em um catalogo fornecido pelo próprio Oracle EBS de interfaces dos domínios do EBS e mostra todos os objetos catalogados como: APIS e suas formas de uso, Webservices mapeados (gerados ou importados), tabelas, views, ou seja, uma seleta de objetos usáveis do Oracle EBS.

Todas os grandes pacotes disponíveis no mercado hoje tem a capacidade de transformar uma funcionalidade em serviço ou simplesmente ligar uma funcionalidade ao serviço sem muito desenvolvimento, o SAP faz isso usando componentes internos, o OTM importa serviço e liga ao processo sem muita customização, o próprio APEX tem funcionalidades deste tipo para gerar e importar serviços.

No Oracle EBS isso não era muito fácil de fazer e só era possível através de uma interface customizada com outro pacote. Este pacote permite que você simplesmente crie uma package e documente todos os seus objetos com os padrões da solução, usando algo parecido com a documentação Java DOC e importe no seu repositório, a partir disso você pode gerar um WSDL e um endpoint totalmente funcional, sustentado pelo server do próprio EBS e com regras de segurança, ou seja, transformar sua API em Webservice simplesmente sem gerar uma linha de código a mais, somente utilizando a solução. Acredito que isso agiliza muito o desenvolvimento.

Existem outras funcionalidades para exposição de objetos, politicas de segurança, importação de serviços externos, etc, vale a pena entender e aproveitar de algo disponibilizado para trazer controle e agilidade no processo de construção.

 Link que discorre sobre o assunto:

https://docs.oracle.com/cd/E26401_01/doc.122/e20923/T291171T329891.htm

Oracle User Guide document:

https://docs.oracle.com/cd/E18727_01/doc.121/e12064/T291171T466519.htm

Digital Signature on Oracle BPEL flow

Digital Signature on Oracle BPEL flow

Lately I created a Java code based on some blogs and forums what could found. This code is used into BPEL flow and it has some development premises:

• The file used for sign a XML file has the exclusive JKS-Java KeyStore format;
• The file used needs be posted on SOA Server (“${WEBLOGIC_DOMAIN_HOME}/security” folder). You can change the target folder for your codification, but you need modify this sample code in one exclusive point;
• The model for signature used is the X509 Signature on RSA SHA-1 Base64;

☛ Tip: This sample declare all path for java classes used, but if you want to define it in your BPEL code using follow syntax <bpelx:exec import="java.lang.String"/>, for your understanding see the document http://docs.oracle.com/cd/E25178_01/dev.1111/e10224/bp_java.htm#BGBEEEFB.

Defining Java Embedding code

/*                                    

   Digital Signature Algorithm (DSA)  

   Created by Eduardo Leite at 17-dec-2013                                    

*/                               

   try{                   

               java.lang.String JKSFile       =  (java.lang.String)getVariableData("vKeyStoreFile");  

               java.lang.String JKSAlias      =  (java.lang.String)getVariableData("vKeyStoreAlias");  

               java.lang.String JKSPassword   =  (java.lang.String)getVariableData("vKeyStorePassword");  

                 

               java.lang.String XMLinput      =  (java.lang.String)getVariableData("vXMLContent");       

                   

                  

               //Convert String to XMLDocument    

               javax.xml.parsers.DocumentBuilderFactory dbFactory = javax.xml.parsers.DocumentBuilderFactory.newInstance();     

               javax.xml.parsers.DocumentBuilder dBuilder = dbFactory.newDocumentBuilder();      

               oracle.xml.parser.v2.XMLDocument doc = (oracle.xml.parser.v2.XMLDocument)dBuilder.parse(new org.xml.sax.InputSource(new java.io.StringReader(XMLinput)));    

              

                     

               String providerName = System.getProperty("jsr105Provider", "org.jcp.xml.dsig.internal.dom.XMLDSigRI");                 

               javax.xml.crypto.dsig.XMLSignatureFactory fac = javax.xml.crypto.dsig.XMLSignatureFactory.getInstance("DOM", (java.security.Provider) Class.forName(providerName).newInstance());                 

                          

               javax.xml.crypto.dsig.DigestMethod digestMethod = fac.newDigestMethod(javax.xml.crypto.dsig.DigestMethod.SHA1, null);                 

               javax.xml.crypto.dsig.Transform transform = fac.newTransform(javax.xml.crypto.dsig.Transform.ENVELOPED, (javax.xml.crypto.dsig.spec.TransformParameterSpec) null);                 

               javax.xml.crypto.dsig.Reference reference = fac.newReference("", digestMethod, java.util.Collections.singletonList(transform), null, null);                  

               javax.xml.crypto.dsig.SignatureMethod signatureMethod = fac.newSignatureMethod(javax.xml.crypto.dsig.SignatureMethod.RSA_SHA1, null);                 

               javax.xml.crypto.dsig.CanonicalizationMethod canonicalizationMethod = fac.newCanonicalizationMethod(javax.xml.crypto.dsig.CanonicalizationMethod.EXCLUSIVE, (javax.xml.crypto.dsig.spec.C14NMethodParameterSpec) null);                 

                         

               // Create the SignedInfo                 

               javax.xml.crypto.dsig.SignedInfo si = fac.newSignedInfo(canonicalizationMethod, signatureMethod, java.util.Collections.singletonList(reference));                 

                         

               // Load the KeyStore and get the signing key and certificate.             

               //java.security.KeyStore ks = java.security.KeyStore.getInstance( "jks" );             

               java.security.KeyStore ks = java.security.KeyStore.getInstance(java.security.KeyStore.getDefaultType());             

               ks.load( new java.io.FileInputStream( "security/" + JKSFile ), JKSPassword.toCharArray());             

               java.security.KeyStore.PrivateKeyEntry keyEntry =             

                   (java.security.KeyStore.PrivateKeyEntry) ks.getEntry             

                       ( JKSAlias, new java.security.KeyStore.PasswordProtection( JKSPassword.toCharArray()));             

               java.security.cert.X509Certificate cert = (java.security.cert.X509Certificate) keyEntry.getCertificate();             

                   

               // Create the KeyInfo containing the X509Data.             

               javax.xml.crypto.dsig.keyinfo.KeyInfoFactory kif = fac.getKeyInfoFactory();              

               java.util.List x509Content = new java.util.ArrayList();             

               x509Content.add(cert.getSubjectX500Principal().getName());             

               x509Content.add(cert);             

               javax.xml.crypto.dsig.keyinfo.X509Data xd = kif.newX509Data(x509Content);             

               javax.xml.crypto.dsig.keyinfo.KeyInfo ki = kif.newKeyInfo(java.util.Collections.singletonList(xd));                              

               javax.xml.crypto.dsig.dom.DOMSignContext dsc = new javax.xml.crypto.dsig.dom.DOMSignContext(keyEntry.getPrivateKey(), doc.getDocumentElement());                

                          

               // Create the XMLSignature, but don't sign it yet.              

               javax.xml.crypto.dsig.XMLSignature signature = fac.newXMLSignature(si, ki);                 

               // Marshal, generate, and sign the enveloped signature.               

               signature.sign(dsc);                 

                    

               // Transform XMLDocument to String    

               javax.xml.transform.TransformerFactory tf = javax.xml.transform.TransformerFactory.newInstance();    

               javax.xml.transform.Transformer transformer;    

               transformer = tf.newTransformer();    

               java.io.StringWriter writer = new java.io.StringWriter();    

               transformer.transform(new javax.xml.transform.dom.DOMSource(doc), new javax.xml.transform.stream.StreamResult(writer));    

               java.lang.String XMLoutput = writer.getBuffer().toString();    

               setVariableData("vXMLContent", XMLoutput  );      

                           

               // Set output                       

               setVariableData( "vJavaErrorCode", "0" ); // Success                                

   }                 

   catch( Exception e ){                 

                                     

       setVariableData( "vJavaErrorCode", "2" ); // Error                    

       setVariableData( "vJavaErrorMessage", e.getMessage() );                    

               

       e.printStackTrace();                 

   }

Defining utilization about variables

• vKeyStoreFile – The name of the JKS file;
• vKeyStoreAlias – The alias of the JKS file;
• vKeyStorePassword – The password of the JKS file;
• vXMLContent – This variable will be store all content of XML;
• vJavaErrorCode – This variable will be return 0 for success, 2 for any error;
• vJavaErrorMessage – This variable will return error message when the variable vJavaErrorCode return the value 2.

  

Related Documents

Defining signature model X509 Base 64 - http://www.w3.org/TR/xmldsig-core/

Incorporating Java and Java EE Code in a BPEL Process - http://docs.oracle.com/cd/E25178_01/dev.1111/e10224/bp_java.htm#BGBEEEFB


Collaborator

Daiane Bitencourt

How do you export/import files from Oracle EBS R12.0.6 or highest using FND GFM utility

This post was dedicated to Oracle EBS developers!

During some days i'm trying to find any blog, note or post about the functionality export/import files from Oracle EBS, but can’t found nothing about it. I needed anything for make reference in my actual activity, so decided write a document explaining how about works the FND GFM utility for export/import files.

This functionality was used in Oracle EBS R12.0.6. The frontend is Oracle OAF, but you can to call that feature from Oracle Forms according of Oracle EBS’s architecture.

☛ IMPORTANT NOTE: very important know what only the content of the file will be imported to Oracle EBS Database on the an exclusive table. When you choose the file by the button “Browse” on this window, the functionality will copy the binary content of  your file and only the content will be stored on FND_LOBS table. Your file will not be removed from original repository.

Talking about this Oracle EBS feature, some points are important to clarify this context and understand what will be implemented in your program:

• The developer team don’t need to create anything for use it, that feature is incorporate on release R12 of the Oracle EBS;
• In the import functionality doesn’t remove your original file;
• Just only the content of file will be imported between your computer (any folder what your computer can access) to Oracle EBS database;
• By definition of that feature, the target table defined to receive the content of the file is named FND_LOBS.

For you implement this feature on your Oracle Forms program, you need to follow some steps how i’ll trying describe bellow:

1. Create a button in your program, because my sample will be based in a button. You can use any other component what you wish;
2. Create some messages for ask to user things how: "Do you want to import a file?", "Do you want to export of this file?", "File imported successfully", any message what you prefer to show for the user;
3. Apply the codes in your program how defined bellow. You need to reference the codes #3 (Import files) or #4 (Export files), the other codes (#1 and #2) are complementary in this case.

Defining code for call the Import/Export OAF page

Code #1: used to create file on FND_LOBS table.

   PROCEDURE file_p( p_file_id   in out fnd_lobs.file_id%type
                   , p_download  in boolean default true ) IS
     l_nAccess_Id  NUMBER;
     l_vServer_Url VARCHAR2(255);
     l_vUrl        VARCHAR2(4000);
     l_nButton     NUMBER;
   BEGIN
     --
     l_nAccess_Id := fnd_gfm.authorize( NULL );
     fnd_profile.get( 'APPS_WEB_AGENT', l_vServer_Url );
     --
     if p_file_id is null then
        l_vUrl := rtrim( l_vServer_Url, '/' ) || '/fnd_file_upload.displayGFMform?access_id=' || to_char( l_nAccess_Id ) || chr(38) || 'l_vServer_Url=' || l_vServer_Url;
     else
        l_vUrl := fnd_gfm.construct_download_url( fnd_web_config.gfm_agent, p_file_id, FALSE );
     end if;
     --
     fnd_utilities.open_url( l_vUrl );
     --
     IF p_download THEN
        -- 
        -- Ask to user what the download was completed
        --
        fnd_message.set_name( 'XXBOL','XXBOL_DOWNLOAD_COMPLETE' );
        l_nButton := fnd_message.question( button1     => 'YES'
                                         , button2     => NULL
                                         , button3     => 'NO'
                                         , default_btn => 1
                                         , cancel_btn  => 3
                                         , icon        => 'question' );
     ELSE
       -- 
       -- Ask to  user what the upload was completed
       --
       fnd_message.set_name( 'XXBOL','XXBOL_UPLOAD_COMPLETE' );
       l_nButton := fnd_message.question( button1     => 'YES'
                                        , button2     => NULL
                                        , button3     => 'NO'
                                        , default_btn => 1
                                        , cancel_btn  => 3
                                        , icon        => 'question' );                                    
     END IF;
     -- 
     IF p_file_id IS NULL THEN
        p_file_id := fnd_gfm.get_file_id( l_nAccess_Id ); 
     ELSE
        clear_file_p( p_file_id => p_file_id );
     END IF;
     --

   END file_p;

Code #2: remove files no more used from FND_LOBS table.

   PROCEDURE clear_file_p( p_file_id in fnd_lobs.file_id%type ) IS
   BEGIN
      --
      DELETE fnd_lobs
       WHERE file_id = p_file_id;
      --
      STANDARD.COMMIT;

   END clear_file_p;   

Code #3: exclusive use for open OAF page for import files

   PROCEDURE import_file_p IS
      CURSOR c_file( pc_file_id fnd_lobs.file_id%type ) IS
        SELECT file_data
          FROM fnd_lobs
         WHERE file_id = pc_file_id;
      l_rFile             c_file%ROWTYPE;
      --
      l_cFile             CLOB := empty_clob;
      l_nHeaderId         NUMBER;
      l_nSeqNumber        NUMBER;
      l_vErrorCode        VARCHAR2(50);
      l_vErrorMessage     VARCHAR2(3000);
      l_nRequestId        NUMBER;
      --
      l_nPos              NUMBER := 1;
      l_nFim              NUMBER := 1;
      l_nQtd_Chars        NUMBER := 1;
      l_vString           CLOB;
      l_nQtd_Occur        NUMBER := 4;
      l_nIndex            NUMBER := 0;
      l_nFile_Id          NUMBER := NULL;
      l_nButton           NUMBER;
      --
      l_nDest_OffSet      NUMBER := 1;
      l_nSource_OffSet    NUMBER := 1;
      l_nLang_Context     NUMBER := 0;
      l_nWarning          NUMBER := 1;
      l_nLobMaxSize       NUMBER := 18446744073709551615;
      l_nDefaultCSid      NUMBER := 0;
      --
   BEGIN  
      -- 
      -- Ask to user about the importation
      --
      FND_MESSAGE.SET_NAME( 'XXBOL', 'XXBOL_IMPORT_FILE' );     
      l_nButton := fnd_message.question( button1     => 'Yes'
                                       , button2     => NULL
                                       , button3     => 'No'
                                       , default_btn => 1
                                       , cancel_btn  => 3
                                       , icon        => 'question' );
      --
      IF l_nButton = 3 THEN 
          RETURN; 
      END IF; 
      file_p( p_file_id  => l_nFile_Id
            , p_download => FALSE ); 
      --
      DBMS_LOB.createtemporary( l_cFile, TRUE );
      --
      OPEN c_file( pc_file_id  => l_nFile_Id );
      FETCH c_file INTO l_rFile;
      IF c_file%NOTFOUND THEN
        CLOSE c_file;
        -- 
        -- Notify the user what no file was imported
        --
        FND_MESSAGE.set_name( 'XXBOL', 'XXBOL_NO_FILE_IMPORTED' ); 
        FND_MESSAGE.show;
        RETURN;
      END IF; 
      CLOSE c_file;
      --
      DBMS_LOB.ConvertToClob( dest_lob     => l_cFile
                            , src_blob     => l_rFile.file_data
                            , amount       => l_nLobMaxSize
                            , dest_offset  => l_nDest_OffSet
                            , src_offset   => l_nSource_OffSet
                            , blob_csid    => l_nDefaultCSid
                            , lang_context => l_nLang_Context
                            , warning      => l_nWarning );
      l_nQtd_Chars := DBMS_LOB.getlength(lob_loc => l_rFile.file_data ); 
      -- 
      clear_file_p( p_file_id => l_nFile_Id );
      --

   END;

Code #4: exclusive use for open OAF page for export files

   PROCEDURE export_file_p IS 
      l_vUserChoice     NUMBER;
      --
      l_vContentFile    CLOB;
      l_bFile           BLOB;
      l_vFileName       VARCHAR2(100);
      l_nDest_OffSet    NUMBER := 1;
      l_nSource_OffSet  NUMBER := 1;
      l_nLang_Context   NUMBER := 0;
      l_nWarning        NUMBER := 1;
      l_nLobMaxSize     NUMBER := 18446744073709551615;
      l_nDefaultCSid    NUMBER := 0;
      l_rFLOBS          fnd_lobs%ROWTYPE;
      l_nButton         NUMBER;
      --
   BEGIN  
      -- 
      FND_MESSAGE.SET_NAME( 'XXBOL', 'XXBOL_EXPORT_FILE' );     
      l_nButton := fnd_message.question( button1     => 'Yes'
                                       , button2     => NULL
                                       , button3     => 'No'
                                       , default_btn => 1
                                       , cancel_btn  => 3
                                       , icon        => 'question' );
      --
      IF l_nButton = 3 THEN 
          RETURN; 
      END IF;  
      -- 
      l_vFileName    := :HEADERS.LAYOUT_CODE || '.xls';
      l_vContentFile := get_excel_file_f;
      --
      -- create a temporary file
      DBMS_LOB.createtemporary( l_bFile, TRUE );
      DBMS_LOB.converttoblob( dest_lob     => l_bFile
                            , src_clob     => l_vContentFile
                            , amount       => l_nLobMaxSize
                            , dest_offset  => l_nDest_OffSet
                            , src_offset   => l_nSource_OffSet
                            , blob_csid    => l_nDefaultCSid
                            , lang_context => l_nLang_Context
                            , warning      => l_nWarning );
      -- 
      SELECT fnd_lobs_s.NEXTVAL
        INTO l_rFLOBS.file_id
        FROM DUAL;  
      --
      l_rFLOBS.file_name               := l_vFileName;
      l_rFLOBS.file_content_type       := 'application/octet-stream';
      l_rFLOBS.file_data               := l_bFile;
      l_rFLOBS.upload_date             := SYSDATE;
      l_rFLOBS.program_name            := 'XXBOL_EXPORT_EXCEL';
      l_rFLOBS.language                := USERENV( 'LANG' );
      l_rFLOBS.oracle_charset          := 'WE8ISO8859P1';
      l_rFLOBS.file_format             := 'IGNORE';          
      --
      INSERT INTO fnd_lobs VALUES( l_rFLOBS ); 
      --
      standard.commit;                 
      --  
      file_p( p_file_id => l_rFLOBS.file_id );                         
      --
      DBMS_LOB.FREETEMPORARY( l_bFile ); -- clear file

   END;

Defining messages for the above codification

Use the document related bellow on session "Related Documents" for understand the component FND Message of the Oracle EBS, because the codification do use this in all long code.

XXBOL_EXPORT_FILE
-----------------------
Do you want export this file?


XXBOL_IMPORT_FILE
-----------------------
Would you like to import a file?


XXBOL_DOWNLOAD_COMPLETE
-----------------------
Has the file been downloaded successfully?


XXBOL_UPLOAD_COMPLETE
-----------------------
The upload page must be opened and must be used for upload of your file.

Has the file been uploaded successfully?


XXBOL_NO_FILE_IMPORTED
-----------------------
No file imported. Please look for following instructions:

1 - File upload completed successfully on upload page.
2 - Please close the web browser.
3 - Return to the Attachments form and select the Yes button to indicate file upload is complete.

Related Documents

• Developer Guide creating messages for your customization, look on session 12 - Message Dictionary (at oct/2014).

Collaborators

Rodrigo Hataya
Daiane Bitencourt