OWSM server agent installation

Is it possible to install WSM server agents in other oc4j instances than the home instance? How? We've tried to find an option in the agent.properties, but no luck... Worse still, the installation script depends on libraries in the home instance for communicating with opmn.... The documentation only mentions changing the property file...

See this thread for the solution: How to secure web service deployed on a different servers using OWSM?

Similar Messages

After restart only one OWSM server agent is installed

I have created two OWSM server agents. One for the home container, the other for a custom container. (SOA Suite 10.1.3.3 - Basic install)
Whenever the Application Server is restarted, only the home container's server agent remains installed. I have to run wsmadmin.sh again to install the second agent before the custom container services are accessible again.
Is there any way to avoid having to do this?

Yes, there is a server agent for weblogic, see http://www.oracle.com/technology/software/products/web-services-manager/index.html to download it (see Third-Party Server Agents). The zip file also contains a pdf about the installation.
Kind Regards,
Andre

OWSM server agent for BPEL process in Weblogic

Hello,
We are trying to protect a BPEL process (in Weblogic) with a OWSM server agent, but we couldn't find clear guidelines on that.
OWSM 10.1.3.x is in one machine, and Oracle BPEL 10.1.3.x is in another, with Weblogic 9.2.
Can anyone give us instructions or tips on how to do this, considering this scenario?
Thanks a lot.
Daniel Viero.

Dave, Andre,
It's unfortunate that you were given incorrect information.
Let's take this issue offline by contacting me directly.
OWSM agent support for .NET was taken out as .NET was going through multiple revisions while 10.1.3.1 was being developed, and the old agent wasn't compatible with the new .NET versions; and there were resource restrictions on our part to keep up with the new version support.
While on this topic, I would like to hear from you and others what their thoughts are around this kind of support in a future release.
1. We could add back .NET agent (similar to 4.0.3)
2. We could manage the policies for .NET through Oracle Enterprise Manager while letting the .NET framework enforce them. This will allow for centralized management of policies, while leveraging the security stack of .NET for enforcement.
Which approach would you prefer?
Thanks,
Vikas Jain
http://ws-security.blogspot.com

BPEL Web Service with OWSM Server Agent NOT AUTHENTICATING

I have deployed OWSM Server Agent to enable WS-Security Username/Password Authentication following the steps in the below URL.
http://www.oracle.com/technology/obe/fusion_middleware/owsm/secure%20soa/securing%20soa%20with%20owsm.htm
Section: Creating and Installing an Oracle WSM Server Agent
The OWSM agent configuration is working fine with individual Web Services.
For BPEL, the authentication is not happening if we call the default endpoint from JAVA proxy or Soap UI e.g
http://host.domainame:7777/orabpel/bpelprocess1/050101 - Authenticates as per the OWSM policy and WORKS FINE
http://host.domainame:7777/orabpel/bpelprocess1 - Executes the process WITHOUT authenticating
Any help would be appreciated.
Thanks
Shehzad

Did you resolve this issue ? We are having same issue with one of our BPEL process ........ any help would be highly appreciated .....
Thanks in Advance

OWSM Server Agent custom steps

Can someone please lead me to a document and/or provide instructions that detail how to configure a custom step (like the one in C:\product\10.1.3.1\OracleAS_1\owsm\samples\customsteps) into an existing server agent policy as one of the pipeline steps. It's not obvious which option it is in the "Step Template" drop-down menu; unless I'm missing something; I'm also thinking the custom step (code/package) itself is a template and needs to be configured so that it appears in the pipeline "Step Template" drop-down.
Thanks in advance!

Found it.
http://www.oracle.com/technology/obe/fusion_middleware/owsm/custom%20steps/custom%20steps.htm

Oracle Audit Vault Server & Agent Installation Error.

