Web Interface for Importing/Exporting
You can import and export app server CSV files via a web interface.
Importing
If you use the Integration Manager to upload a CSV file whose name ends in “.as.csv”, Oracle Transportation Management will assume that the content of the file adheres to the rules of AppServer CSV files, and will process it as such. An example of a file name would be “location.as.csv”, as opposed to “location.csv”.
Each row in the file is processed via the application server instead of directly against the database. This has the benefit of keeping the application server data-cache synchronized with the database.
This page is accessed via Business Process Automation > Integration > Integration Manager. See the Loading CSV Data via User Interface chapter for details about this page.
Errors encountered when importing are reported back to the screen.
Exporting
Care must be taken when exporting an AppServer CSV file due to the lack of support for where-clauses. You should be logged in as a user whose vpd_profile limits the number of rows selected from the entity you plan on exporting. Where-clauses will be supported in future releases. In the example below, the user is logged in as “GUEST.FEWROWS”. This user has a vpd_profile which limits the number of rows in the s_ship_unit table.
You can use the following URL to export (if it is not on your user menu):
https://hostname/servlets/glog.integration.servlet.IntegrationMenuServlet?integration_stylesheet=integration/csvexport.xsl
- In the command field, select the “as.xcsv” command.
- In the tableName field, specify an “EntityName” instead of a table name. In this case, the entity name is “SShipUnit” which differs from the database table name, which would be “S_SHIP_UNIT”.
- Click Run. Your output will then appear
- In your browser, select View > Full Screen.
- Right-click and select View Source. This will place the output in notepad so you can save it to a local file.