[svn] 4494: Added tests to hit channels and services configuration exceptions

Revision: 4494
Author: [email protected]
Date: 2009-01-12 16:12:09 -0800 (Mon, 12 Jan 2009)
Log Message:
Added tests to hit channels and services configuration exceptions
checkintests: passed
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/error.t xt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/DuplicateIdTest/service s-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/channels/InvalidIdTest/services- config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/e rror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/BadDefaultChannelTest/s ervices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/error. txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefTest/servic es-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/DuplicateDefaultAdapter Test/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/IncorrectRootElementTes t/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/er ror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidAdapterIdTest/se rvices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIdTest/services- config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/error.t xt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/NoClassAttrTest/service s-config.xml

my connectivity is okay, I'm getting errors from domain controller itself, I checked and the network is okay, but for the record here is my ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : server
   Primary Dns Suffix . . . . . . . : ***.tk
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ***.tk
Ethernet adapter Ethernet:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
   Physical Address. . . . . . . . . : 00-0C-29-32-7E-79
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 213.233.***.***(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 213.233.***.1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Similar Messages

[svn] 4534: Add configuration tests for flexclient, destination and services

Revision: 4534
Author: [email protected]
Date: 2009-01-14 16:02:42 -0800 (Wed, 14 Jan 2009)
Log Message:
Add configuration tests for flexclient, destination and services
checkintests: passed
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/erro r.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/serv ices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/dest-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/e rror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/s ervices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/error. txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/servic es-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/error. txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/servic es-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/error.tx t
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/services -config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/er ror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/se rvices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/e rror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/s ervices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/erro r.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/serv ices-config.xml

Revision: 4534
Author: [email protected]
Date: 2009-01-14 16:02:42 -0800 (Wed, 14 Jan 2009)
Log Message:
Add configuration tests for flexclient, destination and services
checkintests: passed
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/erro r.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/serv ices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/dest-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/e rror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/s ervices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/error. txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/servic es-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/error. txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/servic es-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/error.tx t
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/services -config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/er ror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/se rvices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/e rror.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/s ervices-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/erro r.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/serv ices-config.xml

Interesting Document: Service Deployment and Service Configuration within the Internet of Things

Hi All,
an interesting document:
Service Deployment and Service Configuration within the Internet of Things
Best regards,
Andy.

Hello Marek,
I suppose you are not planning to do any kinds of advanced config using several VLANs and multiple SSIDs so let's just make your configuration simple and working.
In short, you need to remove all references to VLAN 1 and to any subinterfaces possibly related to the VLAN 1. This means in particular (follow these steps in sequence):
Remove the Dot11Radio0.1 subinterface entirely
In the Dot11Radio0 section, remove the encryption vlan 1 mode ciphers tkip command
In the dot11 ssid ciscowifi section, remove the vlan 1 command
After performing these steps, make sure that the ssid ciscowifi and encryption mode commands are still present in the Dot11Radio0 configuration, and if not, reenter them.
Best regards,
Peter

[svn] 2440: Added test for bug BLZ-214

Revision: 2440
Author: [email protected]
Date: 2008-07-10 12:02:39 -0700 (Thu, 10 Jul 2008)
Log Message:
Added test for bug BLZ-214
Maps with enum keys return null values
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-214
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/datatype/EnumTypeTest.java
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/EnumTy peTest.mxml
blazeds/trunk/qa/resources/frameworks/qa-frameworks.zip

Route mail and Active Directory Sites and Services configuration

Folks,
I have a problem in the internal email routing. My network is spread across various regions and the branch offices are connected together in a mpls network (full mesh). Every region has its own Exchange Server with all roles installed and the smtp connection
to the outside world is linked to two Exchange servers in the headquarter server farm.
The problem is that internally I often see emails going across the Exchange Servers in the branch offices where there is low bandwidth (from 3 to 5 Mbps), thus email are sent first to these servers instead of going immediately to the Exchange hosting
the mailboxes of the intended recipients. This happens also with inbound emails.
This causes slowness in the email system and sometimes also the network with these branch offices suffers from packet loss or very high latency.
I know that Exchange is a site-aware application and uses the Active Directory topology for message routing and to communicate with the services that are running on other Exchange 2013 computers. For this reason I have checked the Active Directory Sites
and Services and surprisingly I have found that there are no sites, no subnets, nothing has been defined but the default settings, included the Inter-Sites transport which contains the default DEFAULTIPSITELINK.
Apart from the fact that clients use logon servers which are not supposed to use in the far remote offices, I am concerned of changing the Exchange Infrastructure whilst the email system is running and I would like to ask your opinion about my next steps:
1) Create subnets for every office
2) Create sites and then link them to the subnets done in point 1
3) Delete the DEFAULTIPSITELINK and create new site links based on the costs (network speed) in order to determine the best routing server. I have 5 remote offices with 5 different network bandwidth, so I'll have to create 5 IP site links: high cost for
link with slow network, low cost for fast network.
4) (Optional) Configure the Exchange-specific cost using the Set-AdSiteLink cmdlet to the AD IP site links created previously
Apart from the valid questions on why the previous Exchange Administrator have forgotten to set up the Active Directory (Topology) Sites and Services...
...And why have chosen to install all Exchange Roles to each server when there was no reason to do that (there are two servers connected to the external smtp gateways in the headquarter, so in my opinion the Exchange Servers in the remote branch offices
should have had only the mailbox and the cas role)...
As a matter of fact, my idea is to go further and create the sites,subnets and the ip site link. If I still notice a wrong email flow, I can configure an ad-hoc Exchange-specific cost using the Set-AdSiteLink cmdlet. Does this sound reasonable to you guys
or I am taking the wrong decisions?
Thanks