Hi,
I am new to Audit vault. When I install Audit Vault on Windows 2008 R2 it throws an error after installing 99%. Kindly help me to resolve.
OS Version : Windows 2008 R2
Oracle Audit Vault Version: 10.2.3.2
Error:
Audit Vault Server:
INFO: Configuration assistant "Oracle Audit Vault Configuration Assistant" failed
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.3\av_1
Configuration directory is set to C:\oracle\product\10.2.3\av_1\cfgtoollogs. All xml files under the directory will be processed
INFO: The "C:\oracle\product\10.2.3\av_1\cfgtoollogs\configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.
INFO: Created a new file C:\oracle\product\10.2.3\av_1\cfgtoollogs\configToolFailedCommands
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.3\av_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.3\av_1\cfgtoollogs\configToolFailedCommands.bak
SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctly configured.
1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
2. Fix the errors causing these failures.
3. Select the failed assistants and click the 'Retry' button to retry them.
xception: VariableNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQu
Also while installing Collection agent, it throws the error while executing runInstaller.
OS Version : AIX 6.1
Oracle Audit Vault Agent Version: 10.2.3.2
Audit Agent:
bash-3.2$ ./runInstaller
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be 5200 or 5300
Failed <<<<
Exiting Oracle Universal Installer, log for this session can be found at /tmp/OraInstall2011-05-12_05-11-03PM/installActions2011-05-12_05-11-03PM.log
*/tmp/OraInstall2011-05-12_05-15-39PM>*cat installActions2011-05-12_05-15-39PM.log
Using paramFile: /finacle/avagent/aix_5l64/install/oraparam.ini
Checking installer requirements...
Checking operating system version: must be 5200 or 5300
Failed <<<<
Exiting Oracle Universal Installer, log for this session can be found at /tmp/OraInstall2011-05-12_05-15-39PM/installActions2011-05-12_05-15-39PM.log
Thanks & Regards,
Mithra.
Edited by: 864048 on Jun 7, 2011 2:57 AM

Hi ,
Please try the following:
Execute the setup in cmd with -ignoreSysPrereqs option.
Thank you.

SOLVED: OWSM Server Agent deployment to 'home' not 'oc4j_soa'

Hi
I've just installed an OWSM agent to manage my web services. By default it has installed it on the oc4j_soa oc4j, which makes sense as this is where BPEL and ESB processes get deployed.
However, my individual services, which I also want to secure are deployed to the 'home' oc4j. Can I change either where the web services are deployed or, additionally deploy an agent to this oc4j?
Any help would be most appreciated.
Chris
Change: Actually, I have changed the oc4j instance where I deploy the services to now, so this is no longer an issue!
Message was edited by:
chriseb
Message was edited by:
chriseb

Denis, Bas, Thanks for your replies.
Was out of the office yesterday.....I think this may be the way i was testing this.
If i try running my secured BPEL Process from the Test Page in OWSM or i try to initiate it from the BPEL Console it only works if i provide authentication info which is what i would expect ...however, if i try to initiate the secured BPEL process from another BPEL Process, i can invoke it without parsing any credentials!

Weblogic 81. portal server doesnot startup after the AM Agent installation

