Right now the version for how to deploy the Agent on Windows without Cygwin. As I mentioned in my post “OEM 12c Agent Deoploy on Windows – no problem with Cygwin!” before, there are several and good reasons to look closer into Cygwin. The following Solution, I call it the dirty way, isn’t probably feasible for long-term deployment of several machines, but if it’s you choise, you’re welcome.
For that we create a compressed package from the available agent software on the OEM server. We move that package per FTP to the target host and unpack it. It follows the customization of the response file. Finally we set off the stuttering deployment. Sounds relatively simple – it is – when you leave the stumpling blocks. Here it goes …
At first you need the agents deployment sofware. You will only get these over the Self Update Service of the Enterprise Manager in opposite to earlier releases. Choose the required OS platform and load the software. In our case Agent Software (188.8.131.52) for Microsoft Windows x64 (64-bit). This works for both Windows Server 2008 and also Windows Server 2012. An 32-bit versions for older Windows versions is also available.
Setup > Extensibility > Self Update > Agent Software
At first we check the available packages on the OEM server:
$OMS_HOME/bin/emcli login -username=sysman -password=****** Login successful $OMS_HOME/bin/emcli get_supported_platforms ———————————————– Version = 184.108.40.206.0 Platform = Microsoft Windows (32-bit) ———————————————– Version = 220.127.116.11.0 Platform = Microsoft Windows x64 (64-bit) ———————————————–
You have to create a directory for the compressed agent software on the OEM server.
Emcli needs the path to the zip-binaries in a variabale for package creation.
Pakage creation follows. Destination should your software directory. You can take the particular platform and destination description from the first query. At the end the package has a size of almost 260 MB.
$OMS_HOME/bin/emcli get_agentimage -destination=”/u03/software/agent12c_win_x64″ -platform=”Microsoft Windows x64 (64-bit)” -version=18.104.22.168.0 === Partition Detail === Space free : 3 GB Space required : 1 GB Check the logs at /u01/app/oracle/product/12.1.0/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2014-12-19_12-13-30-PM.log Downloading /u03/software/agent12c_win_x64/22.214.171.124.0_AgentCore_233.zip File saved as /u03/software/agent12c_win_x64/126.96.36.199.0_AgentCore_233.zip Downloading /u03/software/agent12c_win_x64/188.8.131.52.0_PluginsOneoffs_233.zip File saved as /u03/software/agent12c_win_x64/184.108.40.206.0_PluginsOneoffs_233.zip Downloading /u03/software/agent12c_win_x64/unzip File saved as /u03/software/agent12c_win_x64/unzip Agent Image Download completed successfully.
ll /u03/software/agent12c_win_x64 total 258260 -rw-r–r– 1 oracle oinstall 264452653 Dec 19 12:14 220.127.116.11.0_AgentCore_233.zip
Now you can move the package to the target host on the most suitable way of your choise e.g. FTP. I prefer WinSCP.
Choose an appropriate directory on your target host. The agent will be deployed in the upper directory, in my example in E:\app\oracle\agent.
Now we come to the customization of the Response Files. For that we queue the ports on the OEM first.
more $OMS_HOME/install/portlist.ini Enterprise Manager Upload Http Port=4889 Enterprise Manager Upload Http SSL Port=4903 Enterprise Manager Central Console Http SSL Port=7802 Node Manager Http SSL Port=7403 Managed Server Http Port=7202 Enterprise Manager Central Console Http Port=7788 Oracle Management Agent Port=3872 Admin Server Http SSL Port=7102 Managed Server Http SSL Port=7301
Now we can edit the response file.
Remove the Hash and add a valid value for <value unspecified>.
OMS_HOST=oem12c.carajandb.intra // Hostname OEM Server, fully qualified EM_UPLOAD_PORT=4903 // Enterprise Manager Upload Http SSL Port AGENT_REGISTRATION_PASSWORD=****** // Password for OEM access AGENT_INSTANCE_HOME=E:\app\oracle\agent\agent_inst // Agent Instnace Home AGENT_PORT=3872 // Standard Agent Port b_startAgent=true // start Agent after deploy ORACLE_HOSTNAME=stoermer.carajandb.intra // Target Host s_agentHomeName=agent12gR103 // Windows Servicename arbitrary
Unfortunately editing of the response file ist not enough. Also an entry of the AGENT_BASE_DIR value in the response file can’t protect the followeing error.
Invalid invocation. AGENT_BASE_DIR is mandatory.
What helps is an entry in the agentDeploy.bat itself.
Now we can execute the agentDeploy.bat as administrator and by declaring the complete path to the response file.
The stuttering part follows. We reach an appcrash warning. But deployment would’nt stop by clicking on “Close the program”.
It’s not very kind, but the deployment runs and with a bit patience and after a few minutes it’s completed. You will get information on the progress from the log – last line.
Agent deployment log location: E:\app\oracle\agent\core\18.104.22.168.0\cfgtoollogs\cfgfw\CfmLogger<timestamp>.log
Agent deployment completed successfully.
You should find the running agent in the Enterprise Manager now.