Monthly Archives: Maiatza 2008

SharePoint Migration Tip: Erabili “untagged datuak” Migrazioak Incremental Views

Bat edo nire Oso lehenengo blog-mezu, SPS bezero migratzeko jarraitu genuen prozesu orokorra deskribatu dut 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Migrazio-proiektu, SPS asko mugitzeko modu ona aurkitu behar izan dugu 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

Dokumentu berri honek liburutegia da:

image

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\aldi baterako unitatean, baina SPS bat seinalatuz imajinatu dezakezu 2003 Dokumentu liburutegia:

image

Arrastatu eta jaregin eragiketa, eta ondoren, nire Helburu itxura:

image

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Gainera, Demagun ez dira ehunka dokumentuen (agian milaka) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Horren ordez, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" ikusteko gisa agertzen dira:

image

Orain, norbaitek eseri behera bere esleitu eguneroko ordu bat edo bi pasatzeko migratu dokumentuak etiketatu, they can use the "untagged documents" ikusteko beren ahalegina bideratzen:

image

Erabiltzaile tag dokumentuak, utzi dute zerrenda honetan.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Kutxa Out, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Hala eta guztiz ere, erabiltzailearen fitxategiak eta, ondoren, nabigatzailea ixten bada (edo Windows Explorer erabiltzen dokumentua igo), ezin dugu behartu erabiltzaileari meta datuak sartu (berriro, koadroan out).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</amaiera>

Nire blog Harpidetu.

Technorati Tags:

SharePoint komodina Search: “Pro” Ez da Stem baten “Programazioa”

MSDN bilaketa forum On, pertsona askotan galdetu hau atsegin galdera bat:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ bilatu ez da aurkitu."

Agian ez du sentitzen, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Bilaketa web zatitan dig, kontrol-laukia aurkituko dituzu, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() mota funtzioa.

Hauek batzuk dira zurtoinak:

  • "fish" is a stem to "fishing"
  • "major" is a stem to "majoring"

Hauek ez dira sortzen:

  • "maj" is not a stem to "major"
  • "pro" is not a stem to "programmer"

The WSS/MOSS search engine does support wild card search through the API. Here is one blog article that describes how to do that: http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/03/06/how-to-use-the-moss-enterprise-search-fulltextsqlquery-class.aspx

A 3 party produktu, Ontolica, provides wild card search. I have not used that product.

</amaiera>

Nire blog Harpidetu.

Technorati Tags:

Saio hasiera Workflow SharePoint Designer Jarduera

Azken astean, Nintzen lan nola loop eta estatuko makina bat ezartzeko SharePoint Designer erabiliz eta aipatu, bat alde batera utzita, zela I ziurrenik workflow hobeto mozteak buruz post blog bat idatzi.

Beno, Sanjeev Rajput beat me to it. Begirada bat.

Log datuak zerrenda pertsonalizatu batean gordetzen superior iruditzen erregularra workflow historia erabiliz:

  • Zerrenda pertsonalizatu bat besterik ez da, beraz esportatu dezakezu excel oso erraz.
  • Aldiz sor ditzakezu, dinamikoki datuak iragazi, etc.
  • Ez da auto-purge workflow ohiko historia.

Daude arrisku batzuk / downsides:

  • Askok datu gehiegi mozteak asko fluxuak eragin dezake zerrendan idatzi behar da.
  • Maybe you *do* want automatic purging. You don’t get that feature with this approach (eduki ala ez).
  • Security is tricky. In order to write to the list, the user must have permission to do so. That means that it’s probably not suitable for any kind of "official" audit since the user could discover the list and edit it. This could be overcome with some custom programming.

</amaiera>

Technorati Tags:

Nire blog Harpidetu.

The Trouble With Tribbles … err .. KPIs

This past week I finished off a proof of concept project for a client in Manhattan. While implementing the solution, Ran MOSS KPIs shortcoming beste I (ikus hemen KPI aurreko gai eta nire konpontzeko).

Aurrekariak: We used SharePoint Designer workflow to model a fairly complex multi-month long business process. As it chugged along, it would update some state information in a list. KPIs use this data to do their mojo.

