These two options will perform an extraction using the database extractor embedded into the CAST Delivery Manager Tool - connections are made using JDBC drivers. Use the table below to help fill in the required fields:
| Option | Description |
|---|
Host name | Your Oracle / DB2 server host name: either its netbios name or its IP address |
|---|
Port | - Oracle instance port number, as per Tnsname.ora file - usually 1521
- DB2 server port - usually 50000
|
|---|
| Instance Identification (Oracle) | Choose either: - Service as per Tnsname.ora file
- The SID (System ID) is the instance name as per Tnsname.ora file.
|
|---|
| Database (DB2) | The DB2 database name. |
|---|
| Credentials | Fill in the credentials for the target server: | User name | Oracle or DB2 user. |
|---|
| Password | Password for the user selected in the User name field. |
|---|
| Remember password | This option enables you to force the CAST Delivery Manager Tool to save the database access credentials you have entered above. Choosing an option or not has no impact on the extraction (i.e. the CAST Delivery Manager Tool can still access the required resources). However, if you are creating subsequent Versions of the same schemas on the same server, you can choose to store the password in which case you will not need to re-enter it. - Not stored > The credentials are not saved.
- Local > The credentials are saved in the user's local workspace on the current machine. Choose this option if you do not want the password to be available to other Delivery Managers.
- Server > The credentials are saved locally (as above) and are also synchronized back to the CAST AIC Portal (i.e. the Source Code Delivery Folder). Choose this option if you want the password to be available to other Delivery Managers.
|
|---|
|
|---|
| JVM Memory Size | The CAST extractors are Java based and require the use of the JRE JVM (Java Virtual Machine). This option allows you to configure the Maximum Java Heap Size of your JVM for use during the database/schema browse and extraction processes. By default 1GB of memory is allocated and in most scenarios this value can be left as it is. You may need to change the amount of memory allocated to the JVM if you are getting out of memory exceptions for the Java Heap Space when you either browse to select a database/schema or when you use the Package action to invoke the extraction - this can occur more specifically when attempting to extract a large single database/schema or multiple databases/schemas. Please increase the memory allocation until you no longer receive errors, however, please bear the following in mind: - 32bit JRE: If you are running the CAST Delivery Manager Tool via the CAST AIC Portal and have installed a 32bit JRE for this purpose, or when the CAST Delivery Manager Tool is launched from the CAST Management Studio (when it will use a 32bit JRE that is provided with the CAST installation), CAST recommends that you do not increase the JVM Memory Size value to above 2GB, otherwise you risk running out of system memory.
- If your database/schema extraction consistently runs out of memory despite having allocated the maximum possible with a 32bit JRE, you may need to ensure you are using a 64bit JRE to take advantage of increased memory availability. To do so, you must launch the CAST Delivery Manager Tool from the CAST AIC Portal, rather than directly from the CAST Management Studio (when it will use a 32bit JRE that is provided with the CAST installation). And before you do so, you must manually modify the shortcut to the CAST Delivery Manager Tool (available in the Windows Start menu) to replace the existing path to the 32bit JRE (C:\Windows\SysWOW64\javaws.exe) with your 64bit JRE path ("C:\Program Files\java\jre1.7.0_51\bin\javaws.exe" for example). You can add the -Xmx parameter (maximum memory allocation), that will allow the process to use the memory defined. The shortcut should now look similar to this:
"C:\Program Files\java\jre1.7.0_51\bin\javaws.exe" -Xmx4096M -localfile
"C:\Users\<user_name>\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\6\1c274146-29c73860"
|
|---|
| Repository Type | Vanilla or Project |
|---|
| Schema | Schema in which the PeopleSoft tables are stored:- Oracle USER name
- DB2 schema name
|
|---|
| PeopleTools version | Choose the appropriate PeopleTools version from the drop down list. |
|---|
