the following is an operation memo when goldengate Director v2.0.0.3 is installed:
1. Install weblogic11g (internal version 10.3 or later) and configure it successfully. you can log on to the Weblogic management interface and publish a small application. 2. Install the goldengate server and client. The installation is simple. Follow the prompts on the page. 3. After the installation is complete, start the server and click "Start Oracle goldengate ctor" in the shortcut menu from the Start Menu. It is very likely that the black window will crash and disappear. If the above problem occurs, find the script from the menu and run it with cmd, so that it will not disappear automatically after the crash to capture the error information. The captured error message is (1) log4j: Error cocould not read configuration file from URL. This error roughly indicates that the log4j configuration file is missing. Solution: Run CMD in this shortcut as domain \ startweblogic in the installation directory. CMD, open the script file and find that it calls the file startweblogic with the same name in the sub-directory bin. CMD, open startweblogic in the bin directory. CMD edit. Find the path in the error prompt and replace it with./, because the current directory of this file contains a log4j configuration file. (2) The system prompts that port 7001 is occupied because Weblogic is already running, so the port is occupied. You need to stop the Weblogic service and then start "Start Oracle goldengate director ". In fact, goldengate automatically starts the Weblogic service. 4. after the installation is complete, enter http: // hostname: 7001/acon in the browser. Normally, the logon interface appears. In the logon box, enter the username and initial password admin, you should be able to log on smoothly. 5. when logging on to the Oracle gdsc admin tool, enter the user name and password admin/admin, enter the machine name or IP address for the server, and add the colon and port number. If you do not enter the port number, the error message "failed to get login context" is displayed. perhaps your ETC/gdsc-client-login.conf file is missing...