Hi,
I have a problem starting the weblogic server after I create the agent Authentication provider.
I have cross checked the CLASSPATH values and the JAVA_OPTIONS values.. it is correct
I get the following error
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authenticati:
[java.lang.ClassNotFoundException: Can't load class: com.sun.identity.agents.weblogic.AmAuthProvider]
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateIm)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManager)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelega)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManage)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDeleg)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Auth:
[java.lang.ClassNotFoundException: Can't load class: com.sun.identity.agents.weblogic.AmAuthProvider]
Please help!!!
-Karun

Have you specify relative path or full of weblogic startup script? How's permission for user invoking startup script?
Excerpt from the docs as below:
Startup Script Location: Enter the full path to the startup script that is used to start your BEA WebLogic Server instance.
Have you installed the agent on the admin server instead of the managed server? It should be managed server.
Is this WebLogic clustered environment ? If it is a clustered setup; then you need to follow some specific steps to configure the managed servers. You are better off installing the agent on a managed server and copy the agent changes (CLASSPATH and JAVA_OPTIONS) to all the server instances. Some folks also prefer to copy these changes in commEnv.sh (easy way out) but we do not recommend this route since the server related JAVA_OPTIONS can be specific to each BEA server instance. Please note that the agent installer does not understand the template of admin server script. So, for a clustered environment :
1. Remove the present agent, restore the admin server script.
2. Install the agent on a managed server.
3. If there are more than one managed servers, put the agent startup script related changes manually in each of the managed servers.
4. Also note that you can start managed servers from console or command line. Depending on where you start managed servers, you will have to copy the agent changes to the respective files.
If it is not a clustered environment; follow 1 and 2 only. Could try it out and let us know what are your findings? Jerry

SQL server agent post installation validations

I installed SQL server agent and added instances in OEM.
It was successfully added.
The validation step currently says check the home page reports & reports properties page..
I am seeing many errors (table/view not found) under Instance information, Registry information.Some of the values are populated like " Microsoft SQLServer Database Configuration - database settings" and look ok.. Other grids like "Database settings" have errors
Anyone been through this & know the fix ?
Database Settings
An error has occurred!
Error rendering element. Exception: ORA-00942: table or view does not exist
Home
Instance Information
An error has occurred!
Error rendering element. Exception: ORA-06550: line 1, column 322: PL/SQL: ORA-00942: table or view does not exist ORA-06550: line 1, column 276: PL/SQL: SQL Statement ignored ORA-06550: line 1, column 1031: PL/SQL: ORA-00942: table or view does not exist ORA-06550: line 1, column 512: PL/SQL: SQL Statement ignored ORA-06550: line 1, column 1833: PL/SQL: ORA-00942: table or view does not exist ORA-06550: line 1, column 1453: PL/SQL: SQL Statement ignored

I have the same problem...
Did you manage to resolve it?

Reporting Services 2012 for SharePoint and SQL Server Agent "Subscriptions and Alerts"

After installing Reporting Services for SharePoint (Denali) in my test farm, I'm trying to configure the "SQL Server Agent" access for Reporting Services. From Central Admin I'm going to the Reporting Service applicaiton configuration screen and selecting
"Provision Subscriptions and Alerts". I've tried both options on this screen. I've manually executed the "download sql script" in SQL Server, as well as entering a user with SQL sys admin rights on the SQL server into the login fields on the screen.
The role and permissions have been created for the application pool service account, but Reporting Services is still trying to connect with the annonymous login because I'm getting the following alert each time I open the "Provision Subscriptions and Alerts"
screen:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
The "status" on the screen still shows "SQL Server Agent State cannot be determined". Has anyone else seen this?
Thanks!!

Thanks for your reply!
1) Looks like the new Reporting Services does not run as a Windows Service so it's not listed in the "Configure Service Accounts" pulldown. As a result, I don't see how to set the service account. It's only assigned to an application pool.
I installed it into an existing application pool and that application pool "is" in the list and has a domain service account already assigned.
2) Which users need to be in here in order to configure the "Provision Subscriptions and Alerts" screen? I already have the farm admin account which is the account I use when running Central Admin.
3) As mentioned in #1, I've installed Reporting Services into an existing application pool with other service apps.
4) This link is for Reporting Services 2008 R2 which is very different install process. But I did follow the SQL Server Reporting Services 2012 RC0 installation instructions and the Reporting Services is functioning correctly with no errors.
I'm just not able to configure the sceduling the alerting with interfaces with the SQL Server Agent.
Thanks!

Unable to start SQL server agent service

hi,
We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
entries are in windows dns and resolving the IP to name and name to IP
Error msg: The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." error message.
But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
dns
Sagar

I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename> was missing. The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
configuration, so no changes were needed there.
Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
This worked for me, thanks:-)

Unable to view SQL Server Agent while logged in as user

Hello Everyone,
I have granted SQLAgentUserRole permission to one of the user and using enterprise edition of SSMS. still user is not able to view SQL Server Agent. Any help will be greatly appriciated.

There is no Enterprise Edition of SSMS. There is SSMS Basic and SSMS Complete. Prior to 2012 sp1, only SSMS Basic were available with Express Edition - but as of 2012 sp1 Expredd also offers SSMS Complete. SSMS Complete is selected bu default when you install
SSMS (unless you are prior to 2012 sp1 and are using Express, of course).
However, even SSMS Basic *should* show Agent assuming you have permissions for that. This is hearsay, but from trusted sources. Here is what to do:
Check what is installed for the machine from where you are running SSMS. You can do that using SQL Server Installation Center - see this blog post: http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/10/what-does-this-express-edition-look-like-anyhow.aspx
(towards the end).
On that machine try both this problematic account as well as an account which is sysadmin. Does the sysadmin account see Agent? If so, you know permissions aren't granted properly. If not, then you know the tool is the problme.
Also try the problematic account from a machine where you know you see Agent normally. Again, this will help you assess whether the problem is the tool (SSMS) or permissions for the account.
Tibor Karaszi, SQL Server MVP |
web | blog

Not able to run the SSIS package in SQL Server Agent Job in SQL 2012

Hi,
I scheduled a job (SQL SERVER AGENT) which will call my SSIS package. This package will execute 5 packages in loop.
When I execute this job I am getting error as below
============================================================
Started  : 12:30:19 PM
Error  : 2014-01-23 12:30:20.37
Code  : 0xC00220EC
Source  : Execute Package Task
Description : Error 0x80070005. Failed to create an instance of empty child package.
    The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services,
    may be corrupted on your machine. End Error
