8 Deployment

Manual Deployment

This model requires two steps to deploy your code:

• Export the generated code to a file

• Load the exported file manually to the target application schema

This model enables you to use the development environment to modify (if application is receiving data) or build upon (if application is sending data) the generated PL/SQL code. The file export mechanism is also useful for storing the final PL/SQL code in source control systems. To export stored procedures:

1. In iStudio, click the Deploy tab.

2. Right-click Applications, and select Export PL/SQL. The Export Application dialog box is displayed.

   
   Description of the illustration 8_1.gif
   
   

3. Select the messages to export. Messages can be filtered as follows:

   • Export all messages: Select Applications at the top of the directory.

   • Export all messages of a certain type for all applications: Check All Applications, then select one or more types of messages to export.

   • Export all messages for a specific application: Select the application name.

   • Export all messages of a certain type for a specific application: Select the type under the application name in the directory.

   • To export specific messages: Select the messages by name. To select more than one message or class of messages, click the application.

4. Enter the name of the file to contain the exported stored procedures in the File Prefix field. The name generates multiple files.

   To view the directory page, click Browse.

5. Click OK. The stored procedure is now exported to a text file, which is stored in the user-specified directory (iStudio directory by default), on your computer.

6. Load the exported file into the target schema. The exported PL/SQL file is deployed for the selected application.

Auto Deployment

This option enables you to deploy the PL/SQL from iStudio, using the Deploy PL/SQL Wizard.

To deploy PL/SQL stored procedures from iStudio:

1. Click the Deploy tab in the iStudio window.

2. Right-click a database application and select Deploy PL/SQL. The Deploy PL/SQL - Select Events/Procedures dialog box is displayed.

   The application list displays the published/subscribed events and invoked/implemented procedures.

   
   Description of the illustration deploy1.gif
   
   

3. Select the application, event, or procedure to deploy the corresponding PL/SQL.

   
   Description of the illustration deploy1a.gif
   
   
   
   

   Note: You can deploy PL/SQL code either for one application at a time or at a message level.

   
   

4. Click Next. The Deploy PL/SQL - Database Information dialog box is displayed. This page enables you to specify the database connection information for deploying the PL/SQL code.

   
   Description of the illustration depdatabase.gif
   
   

5. Enter information in the following fields:

   • Database username: The database user name required for connecting to the database.

   • Database password: The password required for connecting to the database.

   • Database URL: The URL of the database required for connecting to the database. The URL should be in the form: host:port:SID.

6. Click Next. The Deploy PL/SQL- Summary dialog box is displayed, which displays a summary of the database connectivity information entered in the previous dialog box.

   
   Description of the illustration deploy3.gif
   
   

7. The Deploy PL/SQL - Summary dialog box displays the following:

   • Database Information

   • Selected Events/Procedures

     This page displays a list of selected packages and the corresponding procedures contained in those packages that you have selected for deployment. The status of each package is displayed in parenthesis next to the package name.

     
     

     Note: The status can be any of the following: Not deployed Package Status Unknown Previously Deployed Previously Deployed, but package specification invalid Previously Deployed, but package body invalid Previously Deployed, but package specification and body invalid

     
     

8. Click Next. The Deploy PL/SQL - Status dialog box is displayed.

   
   Description of the illustration deploy4.gif
   
   

   The Status dialog box displays:

   • A non-editable table: A table that displays the packages of the corresponding application, event, or procedure selected for deployment, and the current status of the package.

   • A Stop At First Error checkbox: If this option is checked and multiple packages are being deployed, then the deployment process will stop after encountering the first error. You will be prompted whether you want to continue with the deployment of the remaining packages or not.

9. Click Deploy. The generated PL/SQL is deployed for the selected application, event, or procedure.

   After the deployment is complete, the status of the PL/SQL deployment process is displayed. If an exception is thrown during the deployment process, then the exception is displayed. After deploying each package, the Status column is updated with success or error messages. The messages are:

   • Deployed successfully: The PL/SQL package was deployed successfully.

   • Deployed, but package specification invalid: The PL/SQL package was deployed. However, the status of the package specification in the database is invalid.

   • Deployed, but package body invalid: The PL/SQL package was deployed. However, the status of the package body in the database is invalid.

   • Deployed, but package specification and body invalid: The PL/SQL package was deployed. However, the status of both, the package specification and body in the database, is invalid.

   • Failed to Deploy: The PL/SQL package could not be deployed in the database.

   • Package status unknown: An error occurred while deploying the PL/SQL package in the database.