We decided to create a new site each time a new one of these business processes kicks off. Aside from the workflow itself, guneak hauen antolatzailea hainbat dokumentu liburutegiak, use audience targeting and so forth. Just a bunch of stuff to help with collaboration among the internal employees, langile eta bezeroaren parte hartzen duten enpresa bazkide bidaiatzen.

Ere nahi dugu, osasun orokorra kontrolatzen duten enpresa-prozesuaren jakin batzuk KPIs egoera workflow-a datuak sustatu eta bisitaldiak KPIs erabiliz.

Azkenik, KPI Aldaketa bat egin duten elementuen zerrendan zerrenda bat ikuspegi bat erabili dugu, gune (datuak beste iturri batetik tiraka aurrean, excel edo SQL bezalako).

Arazoa da: Imajinatu dezakezu, oinarrizko ideia aurrera eramateko produkzio-mundu batean sartu ginen suposatuz, we would want a site template. Provision a new site based off a "business process" txantiloia.

The problem is that you can’t seem to get a functioning KPI that way. When I create a new site based on a template with a KPI List and KPI web part, the new site’s KPI data are broken. The new site’s KPI list points at whatever source you defined when you first saved it as a template.

Adibide moduan By:

  • Create a new site and build it to perfection. This site includes the KPI data.
  • Gorde txantiloi gisa.
  • Gune berri bat sortu eta oinarri txantiloia off bada.
  • Gune berri honek KPI elementuen zerrendan’ iturri gune plantilla, ez da uneko gunea.

Ez instantiation prozesua zuzendu URL.

I tried to solve this by specifying a relative URL when defining the KPI list item. Hala eta guztiz ere, Ezin izan dut lortu duten lan edozein aldaketa.

I always want to pair up these "problem" blog konponbidearen nolabaiteko mezu, but in this case I don’t have a good one. The best I can figure is that you need to go in to the newly provisioned site and fix everything manually. The UI makes this even harder because changing the URL of the source list causes a refresh, beraz, benetan duzu hutsetik gauza osoan birdefinitzeko.

Edonork kudeatzeko modu honetan hobeto daki, mesedez, post a comment.

</amaiera>

Technorati Tags:

MOSS Small Farm Instalazioa eta konfigurazioa Gerra Story

Aste honetan, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Arazo mota estimua handiagoa txostena MSDN foroak eta beste nonbait daukat.

Azken baserriko konfigurazio:

  • SQL / Index / Intranet WFE firewall barruan.
  • DMZ, WFE.
  • Mota batzuk suebaki DMZ eta barne-zerbitzariaren arteko.

Proiektuaren aurretik hasi ginen, we let the client know which ports needed to be open. During the give and take, atzera eta aurrera baino gehiago, esplizituki inoiz ez dugu esan bi gauza garrantzitsu:

  1. SSL esan nahi du ziurtagiri bat behar duzu..
  2. The DMZ server must be part of a domain.

Egun bat, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

Puntu honetan, nahasmena aurkitu dugu ziurtagiria SSL eta gehiagoko, zoritxarrez, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Batez besteko denbora, dugu konponbidea arkitektoek mugitu aurretik enpresa stuff.

Asteburuan A doa eta bezeroaren ziurtagiria lortzen.

Gure azpiegitura lasaia erakusten du eta deskubritzen DMZ zerbitzaria ez da edozein domeinu sartu (bai konfiantza mugatua edo intranet domeinu domeinu perimetroa). We wasted nearly a 1/2 duten egunean. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Beste egun batean pasatzen du, eta segurtasun-batzordeak hainbat, interesatuek eta (beraz, ez) errugabeen bystanders guztiak bat datoz dela OK intranet domeinu zerbitzaria DMZ sartu (hau da poc, azken finean, ez da ekoizpen irtenbide bat).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … Yee HAW! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" egoera.

Long Narrazio laburren, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran konfigurazio morroia eta voila! We were in business.

</amaiera>

Nire blog Harpidetu.

Technorati Tags:

Mea Culpa — SharePoint Designer * CAN * Sortu Estatuko Makina-fluxuak

