Behean line: erabili nahi duzun profila jabetza arau batean ikusleak sortzeko, jabetza ikusgai egon behar du "denek".

I was working with a co-worker yesterday and he was building out a MOSS audience based on a custom user profile property in MOSS. Kasu honetan, ikusle jabetza izeneko "SITECD" eta hitzarmena, gordetzen bat 3 pertsonaia kodea. Ikusleen eta arau bat esan badu, "SITECD berdinen 'ABG' definitu zuen", ondoren, besteak beste, erabiltzaile hori ikusleen profila.

Erabiltzaile bakar profila sortu zuen balio duten eta ikusleen konpilatu, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (inprimaki murriztaileak) and I remembered reading somewhere that property profiles used in rules must be visible by “everyone”. He made that change and that solved the problem.

The really funny thing about this is that I “remembered” reading about this. It was nagging at me this morning for some reason and I realized that I had written a chapter in this book, MOSS azaldu: Microsoft Office SharePoint Server Informazio Langileen sartu Dive Deep 2007, eta estaltzen dut puntu hau oso atalean idatzi dut :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse xehetasun ederra sortu hau idatzi hemen eta erreferentziatutako I kapitulua: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</amaiera>Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

I’ve been working with SharePoint SSO and learning as I go. One way in which this works is that you tell SharePoint about external applications. Users log into that application via some SharePoint function (e.g. iView web zati). The first time the user performs this action, it prompts them for the correct user id and password to use for that system. It’s setting up a mapping between your SharePoint credentials and your credentials for that backend system. Thereafter, Erabiltzaileak ez dute beren ID sartu denean sortu hit dute sistema hori.

That part worked well for me. Hala eta guztiz ere, galdera begs, "Nola ez, erabiltzaile id edo pasahitza aldatu?” The user might have made a mistake, ari zaren edo agian azterketa batzuk egiten ari dev ingurumena eta behar kontuen artean azkar aldatzeko.

Ez dakit erantzun hori, Administración Central sartu ahal izango dituzu baina jakin dut eta erabiltzailearen kredentzialak kudeatzeko:

Administrazio Zentralak> Eragiketak -> Kudeatu Single Sign-On -> Kudeatu kontua Enterprise eskaera definizioa informazioa

Hortik aurrera, kanpo-aplikazio zehatz dezakezu (e.g. SAP) and the account you want to delete. You can also change the mapping.

Badakizu nola azken erabiltzaileei euren kredentzialak zuzenean aldatu ahal izateko, kindly post a comment 🙂

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

I needed to do some minimal proving today that iView web parts can work in my client’s environment. I’ve never worked with this slice of SharePoint before.

Microsoft-ek zuri oso kalitate handiko paper gai honen inguruan sortu.

Oztopo gainditu behar izan nuen lehenengo izan zen non iView web parte? For some reason, izan zen nire lehen pentsamenduaren deskargatzeko gune bat nonbait daukat litzaidake, perhaps SAP’s site. Nuen 1/2 convinced myself that iView web parts might even cost extra. Jakina, MOSS barne dira (Enterprise uste dut; hori da hemen erabiltzen dut Edonola). I’ve seen the standard “add a web part” dialog box hundreds or more times and always glossed over it. No more!

The next obstacle is that I can’t read instructions.

Web zati zen I erabiliz eta mantendu gogaikarriak mezu hau eskuratzerakoan:

No SAP servers are configured for this site. Contact your administrator to configure trusted SAP servers.

Paper zuri argi eta garbi dio file dago konfigurazio-fitxategi bat editatzeko "<Drive gutuna:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, guztiak ikusi nuen izan zen "Archivos de programa ... konfigurazioa" eta berehala joan nintzen du 12 hive. Once I finally slowed down to read it, I realized my mistake and it was easy to fix.

I continued on my merry way with SSO configuration. It’s not all at clear to me if that worked, baina, egun, beste istorio bat da.

Behean line:

1. iView web zatiak sartzen dira out SharePoint batera kutxa (ziurrenik Enterprise).

2. Magia konfigurazio fitxategia, "TrustedSAPHosts.config", ez da bizi 12 hive.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Tonight, I’m doing some hobby work with a virtual machine running on my desktop. I’m connecting via IE on my laptop and I’m noticing horrible performance. IE keeps freezing, batez ere eskuineko izkinan ezer duen goitibeherako eragingo luke sartzeko dut, ondo, drop down. I would click on Site Actions and things freeze up for a while. They would freeze long enough for me to switch over to another browser window and do something else. If I confine myself to navigating around from page to page, it’s reasonably quick, but even that feels slow. Normalean, things are very fast.

I’ve had this happen to me before and I think that I ended up rebooting at the time. I’m about to do that when I somehow notice I’m still VPN’d to a client from 2 days ago(!). I disconnect and that that solves my performance problem.