Error  : 2014-01-23 12:30:20.37
Code  : 0xC00220DE
Source  : Execute Package Task
Description : Error 0x80070005 while loading package file "D:\SSIS\RetailMobileApp\Staging_Pkg\stg_Category_Master.dtsx". Access is denied.End Error
DTExec  : The package execution returned DTSER_FAILURE (1).
Started  : 12:30:19 PM
Finished : 12:30:20 PM
Elapsed  : 1.123 seconds.
The package execution failed.
The step failed.
============================================================
In the STEPS I have selected as follows:
Type : SQL Server Integration Services Package
Run as: SQL Server Agent Service Account
Package Source: File System
What config I need to check here ? This job is not able to access the package stored in the folder.
Sridhar

Thanks for your reply. I had created credentials and used this while creating the Proxy account. With the Proxy account I am able to execute the Job Successfully. Concern here is I used my NT account to create this Proxy. Suppose If I left from the
current project if some one is coming to this project later they need to change the credential with their NT account and run the JOB? Is this right way or we an create any other account in common? If so how?
Sridhar

SSIS package fails under SQL Server Agent job

Hi All
I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.
But SQL Server Agent job is failing to do this. I am getting the error as
" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0."
Please help me.
Thanks

Two things that usually come to mind when this happens from BIDS locally to the SQL Agent are
1. Security is not
adequate under the SQL Agent Service Account
Rule the security problem out by setting up a proxy account that you know ahs security to run the needed tasks in the package. Either that or give the service account the permissions needed.
2. 32bit BIDS development and running under a 64bit Platform in your SSIS installation
This can be fixed by selecting run in 32bit more or running the package with the 32bit installed version of DTEXEC found in the Program Files (x86) folder where you installed tools.
Next, setup logging in the package so you get a more detailed error message. Event handlers on the tasks will be much more detailed using the OnError event. you can write that to either a flat file with a data flow in the event handler or simply
insert the event into a table using the ? as the parms. If you need assistance setting that up, here are basic steps for a SQL Server table
1) Select the task and click the event handler tab in BIDS
2) Select OnError event handler in the list
3) Click the enable link and drag a Execute TSQL Task over to the window
4) Create a table in your SQL Server database (create one so you don't litter your user DBs if needed)
5) Open the task and add the connection as needed. Then add this statement
INSERT INTO dbo.TableYouCreated
(PackageName, SourceName, EventInfo)
VALUES (?,?,?)
6) Go to parameter mappings and add 4 new mappings as following
System::PackageName
Input
nvarchar
0
System::SourceName
Input
nvarchar
1
System::ErrorDescription
Input
nvarchar
2
Save and reimport the package and then the event of the errors should insert into the table in detail
Ted Krueger
Blog on lessthandot.com @onpnt on twitter

FAM 8.0, Tomcat J2EE agent installation problem

Hello:
I was able to install FAM 8.0 in Tomcat 6.0.14 on Ubuntu (7.04) Linux. Everything seems fine. In the end, the applications I want to use with OpenSSO also make use of Tomcat 6.0.14. I noticed on the opensso users email list that the Tomcat 3.0 agent won't be available until early next year; but that the 2.2 agents should work with FAM 8.0. So, I got the the J2EE agent for Tomcat - SJS_Tomcat_Server_55_agent_2.2-01.tar.gz. The documentation makes no references to Tomcat 6, and I'm hoping this is due to the fact that Tomcat 6 was not available when the documentation was written.
Does this agent work with Tomcat 6? I have this problem when installing the agent (agentadmin --install):
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Invalid directory specified for the $CATALINA_HOME environment variable
Invalid CATALINA_HOME directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14I can see in debug/agentadmin.log the following:
[05/24/2008 13:06:37:684 PDT] FileSystemValidator : Is directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? true
[05/24/2008 13:06:37:686 PDT] HomeDirValidator : Is $CATALINA_HOME directory /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? false
[05/24/2008 13:06:37:686 PDT] Invalid CATALINA_HOME directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14This directory does indeed exist, and is accessible by the user I'm logged in as. It appears FileSystemValidator agrees with me, but HomeDirValidator has a problem. I tried this on both Ubuntu 6.04 and Mac OS X 10.5.2. Does this indicate that Tomcat 6 is not supported? Or is it indicative that neither OS on which I've tried to install the agent is officially supported?
Thanks!
Jeff