Thank you very much for your link. This is exactly the page I have read just before posting my question here. It is not easy for me to understand why this has been setup this way by a Microsoft certified engineer.
There are specific rules to follow when Active Directory and Exchange are located in multiple sites and I am not a skilled Exchange Administrator... he keeps saying that it is correct and also tells that if I go forward with my ideas there is the
risk to increase the level of complexity. I prefer more complexity than default setting, and as a consequence of that, connectivity problems!
Hopefully everything goes well. I will post my results here once I have done the changes
Regards

My iTouch is stuck in the calendar. Added an alert, hit done and it won't leave the page. Won't let me cancel it either.

My 4th gen iTouch is fairly new. Upgraded from a 2nd gen. Today when I added an event in my calendar and then added an alert, it froze. I hit the done button, nothing. I can't get back to the general calendar. Turned the iTouch off for 20 seconds, still the same problem. Only the Done button is highlighted and won't respond to get me back to the calendar. Cancel button is not available as it's not high lighted. I've never used alerts before, so not sure if that's what caused the problem. The rest of the iTouch is up and working just fine. Maybe a tad slower and at times a bit jerky. But all the rest of my apps are responding and working.

- Try a reset. Nothing will be lost.
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Next would be a restore, first from backup and then to factory defaults/new iPod if problem persists.

Multi Channel Messaging service Configuring, Testing using Simulator

Hi
I am working on soa project to implement human workflow implementation like sms, voice additional to email service. Can any one guide me to the simulator to be used and configuration to be set.

Please refer section "24.6 Troubleshooting Oracle User Messaging Service" at -
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10226/ns_config.htm
Possible cause -
The UMS Driver for the appropriate channel is configured with a specific list of SenderAddresses, and the message sent by the application has set a non-matching Sender Address.
Note: UMS Server matches the outbound message's sender address, if set, against the available drivers' SenderAddresses to find a matching driver to use for delivering the message. If a driver has set one or more SenderAddresses, then the UMS Server only sends messages with the matching sender address to it.Solutions -
1) Check the following settings in the appropriate UMS Driver using Oracle Fusion Middleware Control:
SenderAddresses
Note: The format for SenderAddresses is a comma-delimited list of <DeliveryType>:<Address>.
For example:
EMAIL:[email protected], EMAIL:[email protected]
2) Leave this property blank, if you want this driver to service outbound messages for all sender addresses for this channel (delivery type).
3) If there are multiple driver instances deployed for the same channel (delivery type) with different configurations, use the SenderAddresses to differentiate the driver instances. For example, one instance can be set with a specific value in SenderAddresses to only service outbound messages with that matching sender address, while the other instance can keep the SenderAddresses blank in order to service all outbound messages that do not specify any sender address or one that does not match that of the first driver instance.
4) SenderAddresses that are configured with the incorrect syntax (such as missing <DeliveryType>:) are ignored by the UMS Server for the purpose of driver selection.Regards,
Anuj

How can we write channels and endpoints configuration in actionscript?