</amaiera>

Nire blog Harpidetu.

Izan gara, erabiltzaile baten onarpen proba lan (UAT) ingurune, gisa, garapen aldean, hil da motela.

FBA konplikatuak erabiliz ingurune bat da, SQL 2008, SSRS hedatua eta web-aplikazioak Internet bidez eskuragarria https erabiltzen, beraz, gogor jaisten jarraitzeko alea.

Aurreko bezero, FBA erabiltzen dugu papera LDAP hornitzaileekin (eta emate-hornitzaileak). One of my colleagues, askoz I baino azkarragoa, determined that the "out of the box" LDAP rol-hornitzaileak, denean, ingurune hori erabiltzen, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.

Egoera hori zirudien antzeko, so we looked into replicating that solution to the today’s client. As I was debugging that, Mezu hau litzateke maiz Sistema erregistroan agertzen nabaritu dut (Gertaera Viewer tik):

A worker process with process id of ‘XXX’ serving application pool ‘Home – 80’ has requested a recycle because it reached its virtual memory limit.

Hau hartu dut app igerilekua zela urrun birziklatzeko esan nahi, oso maiz, eta hori arazo bat errendimendua azaltzeko litzateke.

I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (MB)" had been set to true and had been set to 5000. That seems like enough, but I decided to unset the value and that had an immediate positive effect. No more app pool recycling. No more mysterious slow-downs and pauses.

I don’t really understand the underlying "stuff" hori ez da gertatzen, baina argi eta garbi kausa / efektu gauza bat gertatzen ari da eta oraingoz, UAT ingurumena erabilgarria da.

</amaiera>

Nire blog Harpidetu.

Egokia da, ziurrenik, nahiz eta Praktika Onenen bat, zure bilaketa txostenak hilean behin berrikusi eta bilatzeko aukera onena apustuak gehitu, tune your thesaurus and maybe even uncover some business intelligence that is otherwise hidden to management.

It’s already the 3rd of the month. Time’s awastin’ 🙂

</amaiera>

Nire blog Harpidetu.

At New Jersey SharePoint erabiltzaile talde bart bilera, Microsoft Sr. produktu espezializatuen DuWayne Harrison aurkezten Microsoft Datuak Babesteko kudeatzailea 2007. DuWayne was great (zen bat edo bi lankideek onartzen ikusleek beren izenak ez dut gogoratzen tik). Aurkezpen materialak eskuratu ahal izango duzu hemen.

Arte bart, Ez dut inoiz entzun DPM.

Ez nago bat sistema admin pertsona mota, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. Me, DPM is a backup/restore solution for Microsoft "stuff":

• Fitxategiak
• SQL
• O / S
• Makina birtualak (bizi MB babeskopia, nahiz eta VM berez Unix exekutatzen).
• Bare metal berreskuratzeko (I.E. hondamendi hardware porrota).

Stuff haratago, which I would consider to be minimal requirements for any kind of "real" babeskopia / produktua leheneratu, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

• Datu-base osoa (e.g. edukia, config, etc).
• Gune bildumak
• Banakako guneak
• Banakako elementuak (e.g. dokumentuak).

The actual restore process involves extracting the target data from the backup and save it into a "restore farm" eta, ondoren, bertatik, mugitzen da ekoizpen ingurumena (edo edonora berreskuratu nahi duzu). I think this is seamless, but there was a lot of emphasis on the need for a "restore farm". The restore farm does not need to match the production environment in every particular (batez ere, topologia fisiko) baina ez du behar txantiloiak dagokionez dator, bertsioak, etc.

Nik ez dut ikusten osoa amaiera demo amaitzeko, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, gutxienez tamaina moderatua ingurune.

I was particularly struck by the pricing. Obviously, Ez ezazu dit hau, baina garestiena prezioei dela gutxi gorabehera, honela uste dut (dolar en):

• $600 DPM berez.
• DPM zerbitzari bat Hardware (eta lotutako komunikabide eta gauza guztiak).
• $450 zerbitzari bakoitzeko kopiak nahi duzun ("enterprise" lizentzia).

A bost zerbitzari baserriko litzateke gehien kostua:

• $600 DPM for
• $450 x 5 zerbitzariak = $2,250

Lizentzien kostua, guztira: $2,850

Praktikan, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, adibidez. You don’t necessarily need enterprise licenses either.

The user interface is seems very simple probably would not require any special training to get up to speed. I did ask about that specifically and there is apparently a 1.5 eguneko klasea eskuragarri, da, baina ez dit begi bistakoa Edozeinek litzateke benetan behar hartzea.

Guztia, Da, zalantzarik gabe, merezi du ikertzen ari bazara ez, datuak babesteko SharePoint irtenbide bila uste dut.

</amaiera>

Nire blog Harpidetu.

Twitter: http://twitter.com/pagalvin