Migrating the CORBA server project written in COBOL language to the workbench.
A CORBA server project written in the COBOL language can be migrated to the workbench with the following procedures.
Create an empty CORBA server project.
Select "File" > "New" > "Project" from menu bar, and then select "COBOL" > "CORBA server project" on the "New project" dialog box.
Project name and the target name are set to the same name as the project name to be migrated. On the "Skeleton Code Selection" page, select "Do not generate code" and click the "Finish" button.
Set the compiler options and the linker options for the created project.
When the compiler options, library name, linker options, and the IDL compiler options have been set in the original project to be migrated, select the same settings on the "Property" dialog of the project.
Copy the source files from the original project to be migrated.
In the Component Designer, open the original project to be migrated and confirm the source files (COBOL source file and IDL file) are displayed in the project display region. Then copy these source files from the folder of the original project to be migrated into the folder of the created project that is the migration destination. After confirming the source file, the Component designer can be closed.
the original project to be migrated:<Installation folder of old product>/AP/Projects/<project name>
destination of migration:<User's Document folder>/ Interstage Studio/<product version>/ workspace/<project name>
Note
In the folder of the original project to be migrated, those files that are not displayed in the project display region need not be copied.
When the workspace folder of the workbench has been changed from the default position, the (project name) folder under the workspace folder becomes the destination of migration.
Add the copied files to the project.
Right click the project from the dependency view, and select "Refresh" from the context menu. The copied files will be added to the "Other Files" folder.
Move the copied files to the "Source File" folder.
Select the copied files from "Other File" folder, and execute "Add to Source File" from the context menu. These files will be moved from the "Other file" folder to the "Source File" folder.
Set the main program.
Open the "Source file" folder, select "(project name).cob" under it, and then execute the "Main program" from the context menu.
Compile the IDL file.
Select the existing IDL file in the "Source File" folder, and execute "Compile File" from the context menu. Before compiling IDL files, it is necessary to start Interstage Application Server and the service (basic service) required for the management of Interstage.
To start the basic service, use the Interstage basic service operation tool. To start the tool, select "Interstage"> "Studio" > "Interstage Base Service Operation Tool" from the start menu.
To start Interstage Application Server, use the Interstage management console.
Move the skeleton file to the "Source File" folder.
If the IDL file has been compiled, COBOL source files and COBOL library files that act as stub and skeleton are generated in the "Other File" folder.
Move these files that act as the skeleton to the "Source File" folder. Move the following files to the "Source File" folder using the same procedures above.
Interface file: (module name)-(interface name).cob
Helper class file: (module name)-(interface name)--HELPER.cob
Narrow skeleton file: (module name) - (interface name) _ NARROW.cob
Tie class file: (module name)-(interface name)--TIE.cob
Implementation registration file: (module name)-(interface name)--NEW.cob
Data type class file: (data type name).cob
Data type Helper file: (data type name)--HELPER.cob
Note
Do not move the library file (*.cbl) and stub file (*--stub.cob,*--NarrowStub.cob) to the "Source Files" folder.
Troubleshooting CORBA Application
Problems related to CORBA Application
Action
To compile the IDL file, the service (management service) required for the management of the Interstage Application Server and Interstage must be started in advance. If it has not started, start it first. To start the management service, the Interstage Management Service Operation Tool is used. To start the tool, select "Interstage" > "Studio" > "Interstage Management Service Operation Tool" from the start menu. To start the Interstage Application Server, the Interstage Management Console must be used.
Action
Although environment setup is not required when the server function of Interstage Application Server is used in combination with development work, it is required when the client package is used in combination with development work.
To use the client package in combination with development work, the server to be accessed must be specified in the "Interstage-Application-Server-installation-folder"\odwin\etc\inithost file.
Action
If the host of the Interface Repository service is changed while workbench is running, the change is not reflected in the list of CORBA server objects as long as workbench remains active. If the host of the Interface Repository service has been changed, restart workbench.
Action
When a CORBA server project is being built, the main program name must match the project name. Do not change the main program from that in the default file.
The following error message is displayed in the Console view:
OD: Error: od51401:IDLparser: CORBA_Container_lookup function caused IDL: CORBA/StExcep/COMM_FAILURE: 1.0 in exception information. Minor code is 0x464a010a OD: Error: od51221:IDLc: IDLparser command error. Error code=4
Action
The IDL compiler is executed if the IDL file has been updated. The Build fails if attempted while Interstage Application Server is in the forced stop state because IDL compiler execution fails. In this event, use the Interstage Management Console to start Interstage Application Server, and re-execute build.
The following error message is displayed in the Console view:
OD: Warning: od51006:IDLinst: Any object::SAMPLE to be deleted was not found.
Action
If "Register to Interface Repository" is selected in the IDL compiler setup window, the IDL compiler first deletes existing information stored in the interface repository before saving new information. During the initial building of a project, no information is stored in the interface repository, so a warning message indicating a failure to delete stored information is displayed. The project is built successfully regardless of the warning message.