Hi All
              how can we define channelset in actionscript in flex
                just like at my client side application itself not in remote-config.xml
                   var cs:ChannelSet = new ChannelSet();
                 var amf:AMFChannel = new AMFChannel(.................................
                   i dont know how to proceed further
                  could any one please help me

Hi All
              how can we define channelset in actionscript in flex
                just like at my client side application itself not in remote-config.xml
                   var cs:ChannelSet = new ChannelSet();
                 var amf:AMFChannel = new AMFChannel(.................................
                   i dont know how to proceed further
                  could any one please help me

5.1 audio is missing one channel and other stories

Ok, I started another post earlier about this problem, but I thought I'd explain it a different way.
Here's my problem. I go into the MSI Sound Manager and go to the speaker test tab. I click on every speaker and everyone of them works except the REAR RIGHT speaker. No sound comes out. If I put it up to my ear, there's some static but no sound! I tried every version of the Realtek driver under the sun as well as every BIOS update from 1.10 up to 1.9b2.
Here's the second problem:
I RMAed the first board to Newegg and they sent me another one. The second one did the same thing. MSI suggested that I take the mobo out of the case because maybe it was a grounding issue. I did that (had everything hooked up on a phonebook) and it didn't change anything. So, instead of sending back this board too I figured I'd try a Sound card instead. I picked up a turtle beach santa cruz card, disabled the onboard sound and installed this board. On that board, The front and rear channels work but nothing comes out of the center. Am I just so lucky that 3 pieces of sound hardware don't work for me?
All I want is 5.1 sound!
Here's my computer
500W Power Supply: +3.3V 28A, +5V 50A, +12V 18A, -5V 10A, -12V 1A, +5VSB 2.5A
AMD Athlon 3200+
MSI K8T Neo FSR
2x512MB VData PC3200 RAM
eVGA GeForce 6800 GT
NEC DVD Burner
Optowrite CD Burner
250GB IDE WD Hard Drive
Samsung Floppy

microsofts has a sound test program that will test 5.1 channels, and says right front left rear, etc. so if your still missing sounds after two boards, i would examine the jumpers , try both front and then rear jacks, then try the speakers on a different system , also look at speaker calibration and check speackers, physical knobs, fader balance etc..
also i just checked ebay and audigy2's can be had for 30$ or so, and may be worth investigating. are you in the us.
but i have a suspition that the problem is either the jack is not all the way in or speaker related, or a setting, as the chances of two boards with the same problem is slim but not impossible.

Global virtual channels and DAQmx AI inputs

I would like to see and example linking global virtual channels and input configuration for DAQmx AI inputs. The DAQmx input requires physical channels and not global virtual channels.

Hello rlbrehm,
If you are using a global virtual channel then you have alredy set up the input configuration, as shown here:
So you simply need to set up timing and read, as shown here and in the attached VI:
Message Edited by Dr. Doiron on 08-06-2009 02:55 PM
With warm regards,
David D.
Attachments:
Global Virtual Channel.vi ‏9 KB
Input Config.jpg ‏176 KB
VI.jpg ‏78 KB

AD Sites and Services and Best Practices

Hey All,
I am new to OES, but not new to AD. I am in an environment in which DSfW was recently setup to support VDI testing.
I notice that there is no configuration under AD Sites and Services. We have multiple sites, with DCs setup at each site. The consequence of not having Sites and Services configured is that machines/users in site "A" are logging in through site "B" domain controllers. Obviously, this is not ideal nor best practice. Secondly, this leads me to wonder how the domain controllers are replicating since I do not see NTDS entries in Sites and Service MMC for the domain controllers, yet I do see that AD data is replicating by comparing databases (simply adding a new user on one DC I see it added on the secondary DCs). So I know it's replicating, but apparantly not using AD schema?
One other question I have about DSfW is regarding the migration from a mixed environment to a full AD environment. We are deploying AD primarily due to VDI initiatives, and currently only testing this. Looking further down the road for planning purposes I have to wonder if it's possible to stand up a 2008 R2 server, join it to the domain, dc promo it, FSMO transfer, then decommossion the DSfW systems. This would leave us with purely Windows DC environment for authentication. Is this something some people have done before? Is it a recommended best path for migrating? Cause I also see others creating a second AD environment, then building the trusts between DSfW's domain and the "new" domain (assuming these are not in the same forrest). That would be less than ideal.
Thanks in advance for any responses...

Originally Posted by jmarton
DSfW does not currently support "sites and services" but it's on the
roadmap and currently targed for OES 11 SP2.
Excellent! I feel sane now :) I can live with this, as long as it's expected/normal.
It sounds like you need sites and services, but once that's in DSfW,
why migrate from DSfW to MAD if DSfW works for your VDI initiative?
You are correct. I am simply planning and making sure all the options are in play here.
I would rather not get too deeply reliant on DSfW if it will make any future possible migration more difficult. Otherwise, DSfW is extremely convenient....I am impressed actually.
I also believe there may be a way we can control the DC used for specific "contexts" (or OUs as Microsoft calls them). So if I have a group of users in a particular OU that reside at a particular branch I think I should be able to set their preferred domain controller....and if so, that means sites & services becomes nearly irrelevent. I would be ineterested to talk to people who are using DSfW with multiple sites in play.

[svn:osmf:] 13351: Adding a new TimeUtil class and corresponding unit tests .

Revision: 13351
Revision: 13351
Author:   [email protected]
Date:     2010-01-07 16:19:20 -0800 (Thu, 07 Jan 2010)
Log Message:
Adding a new TimeUtil class and corresponding unit tests.
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as
Added Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/utils/TimeUtil.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/utils/TestTimeUtil.as

HI
add that fileds in the all locations where you need it like
in internal table declaration , write statement , select statement
these are the main areas where you have to add that 2 fileds

[svn] 4408: Adding Config tests for DeserializationValidators and MessageFilters

Revision: 4408
Author: [email protected]
Date: 2009-01-06 12:56:35 -0800 (Tue, 06 Jan 2009)
Log Message:
Adding Config tests for DeserializationValidators and MessageFilters
CheckInTests: passed
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good MessageFilterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good MessageFilterTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good MessageFilterTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/mult ipleGoodMessageFilterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/mult ipleGoodMessageFilterTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/mult ipleGoodMessageFilterTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingMessageFilterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingMessageFilterTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingMessageFilterTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingValidatorTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingValidatorTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingValidatorTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingMessageFilterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingMessageFilterTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingMessageFilterTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeMessageFilterTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeMessageFilterTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeMessageFilterTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/services-config.xml

[svn] 1754: Add more authentication tests for different channels.

Revision: 1754
Author: [email protected]
Date: 2008-05-15 14:43:20 -0700 (Thu, 15 May 2008)
Log Message:
Add more authentication tests for different channels. Fix a couple timing issues in the tests. Some tests were calling logout() and not waiting before running the next test which was failing in some cases.
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-amf/MessagingAuthenticationTest.mxml
Added Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/JMSAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MessagingAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MessagingAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MessagingAuthenticationTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MessagingAuthenticationTest2.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/polling-http/MultiTopicMessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/JMSAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MessagingAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MessagingAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MessagingAuthenticationTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MessagingAuthenticationTest2.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-amf/MultiTopicMessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/JMSAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/JMSAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MessagingAuthConSubscribeTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MessagingAuthProSendTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MessagingAuthSendSubscribeConstraintTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MessagingAuthenticationTest.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MessagingAuthenticationTest2.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/securi ty/streaming-http/MultiTopicMessagingAuthConSubscribeTest.mxml

Hello Emil,
Thank you for your response.
We have SAP PI 7.11 and we did get it to work with SPNego (Kerberos token) for an SSO interface from a .Net web client using an ActiveDirectory User. It was NOT an easy task, but it worked.
The problem we are facing is that when we setup the Authentication Stack for the XISOAPAdapter component in the NWA as instructed by SAP to support BASIC Auth AND SPNego, the old .Net clients that do not FORCE the Basic Auth try to connect with an NTLM Token (and this doesn't work)
After their first request they receive a response from PI with:
www-authenticate: Basic realm="XISOAPApps"
www-authenticate: Negotiate
Then they choose to send NTLM Token instead of the Basic. This very simple to fix, by forcing the .Net client to send Basic or Kerberos. But we can not change the client side as they are in production env. for some time now, and we have over 200 interfaces with several applications, the impact is quite big...if you know what I mean...
So I thought that maybe it was possible to do some Z XISOAPAdapter component parallel to the original and have two different Auth Stacks.
We have opened an OSS with SAP and we are exchanging msgs for some time now. I'll let you all know how this ended...
Regards.
PS: Would be great to read Michal Krawczyk thoughts on this topic ! thx !

[svn:fx-trunk] 11989: Added Jody's TabBar example and the TabBar icon.

Revision: 11989
Revision: 11989
Author:   [email protected]
Date:     2009-11-19 09:13:28 -0800 (Thu, 19 Nov 2009)
Log Message:
Added Jody's TabBar example and the TabBar icon.   This feature should be OK to officially sign-off now.
QE notes:
Doc notes:
Bugs:
Reviewer: Hans
Tests run:
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TabBar.as
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/TabBarExam ple.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TabBar.png

I am not sure what's happening with IE9 (no live site) but I had real problems viewing your code in Live View - until I removed the HTML comment marked below. Basically your site was viewable in Design View but as soon a I hit Live view, it disappeared - much like IE9. See if removing the comment solves your issue.
<style type="text/css">
<!-- /*Remove this */
body {
    margin: 0;
    padding: 0;
    color: #000;
    background:url(Images/websitebackgroundhomee.jpg) repeat scroll 0 0;
    font-family: David;
    font-size: 15px;
    height:100%;

[svn] 4494: Added tests to hit channels and services configuration exceptions

Similar Messages

Maybe you are looking for