Hi Denis:
Before being redirected to another short term task, I did indeed get the Tomcat 6 agent to work. I probably won't be able to look at OpenSSO again seriously for another couple of months. :(
I have the OpenSSO server running on Tomcat 6.0.14 on Ubuntu 6.x Linux running in a virtual machine on my Mac. I was not able to get the server to run directly on the Mac, and I cannot remember the reason at this time.
But, as far as the agent goes, I run it again using Tomcat 6.0.14 on my Mac (Mac OS X 10.5.2), using the 1.5 JRE. I do have the agentapp war deployed as well as the agentsample web application to play with. In my catalina.out file:
Jun 18, 2008 10:07:20 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Jun 18, 2008 10:07:20 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentapp.war
Jun 18, 2008 10:07:21 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentsample.war
Jun 18, 2008 10:07:22 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Jun 18, 2008 10:07:22 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8011
Jun 18, 2008 10:07:22 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=nullI have no error messages is any Tomcat log file.
I checked out the source code for the Tomcat v6 agent (2.2) on May 27, so I don't know how that compares to yours or what's been checked into CVS since my build. I also don't know what the OpenSSO NamingService is.
I assume you used fully qualified domain names to specify the web application to be protected by agent as well as the OpenSSO server itself. The following is the output of the conversation when I run the agent installer script on my system. It has been redacted a bit (domain name and encryption key) to protect my client, but otherwise this is what I supplied to the installer:
Enter the complete path to the directory which is used by Tomcat Server to
store its configuration Files. This directory uniquely identifies the
Tomcat Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the Tomcat Server Config Directory Path
[/opt/apache-tomcat-6.0.14/conf]: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Enter the fully qualified host name of the server where Access Manager
Services are installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: login.opensso.example.com
Enter the port number of the Server that runs Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services port [80]: 8080
Enter http/https to specify the protocol used by the Server that runs Access
Manager services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Protocol [http]:
Enter the Deployment URI for Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Deployment URI [/amserver]: /opensso
Enter the fully qualified host name on which the Application Server
protected by the agent is installed.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Host name: analysis.opensso.example.com
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Choose yes to deploy the policy agent in the global web.xml file.
[ ? : Help, < : Back, ! : Exit ]
Install agent filter in global web.xml ? [true]:
Enter the preferred port number on which the application server provides its
services.
[ ? : Help, < : Back, ! : Exit ]
Enter the port number for Application Server instance [80]: 8090
Select http or https to specify the protocol used by the Application server
instance that will be protected by Access Manager Policy Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the Preferred Protocol for Application Server instance [http]:
Enter the deployment URI for the Agent Application. This Application is used
by the agent for internal housekeeping.
[ ? : Help, < : Back, ! : Exit ]
Enter the Deployment URI for the Agent Application [/agentapp]:
Enter a valid Encryption Key.
[ ? : Help, < : Back, ! : Exit ]
Enter the Encryption Key [XXmyencryptionkeyXX]:
Enter a valid Agent profile name. Before proceeding with the agent
installation, please ensure that a valid Agent profile exists in Access
Manager.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Profile name: testagent1
Enter the path to a file that contains the password to be used for identifying
the Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the path to the password file: /Users/jas/Development/opensso/tryout/agent_password
SUMMARY OF YOUR RESPONSES
Tomcat Server Config Directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Access Manager Services Host : login.opensso.example.com
Access Manager Services Port : 8080
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /opensso
Agent Host name : analysis.opensso.example.com
$CATALINA_HOME environment variable :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Tomcat global web.xml filter install : true
Application Server Instance Port number : 8090
Protocol for Application Server instance : http
Deployment URI for the Agent Application : /agentapp
Encryption Key : XXmyencryptionkeyXX
Agent Profile name : testagent1
Agent Profile Password file name :
/Users/jas/Development/opensso/tryout/agent_password
Verify your settings above and decide from the choices below.
1. Continue with Installation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]: 1
Updating the
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/bin/setclasspath.sh
script with the Agent classpath ...DONE.
Creating directory layout and configuring Agent file for Agent_001
instance ...DONE.
Reading data from file
/Users/jas/Development/opensso/tryout/agent_password and encrypting
it ...DONE.
Generating audit log file name ...DONE.
Creating tag swapped AMAgent.properties file for instance Agent_001 ...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Realm to Server XML file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Adding filter to Global deployment descriptor file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Filter and Form login authentication to selected Web
applications ...DONE.
SUMMARY OF AGENT INSTALLATION
Agent instance name: Agent_001
Agent Configuration file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/config/AMAgent.properties
Agent Audit directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/audit
Agent Debug directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/debug
Install log file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/logs/audit/install.log
Thank you for using Access Manager Policy Agent
[jaslap:tryout/tomcat_v6_agent/bin] jas% Can you post the exception details you're getting. That might help someone diagnose the problem.
Take it easy,
Jeff

OWSM server agent installation

Similar Messages

Maybe you are looking for