»  Forums
Minimize FLCAUG Discussion Forums
Print  
 
Subject: Problem using 'wild card' in profile triggers
You are not authorized to post a reply.
Author Messages

SuperUser

Advanced MemberUser is Offline
Posts:26

05/14/2003 2:11 PM  
Have been trying to use wild cards in a file-close trigger profile and can
not get it to work. I m trying to create a profile trigger with a file close
on a file that tm_Image_mmddyy.txt . I have tried many combinations and can
not get any wildcards to work at all. The only file close triggers that work
has specific file names.

SuperUser

Advanced MemberUser is Offline
Posts:26

05/14/2003 2:15 PM  
Hey Tim,

We tried to use the file triggers on NT, but ran into too many exceptions. Sorry I can't help. I will forward to others in my group and ask their input.


SuperUser

Advanced MemberUser is Offline
Posts:26

05/19/2003 9:46 AM  
I found out from CA to turn off the "stat method" in the trigger profile. It works great,

SuperUser

Advanced MemberUser is Offline
Posts:26

04/08/2004 2:25 AM  
Using periods between wildcards wont work.
eg

SuperUser

Advanced MemberUser is Offline
Posts:26

04/08/2004 3:15 PM  
Here is a list of all the ports that are used and what they are used for.

161: SNMP Listen (aws_sadmin) (mibbrowse) (UDP)=20 162: SNMP Broadcast (aws_snmp) (UDP)=20 216: CAI_LIC_D (CA Licensing) (TCP)=20 1433: aws_wvgate (MSSQL Server connectivity) (TCP)=20 1470--=20 1475: abrowser - bypass via dsm routing (UDP)=20 1721: CCI (ccirmtd) (cci remote for Unix connection) (TCP)=20 4104: CAM (UDP)=20 5678: awservices excutable=20 5679: AW services connect awservices service=20 6162: SNMP (UDP)=20 6664: 1.5 Agents (UDP)=20 6665: abrowser ; mibbrowse (UDP)=20 =20 7000: CCI (cci remote for MVS connection) (TCP)=20 7001: CCI (TCP)=20 7003: CCI (quenetd) (TCP)=20 7004: CCI (quenetd) (TCP)=20 7770: Agents (communication to ORB) (abrowser) (TCP)=20 7771: ICMP Ping (DSM)=20 1) port 161 SNMP (ca-unicenter used this port for incoming traps)=20 =20 2) 162/6162 SNMP-TRAP (these ports have to be enabled both ways)=20 =20 3) 6665 PORTS USED BY AGENTS (can be changed if AWS_SADMIN is started=20 with -p )=20 =20 4) 6x64 PORT USED for 1.5 agents=20 =20 5) 7770 AWS-ORB, and all other services to speak with orb (this can be=20 changed in quick.cfg file)=20 =20 6) 7771 ICMP ping port (for DSM machines only)=20 =20 7) 5678, 5679 used by awservices executeables=20 NOTE: ports 7770, 7771, 5678, 5679 are ports that are local to the

machine besides the above ports unicenter enterprise management uses port=20 1721 and 7003 for cci communications and 7001 for unicenter communication=20 =20 For TNG EVENT Management the following ports need to be opened bi-direcionaly =20 _1721: UNIX to UNIX and UNIX to NT communication via the remote=20 =20 =20

=20 7001: NT to NT communication using TCP/IP (this is the one you will need for=20 the firewall situation)=20 =20 7003: NT to NT communication using RPC (TCP endpoint)=20 7004: NT to NT communication using RPC (UDP endpoint)=20 =20 Now if you are running only workload agent on the unix machine=20 and try to communicate to the NT manager machine then all you need is=20 1721: UNIX to UNIX and UNIX to NT communication via the remote.=20 =20

SuperUser

Advanced MemberUser is Offline
Posts:26

04/08/2004 6:15 PM  
Sean, See Technical Document ID: TEC264704

SuperUser

Advanced MemberUser is Offline
Posts:26

04/14/2004 1:02 AM  
Thankyou for the info on ports numbers. Is there any documents on the web for Unix setups for workload triggers?
You are not authorized to post a reply.
Forums > Discussion Forums > Unicenter Topics > Problem using 'wild card' in profile triggers



ActiveForums 3.6
 
     
Date » 23 July, 2008    Copyright 2002-2008 by RavenSystems & FL CA Users Group Login : Register
Inspired by Nina