I’ve recently learned that it’s possible and even fairly easy to create a state machine workflow using SharePoint Designer. Necessity is the mother of invention and all that good stuff and I had a need this week that looked for an invention. Coincidentally, Topatu dut MSDN foro honetan post baita. My personal experience this week and that "independent confirmation" lends strength to my conviction. I plan to write about this at greater length with a full blown example, baina hemen da GIST da:

  • Hurbilketa Izan ere, eu Zerrendako elementu bat aldatu ahal baliatzen, thereby triggering a new workflow. I’ve normally considered this to be a nuisance and even semaforoak erabiliz Blogetakoak hura kudeatzeko.
  • SharePoint ahalbidetzen anitz independente fluxuak aktiboa izan da zerrenda-elementu jakin aurka.

Konfiguratzeko:

  • Diseinatzeko zure egoera makina (hau da,, estatu eta nola estatu batetik bestera trantsizio).
  • Ezartzea, egoera bakoitzean workflow independente gisa.
  • Konfiguratzeko egoera fluxuak horietako bakoitza exekutatu zerrendako elementua edozein aldaketa erantzunez.

Egoera latza workflow bakoitzean patroi hau honela:

  • Hasieratzea gainean, determine whether it should really run by inspecting state information in the "current item". Abort if not.
  • Egin lana.
  • Update the "current item" with new state information. This triggers an update to the current item and fires off all the state workflows.

Alde batera nabarmenak prestazio bat aitortzen duen egoera makina workflow bat sortu ahal, egoera informazio hori guztia eraikin KPIs eta interesgarria ikuspegietako emanaldirik.

Handi samarra izan eragozpen bat du — standard workflow history tracking is even more useless than normal 🙂 That’s easily remedied, Hala ere,. Store all of your audit type information in a custom list. That’s probably a good idea even for vanilla sequential workflow, but that’s for another blog post 🙂

I call this a "mea culpa" izan dudalako, zoritxarrez, said more than once on forums and elsewhere that one must use visual studio to create a state machine workflow. That simply isn’t true.

</amaiera>

Nire blog Harpidetu.

Technorati Tags:

Hard Way ikasteko — DMZ WFE behar da domeinu bat izango da

Ez da egia, nahiz eta literalki, praktiko gisa materia, Interneteko web-begira aurrean DMZ batean bukaera behar domeinu bat izango da (I.E. ez da gutxi egin lantalde zerbitzari standalone batzuk). It doesn’t need to be in the same domain as the internal WFE(s) eta beste zerbitzariak (eta, seguruenik, behar ez), baina domeinu bat izan behar du.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Tamalez, Esaldi bat nonbait esan gehitzeko huts egin dugu, to efektua, "the whole bloody point of this configuration is to allow your DMZ WFE server, domeinu bat, barne baserria batzeko."

Ekitaldi ekaitz perfektua A, non dugu, funtsean, aurpegia geratzen denean begiratu izan dugu agian eskubidea, konspiratu arazo hau ezkutatzeko, gugandik nahiko prozesuan berandu arte, beraz, niri saihesten dei batetik nire "esango albiste txarra goiz" araua.

Sigh.

Nire blog Harpidetu.

Technorati Tags:

Ez baduzu, saiatu Twitter …

Twitter is a very odd duck. I’ve been using Twitter for a little over a month and in some indefinable way, it’s almost as important to me as email. I find myself vaguely unsettled if I wait too long before looking over what others are twittering about. I get annoyed at Twitter’s occasional performance problems because it means I’m missing out. I get a little puff of excitement when I see a new Woot announcement.

Modu bat benetan osatzen blogak eta foroak, eta are pertsonala aurpegira bilerak komunitate errealak eraikitzailea da.

Azken hilabetean, Jarraitu dut pertsona horrek saiakera bat hotzak dardarka ari Seder bat kudeatzeko at.

I’ve learned personal detail about many folks I mainly "know" blogen bitartez — non bizi, proiektu mota batzuetan lan egiten dute, dutela lan bat / familia-arazoak besterik kudeatzeko ni bezalako.

Pertsona ama zendu … a sad event for sure. But sharing that fact changes and enhances the character of the whole experience.

Hori besterik pertsonala stuff.

There’s more to it than that. It’s also another medium for sharing ideas, edo gehiago izan ohi dut, seeking help. Throw a question up on Twitter and you’re never left hanging and the responses typically arrive within minutes.

Ez baduzu, saiatu, you should really give it a go.

Look at me up http://www.twitter.com/pagalvin

Nire blog Harpidetu.

Technorati Tags: