Nyaraka za kila mwezi: Machi 2009

Furaha SharePoint SSO Ukweli wa Siku

1 Kujibu

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 mtandao sehemu). 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, mtumiaji si kuwa na kuingia ID yao wakati wao hit juu kwamba mfumo.

That part worked well for me. Hata hivyo, ni begs swali, "Jinsi gani mabadiliko ya kwamba mtumiaji id mtumiaji au password?” The user might have made a mistake, au labda wewe ni kufanya baadhi ya kupima katika mazingira ya dev na haja ya haraka kubadili kati ya akaunti.

Sijui jibu la kwamba, lakini najua kwamba unaweza kwenda katika Utawala wa Kati na kusimamia sifa ya mtumiaji:

Kati Tawala -> Shughuli -> Kusimamia Single Ishara-ya -> Kusimamia Akaunti Taarifa kwa Ufafanuzi Maombi Enterprise

Kutoka huko, unaweza kutaja programu ya nje (e.g. SAP) and the account you want to delete. You can also change the mapping.

Kama unajua jinsi ya kuruhusu watumiaji wa mwisho moja kwa moja mabadiliko ya sifa zao, upole kuchapisha maoni 🙂

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: , ,

Adventures Kwa iView Mtandao vya

Acha reply

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 imejenga sana ubora karatasi nyeupe juu ya somo hili.

kikwazo kwanza nilikuwa na kushinda mara - ambapo ni mtandao iView sehemu? Kwa sababu baadhi ya, mawazo yangu ya kwanza ilikuwa kwamba Ningependa kuwa na kushusha ni kutoka tovuti mahali fulani, perhaps SAP’s site. Mimi nilikuwa 1/2 convinced myself that iView web parts might even cost extra. Bila shaka, wao ni pamoja na MOSS (Nadhani Enterprise; kwamba ni nini mimi nina kutumia hapa katika tukio lolote). 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.

Nilikuwa kutumia sehemu ya mtandao na naendelea kupata ujumbe huu annoying:

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

karatasi nyeupe anasema wazi wazi kuhariri faili Configuration iko katika faili "<Kuendesha Letter:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, yote niliyoona ilikuwa "Mpango Files ... Config" na mimi akaenda moja kwa moja mbali na 12 mzinga. 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, lakini hiyo ni hadithi nyingine kwa siku nyingine.

Bottom line:

1. iView sehemu ya mtandao ni pamoja na nje ya boksi na SharePoint (pengine Enterprise).

2. uchawi Configuration faili, "TrustedSAPHosts.config", haina kuishi katika 12 mzinga.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: , ,

MOSS User Profile kama Mamlaka kwa mtumiaji Upendeleo lugha

4 majibu

Juu ya mradi wangu wa sasa, baadhi ya watumiaji wa kusafiri kote duniani na wakati wao kufika katika nchi mbalimbali, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (Nimekuwa tu waligundua kwamba mashine mgeni inaweza kuwa Packs lugha ya haki… pengine si, kwa kweli… Mimi maegesho kwamba moja kwa sasa).

SharePoint needs to provide a mechanism whereby the user can pick their preferred language and then have MOSS honor that language regardless of how the user accesses MOSS. In other words, disregard whatever the browser tells IIS/MOSS and instead look up that preferred language and use it.

Tunakwenda kuchunguza njia mbili:

  1. HTTP Handler: desturi HTTP handler imewekwa kwenye IIS kuangalia hadi MOSS mtumiaji profile, kufikiri lugha unayopendelea na kisha kubadili header HTTP kuzunguka kama inahitajika kabla ya kupitisha kudhibiti MOSS.
  2. global.asax: Modify global.asax to do the same thing. We may modify something else, but the idea is that we find some place where we can insert our locale-switching logic.

nyingine complicating sababu ni kwamba tunahitaji kusaidia watumiaji 60k, kuhusu 1,000 ambayo inaweza kuwa wakati huo huo kupata MOSS katika ujazo wa kilele.

Handler HTTP inaonekana kuwa kuporomoka, but possibly the best place to put the code since it’s at the IIS level and all-knowing. It’s a good single point of work.

Sisi ni leaning kuelekea mbinu global.asax aina, hasa kwa sababu tunaamini tutaweza kuwa na chaguzi zaidi kwa ajili ya data Caching katika hatua hiyo.

Nitakuwa mabalozi zaidi juu ya somo hili kama mimi kujifunza zaidi.

Kama una kujua chochote kuhusu hii, tafadhali baada ya maoni 🙂

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Ukamataji “mailto:” Metrics

5 majibu

I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — kama wewe ni kuangalia katika makala ya kuvutia juu ya intranet na wanataka kushiriki kwa mtu, click a link labeled "Share this story" email ni rafiki yako.

Sisi alicheza karibu na fomu ya desturi kwa lengo hili, lakini mwisho, akili ya kawaida alishinda siku na sisi tu kutumia ukoo <href = mailto:…> technique. (<mailto href:…> ni ya kushangaza imara kidogo kidogo ya HTML; kama ziada, kiungo ambayo huleta mimi nyuma yangu ya zamani UNIX mtu siku kurasa; wale walikuwa siku!).

Mbinu hii hutoa interface kubwa kwa watumiaji wa mwisho kwani wao kupata kwa kutumia MS Outlook yao ukoo mteja (au chochote email mteja wao kuwa imewekwa).

Inafanya mambo magumu juu yetu aina developer maskini kwani wao mteja * pia * anataka kukimbia ripoti katika siku zijazo kwamba inaonyesha jinsi mara nyingi watumiaji wa kushiriki hadithi na hata hadithi ambayo ni pamoja mara nyingi.

We whiteboarded a few potential solutions. My favorite is to carbon copy (CC) a SharePoint list. That way, the end user still gets the outlook client while we get to capture the event because we’ll get a copy of the email ourselves. There are some obvious drawbacks. The main problem is that the user could simply blank out or otherwise mangle the CC address. Na, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Kama una baadhi ya mbinu wajanja kutatua tatizo hili, tafadhali kufanya kuwaambia.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin